Vulnerabilities · 2020 · Envoyproxy
CVE-2020-11767
Envoyproxy Envoy vulnerability
Istio through 1.5.1 and Envoy through 1.14.1 have a data-leak issue. If there is a TCP connection (negotiated with SNI over HTTPS) to *.example.com, a request for a domain concurrently configured explicitly (e.g., abc.example.com) is sent to the server(s) listening behind *.example.com. The outcome should instead be 421 Misdirected Request. Imagine a shared caching forward proxy re-using an HTTP/2 connection for a large subnet with many users. If a victim is interacting with abc.example.com, and a server (for abc.example.com) recycles the TCP connection to the forward proxy, the victim's browser may suddenly start sending sensitive data to a *.example.com server. This occurs because the forward proxy between the victim and the origin server reuses connections (which obeys the specification), but neither Istio nor Envoy corrects this by sending a 421 error. Similarly, this behavior voids the security model browsers have put in place between domains.
Affected products
Envoy, Istio. 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
- bugs.chromium.org/p/chromium/issues/detail?id=954160#c5 · Third Party Advisory
- github.com/envoyproxy/envoy/issues/6767 · Third Party Advisory
- github.com/istio/istio/issues/13589 · Exploit
- github.com/istio/istio/issues/9429 · Third Party Advisory
- nvd.nist.gov/vuln/detail/CVE-2020-11767
- cve.org/CVERecord?id=CVE-2020-11767
More vulnerabilities in Envoyproxy products
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.