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
Configurations
History
21 Nov 2024, 04:33
Type | Values Removed | Values Added |
---|---|---|
References | () http://lists.opensuse.org/opensuse-security-announce/2020-03/msg00034.html - | |
References | () https://blog.envoyproxy.io - Product | |
References | () https://github.com/envoyproxy/envoy/commits/master - Patch | |
References | () https://github.com/envoyproxy/envoy/security/advisories/GHSA-356m-vhw2-wcm4 - Exploit, Third Party Advisory | |
References | () https://groups.google.com/forum/#%21forum/envoy-users - |
Information
Published : 2019-12-13 13:15
Updated : 2024-11-21 04:33
NVD link : CVE-2019-18802
Mitre link : CVE-2019-18802
CVE.ORG link : CVE-2019-18802
JSON object : View
Products Affected
envoyproxy
- envoy
CWE