Codex Discovered a Hidden HTTP/2 Bomb

DiabloD318d ago· 2 in thread

After reading the article, I can conclude that Codex discovered nothing new.

This is already something that is known, and if you're able to be targeted by this (which is not the majority of users) configure your httpd differently.

swedishuser18d ago

Apache and nginx maintainers implemented fixes one or two days after the author reported, so how do you mean this was known already?

DiabloD316d ago

AFIAK, it was already being actively exploited in DDoS attacks.

BobbyTables218d ago· 1 in thread

Couldn’t simple fuzzing have found this?

pixel_popping18d ago

Not really, as it wasn't found for close to a decade (>5 years for most webservers).

HDBaseT18d ago

Not ideal.

This appears to be fixed as of April (at least for Apache). [0].

[0] - https://github.com/nginx/nginx/commit/365694160a85229a7cb006...

eqvinox17d ago

> We disclosed to Apache on May 27, and Stefan Eissing fixed it on the same day by making cookie headers count against LimitRequestFields.

I was about to say, the bug here isn't in the protocol, it's that memory use isn't being counted & limited as it should... and, yeah.

I'm a bit surprised this happened to Apache, though. APR uses pool allocators. That should be easy enough to track and limit...

Codex Discovered a Hidden HTTP/2 Bomb (opens in new tab)

Codex Discovered a Hidden HTTP/2 Bomb (opens in new tab)

7 comments

7 comments