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 up to and including 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.
| Vulnerable Product | Search on Vulmon | Subscribe to Product |
|---|---|---|
envoyproxy envoy 1.0.0 |
||
envoyproxy envoy 1.1.0 |
||
envoyproxy envoy 1.2.0 |
||
envoyproxy envoy 1.4.0 |
||
envoyproxy envoy 1.6.0 |
||
envoyproxy envoy 1.11.0 |
||
envoyproxy envoy 1.11.2 |
||
envoyproxy envoy 1.7.1 |
||
envoyproxy envoy 1.8.0 |
||
envoyproxy envoy 1.9.0 |
||
envoyproxy envoy 1.9.1 |
||
envoyproxy envoy 1.3.0 |
||
envoyproxy envoy 1.5.0 |
||
envoyproxy envoy 1.7.0 |
||
envoyproxy envoy 1.10.0 |
||
envoyproxy envoy 1.11.1 |
Vulmon