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://www.envoyproxy.io/docs/envoy/v1.9.1/intro/version_history | Release Notes Vendor Advisory |
https://github.com/envoyproxy/envoy/issues/6434 | Exploit Issue Tracking Third Party Advisory |
https://groups.google.com/forum/#!topic/envoy-announce/VoHfnDqZiAM | Third Party Advisory |
https://access.redhat.com/errata/RHSA-2019:0741 | Third Party Advisory |
https://github.com/envoyproxy/envoy/security/advisories/GHSA-x74r-f4mw-c32h | Exploit Mitigation Third Party Advisory |
Information
Published : 2019-04-25 08:29
Updated : 2022-01-01 12:16
NVD link : CVE-2019-9900
Mitre link : CVE-2019-9900
JSON object : View
CWE
CWE-74
Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection')
Products Affected
envoyproxy
- envoy
redhat
- openshift_service_mesh