Vulnerabilities · 2019 · Envoyproxy
CVE-2019-9900
Envoyproxy Envoy vulnerability
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
Envoy, Openshift Service Mesh. The exact versions are in the references.
What to do now
- Check your exposureFind out whether Envoyproxy Envoy runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- www.envoyproxy.io/docs/envoy/v1.9.1/intro/version_history · Vendor Advisory
- github.com/envoyproxy/envoy/security/advisories/GHSA-x74r-f4mw-c32h · Exploit
- access.redhat.com/errata/RHSA-2019:0741 · Third Party Advisory
- github.com/envoyproxy/envoy/issues/6434 · Exploit
- groups.google.com/forum/#%21topic/envoy-announce/VoHfnDqZiAM
- nvd.nist.gov/vuln/detail/CVE-2019-9900
- cve.org/CVERecord?id=CVE-2019-9900
More vulnerabilities in Envoyproxy products
CVE-2026-22771CVE-2025-66220CVE-2025-64763CVE-2025-64527CVE-2025-62504CVE-2025-62409CVE-2025-55162CVE-2025-54588All 93
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.