CVE-2020-11767
Istio through 1.5.1 and Envoy through 1.14.1 have a data-leak issue.
Auswirkung
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.
Ein Angreifer kann die Lücke über das Netzwerk ausnutzen, ohne Anmeldung, allerdings muss ein Nutzer etwas tun, etwa eine Datei oder einen Link öffnen. Dafür müssen bestimmte Bedingungen erfüllt sein, was einen Angriff erschwert. Bei Erfolg: geringes Risiko, dass Daten ausgelesen werden.
Betroffene Produkte
| Hersteller | Produkt | Betroffene Versionen |
|---|---|---|
| Envoyproxy | Envoy | bis einschließlich 1.14.1 |
| Istio | Istio | bis einschließlich 1.5.1 |
Referenzen
- NVD-Eintrag
- CVE.org-Eintrag
- https://bugs.chromium.org/p/chromium/issues/detail?id=954160#c5
- https://github.com/envoyproxy/envoy/issues/6767
- https://github.com/istio/istio/issues/13589
- https://github.com/istio/istio/issues/9429
- https://bugs.chromium.org/p/chromium/issues/detail?id=954160#c5
- https://github.com/envoyproxy/envoy/issues/6767
- https://github.com/istio/istio/issues/13589
- https://github.com/istio/istio/issues/9429