First published: Tue Apr 09 2019(Updated: )
A flaw was found in Envoy 1.9.0 and older. When parsing HTTP/1.x header values, Envoy 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. Upstream issue: <a href="https://github.com/envoyproxy/envoy/issues/6434">https://github.com/envoyproxy/envoy/issues/6434</a> References: <a href="https://istio.io/blog/2019/announcing-1.1.2/">https://istio.io/blog/2019/announcing-1.1.2/</a>
Affected Software | Affected Version | How to fix |
---|---|---|
Envoy Envoy | <1.9.0 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The severity of REDHAT-BUG-1698020 is considered high due to the potential for remote attackers to exploit the flaw.
To fix REDHAT-BUG-1698020, upgrade Envoy to version 1.10.0 or later, which addresses the vulnerability.
Versions of Envoy up to and including 1.9.0 are affected by REDHAT-BUG-1698020.
The impact of REDHAT-BUG-1698020 allows remote attackers to bypass header matching rules, potentially gaining unauthorized access.
A temporary workaround for REDHAT-BUG-1698020 is to implement strict validation of header values to reject NUL characters.