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.
References
Link | Resource |
---|---|
https://github.com/envoyproxy/envoy/commits/master | Third Party Advisory |
https://github.com/envoyproxy/envoy/issues/8520 | Third Party Advisory |
https://github.com/envoyproxy/envoy/commit/afc39bea36fd436e54262f150c009e8d72db5014 | Patch Third Party Advisory |
Configurations
Configuration 1 (hide)
|
Information
Published : 2019-10-09 09:15
Updated : 2019-10-17 10:03
NVD link : CVE-2019-15226
Mitre link : CVE-2019-15226
JSON object : View
CWE
CWE-400
Uncontrolled Resource Consumption
Products Affected
envoyproxy
- envoy