Note:
This project will be discontinued after December 13, 2021. [more]
Product:
Envoy
(Envoyproxy)Repositories |
Unknown: This might be proprietary software. |
#Vulnerabilities | 74 |
Date | Id | Summary | Products | Score | Patch | Annotated |
---|---|---|---|---|---|---|
2020-07-01 | 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. | Envoy | 7.5 | ||
2020-07-14 | 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, when it should only allow subdomain.example.com. This defect applies to both validating a client TLS certificate in mTLS, and validating a server TLS certificate for upstream connections. This... | Envoy | 5.4 | ||
2020-10-01 | 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. | Envoy | 8.3 | ||
2020-10-01 | CVE-2020-25018 | Envoy master between 2d69e30 and 3b5acb2 may fail to parse request URL that requires host canonicalization. | Envoy | 7.5 | ||
2020-12-15 | CVE-2020-35470 | Envoy before 1.16.1 logs an incorrect downstream address because it considers only the directly connected peer, not the information in the proxy protocol header. This affects situations with tcp-proxy as the network filter (not HTTP filters). | Envoy | 8.8 | ||
2020-12-15 | CVE-2020-35471 | Envoy before 1.16.1 mishandles dropped and truncated datagrams, as demonstrated by a segmentation fault for a UDP packet size larger than 1500. | Envoy | 7.5 | ||
2021-03-11 | CVE-2021-21378 | Envoy is a cloud-native high-performance edge/middle/service proxy. In Envoy version 1.17.0 an attacker can bypass authentication by presenting a JWT token with an issuer that is not in the provider list when Envoy's JWT Authentication filter is configured with the `allow_missing` requirement under `requires_any` due to a mistake in implementation. Envoy's JWT Authentication filter can be configured with the `allow_missing` requirement that will be satisfied if JWT is missing (JwtMissed... | Envoy | 8.2 | ||
2021-05-20 | CVE-2021-28682 | An issue was discovered in Envoy through 1.71.1. There is a remotely exploitable integer overflow in which a very large grpc-timeout value leads to unexpected timeout calculations. | Envoy | 7.5 | ||
2021-05-20 | CVE-2021-28683 | An issue was discovered in Envoy through 1.71.1. There is a remotely exploitable NULL pointer dereference and crash in TLS when an unknown TLS alert code is received. | Envoy | 7.5 | ||
2021-05-20 | CVE-2021-29258 | An issue was discovered in Envoy 1.14.0. There is a remotely exploitable crash for HTTP2 Metadata, because an empty METADATA map triggers a Reachable Assertion. | Envoy | 7.5 |