First published: Wed Oct 09 2019(Updated: )
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.
Credit: cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
Envoy Proxy | =1.0.0 | |
Envoy Proxy | =1.1.0 | |
Envoy Proxy | =1.2.0 | |
Envoy Proxy | =1.3.0 | |
Envoy Proxy | =1.4.0 | |
Envoy Proxy | =1.5.0 | |
Envoy Proxy | =1.6.0 | |
Envoy Proxy | =1.7.0 | |
Envoy Proxy | =1.7.1 | |
Envoy Proxy | =1.8.0 | |
Envoy Proxy | =1.9.0 | |
Envoy Proxy | =1.9.1 | |
Envoy Proxy | =1.10.0 | |
Envoy Proxy | =1.11.0 | |
Envoy Proxy | =1.11.1 | |
Envoy Proxy | =1.11.2 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2019-15226 has been assigned a severity rating of medium due to its potential impact on service availability.
To fix CVE-2019-15226, upgrade to a version of Envoy Proxy that is 1.11.2 or later.
CVE-2019-15226 affects Envoy Proxy versions from 1.10.0 up to, but not including, 1.11.2.
CVE-2019-15226 impacts both HTTP/1.x and HTTP/2 traffic.
Yes, CVE-2019-15226 can be exploited to cause a Denial of Service (DoS) condition.