On Saturday 25 June 2022 at 11:27 UTC, a CLDAP reflection targeted a crypto exchange customer in Iberia. The attack peaked at 270.2 Gbps and lasted 63 minutes. Traffic originated from 722 autonomous systems in 63 countries, predominantly misconfigured open reflectors.
| Vector | CLDAP reflection |
| Peak | 270.2 Gbps |
| Duration | 63 min |
| Time to mitigation | 0.688 s |
| Attack traffic reaching origin | 0.023% |
| Legitimate traffic challenged | 0.64% |
Timeline
The attack was preceded by an extortion email received two days earlier. Edge packet filters identified the flood by source port and payload signature and dropped it at line rate across 36 points of presence.
What the customer saw
A brief increase in p99 latency of 185 ms during the first minute, then normal service.
Recommendations
- Enable log streaming to your SIEM for faster correlation.
- Add a dedicated rate limit for the targeted route.
- Review allow-listed partner ranges quarterly.
Is the risk score exposed in the logs so we can build our own dashboards on it?
Is the risk score exposed in the logs so we can build our own dashboards on it?
This matches what we see in iGaming around big matches.
Nice to read a vendor blog that admits what went wrong.
Great write-up. We saw almost the same pattern on our login endpoint last month.
This matches what we see in iGaming around big matches.
Interesting that most attacks are under ten minutes. Our experience is similar.