CVE-2019-15226

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

Remedy

https://github.com/envoyproxy/envoy/commit/afc39bea36fd436e54262f150c009e8d72db5014

Never miss a vulnerability like this again

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co

By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.