When parsing HTTP/1.x header values, Envoy 1.9.0 and before does not reject embedded zero characters (NUL, ASCII 0x0). This allows remote attackers crafting header values containing embedded NUL characters to potentially bypass header matching rules, gaining access to unauthorized resources.
References
Link | Resource |
---|---|
https://access.redhat.com/errata/RHSA-2019:0741 | Third Party Advisory |
https://github.com/envoyproxy/envoy/issues/6434 | Exploit Issue Tracking Third Party Advisory |
https://github.com/envoyproxy/envoy/security/advisories/GHSA-x74r-f4mw-c32h | Exploit Mitigation Third Party Advisory |
https://groups.google.com/forum/#%21topic/envoy-announce/VoHfnDqZiAM | |
https://www.envoyproxy.io/docs/envoy/v1.9.1/intro/version_history | Release Notes Vendor Advisory |
Configurations
History
01 Jan 2022, 20:16
Type | Values Removed | Values Added |
---|---|---|
CPE | cpe:2.3:a:redhat:openshift_service_mesh:-:*:*:*:*:*:*:* | |
References | (CONFIRM) https://github.com/envoyproxy/envoy/security/advisories/GHSA-x74r-f4mw-c32h - Exploit, Mitigation, Third Party Advisory | |
CWE | CWE-74 |
Information
Published : 2019-04-25 15:29
Updated : 2024-02-04 20:20
NVD link : CVE-2019-9900
Mitre link : CVE-2019-9900
CVE.ORG link : CVE-2019-9900
JSON object : View
Products Affected
envoyproxy
- envoy
redhat
- openshift_service_mesh
CWE
CWE-74
Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection')