Information Exposure Affecting envoyproxy/envoy package, versions [,1.14.2)


Severity

Recommended
0.0
low
0
10

CVSS assessment made by Snyk's Security Team. Learn more

Threat Intelligence

EPSS
0.13% (50th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-UNMANAGED-ENVOYPROXYENVOY-2365500
  • published26 Jan 2022
  • disclosed15 Apr 2020
  • creditUnknown

Introduced: 15 Apr 2020

CVE-2020-11767  (opens in a new tab)
CWE-200  (opens in a new tab)

How to fix?

Upgrade envoyproxy/envoy to version 1.14.2 or higher.

Overview

Affected versions of this package are vulnerable to Information Exposure. 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.

CVSS Scores

version 3.1