296,138
Total vulnerabilities in the database
Upon receiving each incoming request header data, Envoy will iterate over existing request headers to verify that the total size of the headers stays below a maximum limit. The implementation in versions 1.10.0 through 1.11.1 for HTTP/1.x traffic and all versions of Envoy for HTTP/2 traffic had O(n^2) performance characteristics. A remote attacker may craft a request that stays below the maximum request header size but consists of many thousands of small headers to consume CPU and result in a denial-of-service attack.
Software | From | Fixed in |
---|---|---|
envoyproxy / envoy | 1.0.0 | 1.0.0.x |
envoyproxy / envoy | 1.1.0 | 1.1.0.x |
envoyproxy / envoy | 1.2.0 | 1.2.0.x |
envoyproxy / envoy | 1.3.0 | 1.3.0.x |
envoyproxy / envoy | 1.4.0 | 1.4.0.x |
envoyproxy / envoy | 1.5.0 | 1.5.0.x |
envoyproxy / envoy | 1.6.0 | 1.6.0.x |
envoyproxy / envoy | 1.7.0 | 1.7.0.x |
envoyproxy / envoy | 1.7.1 | 1.7.1.x |
envoyproxy / envoy | 1.8.0 | 1.8.0.x |
envoyproxy / envoy | 1.9.0 | 1.9.0.x |
envoyproxy / envoy | 1.9.1 | 1.9.1.x |
envoyproxy / envoy | 1.10.0 | 1.10.0.x |
envoyproxy / envoy | 1.11.0 | 1.11.0.x |
envoyproxy / envoy | 1.11.1 | 1.11.1.x |
envoyproxy / envoy | 1.11.2 | 1.11.2.x |