An issue was discovered in Envoy 1.12.0. An untrusted remote client may send an HTTP header (such as Host) with whitespace after the header content. Envoy will treat "header-value " as a different string from "header-value" so for example with the Host header "example.com " one could bypass "example.com" matchers.
References
Link | Resource |
---|---|
https://github.com/envoyproxy/envoy/commits/master | Patch |
https://blog.envoyproxy.io | Product |
https://github.com/envoyproxy/envoy/security/advisories/GHSA-356m-vhw2-wcm4 | Exploit Third Party Advisory |
https://groups.google.com/forum/#!forum/envoy-users | Mailing List Third Party Advisory |
http://lists.opensuse.org/opensuse-security-announce/2020-03/msg00034.html |
Configurations
Information
Published : 2019-12-13 05:15
Updated : 2020-08-24 10:37
NVD link : CVE-2019-18802
Mitre link : CVE-2019-18802
JSON object : View
CWE
Products Affected
envoyproxy
- envoy