CVE-2020-11767
First published: Wed Apr 15 2020(Updated: )
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.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Envoyproxy Envoy | <=1.14.1 | |
| Istio Istio | <=1.5.1 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the vulnerability ID for this data-leak issue?
The vulnerability ID is CVE-2020-11767.
Which software versions are affected by this vulnerability?
Istio versions up to and including 1.5.1 and Envoy versions up to and including 1.14.1 are affected.
What is the severity of CVE-2020-11767?
The severity of CVE-2020-11767 is rated as low with a severity value of 3.1.
How does the data-leak issue in CVE-2020-11767 occur?
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.
Are there any references related to CVE-2020-11767?
Yes, you can find more information about CVE-2020-11767 on the following links: [link1](https://bugs.chromium.org/p/chromium/issues/detail?id=954160#c5), [link2](https://github.com/envoyproxy/envoy/issues/6767), [link3](https://github.com/istio/istio/issues/13589)
- agent/references
- agent/author
- agent/severity
- agent/type
- agent/event
- agent/description
- agent/last-modified-date
- agent/softwarecombine
- agent/first-publish-date
- agent/tags
- collector/nvd-index
- agent/software-canonical-lookup-request
- vendor/envoyproxy
- canonical/envoyproxy envoy
- version/envoyproxy envoy/1.14.1
- vendor/istio
- canonical/istio istio
- version/istio istio/1.5.1