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>
Credit: cve@mitre.org
Affected Software | Affected Version | How to fix |
---|---|---|
Envoyproxy Envoy | <=1.9.0 | |
Redhat Openshift Service Mesh |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2019-9900 is a vulnerability in Envoy 1.9.0 and earlier that allows remote attackers to potentially bypass header matching rules.
CVE-2019-9900 affects EnvoyProxy Envoy versions up to and including 1.9.0.
CVE-2019-9900 has a severity rating of 8.3 (high).
Remote attackers can craft header values with embedded NUL characters to potentially bypass header matching rules and gain unauthorized access to resources.
To fix the CVE-2019-9900 vulnerability, upgrade EnvoyProxy Envoy to a version later than 1.9.0.