CVE-2019-15226

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.

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

Configuration 1

cpe:2.3:a:envoyproxy:envoy:1.0.0:*:*:*:*:*:*:* cpe:2.3:a:envoyproxy:envoy:1.1.0:*:*:*:*:*:*:* cpe:2.3:a:envoyproxy:envoy:1.2.0:*:*:*:*:*:*:* cpe:2.3:a:envoyproxy:envoy:1.3.0:*:*:*:*:*:*:* cpe:2.3:a:envoyproxy:envoy:1.4.0:*:*:*:*:*:*:* cpe:2.3:a:envoyproxy:envoy:1.5.0:*:*:*:*:*:*:* cpe:2.3:a:envoyproxy:envoy:1.6.0:*:*:*:*:*:*:* cpe:2.3:a:envoyproxy:envoy:1.7.0:*:*:*:*:*:*:* cpe:2.3:a:envoyproxy:envoy:1.7.1:*:*:*:*:*:*:* cpe:2.3:a:envoyproxy:envoy:1.8.0:*:*:*:*:*:*:* cpe:2.3:a:envoyproxy:envoy:1.9.0:*:*:*:*:*:*:* cpe:2.3:a:envoyproxy:envoy:1.9.1:*:*:*:*:*:*:* cpe:2.3:a:envoyproxy:envoy:1.10.0:*:*:*:*:*:*:* cpe:2.3:a:envoyproxy:envoy:1.11.0:*:*:*:*:*:*:* cpe:2.3:a:envoyproxy:envoy:1.11.1:*:*:*:*:*:*:* cpe:2.3:a:envoyproxy:envoy:1.11.2:*:*:*:*:*:*:*

---

Published : 2019-10-09 04:15

Updated : 2019-10-17 05:03

---

NVD link : CVE-2019-15226

Mitre link : CVE-2019-15226

No products.

CWE-400