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 |
History
No history.
MITRE Information
Status: PUBLISHED
Assigner: mitre
Published: 2019-04-25T14:55:57
Updated: 2019-11-12T13:27:05
Reserved: 2019-03-21T00:00:00
Link: CVE-2019-9900
JSON object: View
NVD Information
Status : Modified
Published: 2019-04-25T15:29:01.497
Modified: 2023-11-07T03:13:48.520
Link: CVE-2019-9900
JSON object: View
Redhat Information
No data.
CWE