Vulnerabilities · 2020 · Envoyproxy
CVE-2020-8660
Envoyproxy Envoy vulnerability
CNCF Envoy through 1.13.0 TLS inspector bypass. TLS inspector could have been bypassed (not recognized as a TLS client) by a client using only TLS 1.3. Because TLS extensions (SNI, ALPN) were not inspected, those connections might have been matched to a wrong filter chain, possibly bypassing some security restrictions in the process.
Affected products
Envoy. 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.13.1/intro/version_history · Vendor Advisory
- access.redhat.com/errata/RHSA-2020:0734 · Third Party Advisory
- github.com/envoyproxy/envoy/security/advisories/GHSA-c4g8-7grc-5wvx · Third Party Advisory
- nvd.nist.gov/vuln/detail/CVE-2020-8660
- cve.org/CVERecord?id=CVE-2020-8660
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.