News for hackers. Stuff that matters.
Re:Google mitigated the largest DDoS attack to date, peaking... by Aissen on Tuesday October 10, 2023 @08:42AM (#37831316)
The technical article (linked in the post) has more interesting details: https://blog.cloudflare.com/technical-breakdown-http2-rapid-...
Re:Google mitigated the largest DDoS attack to date, peaking... by H8crilA on Tuesday October 10, 2023 @10:22AM (#37832487)
This should be the top comment.

TL;DR: HTTP/2 is internally concurrent, can handle multiple streams. It is possible in HTTP/2 to send a nasty request that looks like so:

  - GET x1
  - GET x2
  - GET x3
  - GET x4
  - ...
  - GET x100
  - Actually, cancel all of the above
  - GET x101
  - GET x102
  - (...)
  - GET x200
  - Actually, cancel all of the above.
  - (...)
This can be repeated a lot of times. The problem is that the endpoint, which typically is a reverse proxy, might start dispatching the requests before it reads about their cancellation. And sure it will cancel them, but that will result in some resource usage downstream. Such requests are accepted because at no point the client has opened more than 100 streams, which is the typical concurrency limit. The example from the blog manages to squeze 1000 GETs in a single packet.

Maybe it's just me, but it's always fun to see such creative and simple abuses of protocols/code.

Re:Google mitigated the largest DDoS attack to date, peaking... by ryanisnan on Tuesday October 10, 2023 @12:49PM (#37834486)
That’s pretty fascinating. This is a naive solution, but couldn’t the protocol have supported limits of requests per packet? I get that it is antithetical, but for most sites, this type of request pattern seems highly unusual.
Re:Google mitigated the largest DDoS attack to date, peaking... by AtNightWeCode on Tuesday October 10, 2023 @01:13PM (#37834741)
If this is true than the design is problematic. What makes it even worse is that cancellation of requests typically does not work in cloud environments. It is a bit laughable that Azure for instance recommend the use of cancellation tokens but in reality you never get them for web requests.
Re:Google mitigated the largest DDoS attack to date, peaking... by carstenhag on Tuesday October 10, 2023 @02:48PM (#37835908)
Look at F5's entry regarding this CVE. They specifically mention they have set a safer limit because they expected this to be an attack vector, haha