Description
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.
Affected products
Version statuses are supplied by the assigning organization. Consult the original record for detailed ranges and platform conditions.
n/a n/a
n/aaffected
References
- https://access.redhat.com/errata/RHSA-2019:0741 ↗
- https://www.envoyproxy.io/docs/envoy/v1.9.1/intro/version_history ↗
- https://github.com/envoyproxy/envoy/issues/6434 ↗
- https://groups.google.com/forum/#%21topic/envoy-announce/VoHfnDqZiAM ↗
- https://github.com/envoyproxy/envoy/security/advisories/GHSA-x74r-f4mw-c32h ↗