Lucene search

K
EnvoyproxyEnvoy1.13.0

5 matches found

CVE
CVE
added 2020/03/04 10:15 p.m.107 views

CVE-2020-8660

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 s...

5.3CVSS5.6AI score0.00025EPSS
CVE
CVE
added 2020/07/01 3:15 p.m.95 views

CVE-2020-8663

Envoy version 1.14.2, 1.13.2, 1.12.4 or earlier may exhaust file descriptors and/or memory when accepting too many connections.

7.5CVSS7.4AI score0.00105EPSS
CVE
CVE
added 2024/04/18 3:15 p.m.86 views

CVE-2024-32475

Envoy is a cloud-native, open source edge and service proxy. When an upstream TLS cluster is used with auto_sni enabled, a request containing a host/:authority header longer than 255 characters triggers an abnormal termination of Envoy process. Envoy does not gracefully handle an error when setting...

7.5CVSS6.5AI score0.00044EPSS
CVE
CVE
added 2020/07/14 10:15 p.m.73 views

CVE-2020-15104

In Envoy before versions 1.12.6, 1.13.4, 1.14.4, and 1.15.0 when validating TLS certificates, Envoy would incorrectly allow a wildcard DNS Subject Alternative Name apply to multiple subdomains. For example, with a SAN of *.example.com, Envoy would incorrectly allow nested.subdomain.example.com, whe...

5.5CVSS5.2AI score0.00116EPSS
CVE
CVE
added 2020/10/01 5:15 p.m.59 views

CVE-2020-25017

Envoy through 1.15.0 only considers the first value when multiple header values are present for some HTTP headers. Envoy’s setCopy() header map API does not replace all existing occurences of a non-inline header.

8.3CVSS8.1AI score0.00053EPSS