Bitnami package
envoy
pkg:bitnami/envoy
Vulnerabilities (117)
| CVE | Sev | CVSS | KEV | Affected versions | Fixed in | Published | Description |
|---|---|---|---|---|---|---|---|
| CVE-2021-29258 | Hig | 7.5 | >= 1.14.6, < 1.14.7 | 1.14.7 | May 20, 2021 | 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. | |
| CVE-2021-28683 | Hig | 7.5 | >= 1.16.2, < 1.16.3 | 1.16.3 | May 20, 2021 | 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. | |
| CVE-2021-28682 | Hig | 7.5 | >= 1.14.6, < 1.14.7 | 1.14.7 | May 20, 2021 | 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. | |
| CVE-2021-21378 | Hig | 8.2 | >= 1.17.0, < 1.17.1 | 1.17.1 | Mar 11, 2021 | 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 | |
| CVE-2020-35471 | Hig | 7.5 | < 1.16.1 | 1.16.1 | Dec 15, 2020 | Envoy before 1.16.1 mishandles dropped and truncated datagrams, as demonstrated by a segmentation fault for a UDP packet size larger than 1500. | |
| CVE-2020-35470 | Hig | 8.8 | < 1.16.1 | 1.16.1 | Dec 15, 2020 | 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). | |
| CVE-2020-25017 | Hig | 8.3 | < 1.12.7 | 1.12.7 | Oct 1, 2020 | 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. | |
| CVE-2020-15104 | Med | 4.6 | < 1.12.6 | 1.12.6 | Jul 14, 2020 | 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.subdoma | |
| CVE-2020-8663 | Hig | 7.5 | < 1.12.5 | 1.12.5 | Jul 1, 2020 | 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. | |
| CVE-2020-12605 | Hig | 7.5 | < 1.12.5 | 1.12.5 | Jul 1, 2020 | Envoy version 1.14.2, 1.13.2, 1.12.4 or earlier may consume excessive amounts of memory when processing HTTP/1.1 headers with long field names or requests with long URLs. | |
| CVE-2020-12604 | Hig | 7.5 | < 1.12.5 | 1.12.5 | Jul 1, 2020 | Envoy version 1.14.2, 1.13.2, 1.12.4 or earlier is susceptible to increased memory usage in the case where an HTTP/2 client requests a large payload but does not send enough window updates to consume the entire stream and does not reset the stream. | |
| CVE-2020-12603 | Hig | 7.5 | < 1.12.5 | 1.12.5 | Jul 1, 2020 | Envoy version 1.14.2, 1.13.2, 1.12.4 or earlier may consume excessive amounts of memory when proxying HTTP/2 requests or responses with many small (i.e. 1 byte) data frames. | |
| CVE-2020-11767 | Low | 3.1 | < 1.14.2 | 1.14.2 | Apr 15, 2020 | 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 *.examp | |
| CVE-2020-8660 | Med | 5.3 | < 1.12.3 | 1.12.3 | Mar 4, 2020 | 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, possib | |
| CVE-2020-8664 | Med | 5.3 | <= 1.13.0 | — | Mar 4, 2020 | CNCF Envoy through 1.13.0 has incorrect Access Control when using SDS with Combined Validation Context. Using the same secret (e.g. trusted CA) across many resources together with the combined validation context could lead to the “static” part of the validation context to be not | |
| CVE-2020-8661 | Hig | 7.5 | <= 1.13.0 | — | Mar 4, 2020 | CNCF Envoy through 1.13.0 may consume excessive amounts of memory when responding internally to pipelined requests. | |
| CVE-2020-8659 | Hig | 7.5 | <= 1.13.0 | — | Mar 4, 2020 | CNCF Envoy through 1.13.0 may consume excessive amounts of memory when proxying HTTP/1.1 requests or responses with many small (i.e. 1 byte) chunks. |
- affected >= 1.14.6, < 1.14.7fixed 1.14.7
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.
- affected >= 1.16.2, < 1.16.3fixed 1.16.3
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.
- affected >= 1.14.6, < 1.14.7fixed 1.14.7
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.
- affected >= 1.17.0, < 1.17.1fixed 1.17.1
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
- affected < 1.16.1fixed 1.16.1
Envoy before 1.16.1 mishandles dropped and truncated datagrams, as demonstrated by a segmentation fault for a UDP packet size larger than 1500.
- affected < 1.16.1fixed 1.16.1
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).
- affected < 1.12.7fixed 1.12.7
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.
- affected < 1.12.6fixed 1.12.6
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.subdoma
- affected < 1.12.5fixed 1.12.5
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.
- affected < 1.12.5fixed 1.12.5
Envoy version 1.14.2, 1.13.2, 1.12.4 or earlier may consume excessive amounts of memory when processing HTTP/1.1 headers with long field names or requests with long URLs.
- affected < 1.12.5fixed 1.12.5
Envoy version 1.14.2, 1.13.2, 1.12.4 or earlier is susceptible to increased memory usage in the case where an HTTP/2 client requests a large payload but does not send enough window updates to consume the entire stream and does not reset the stream.
- affected < 1.12.5fixed 1.12.5
Envoy version 1.14.2, 1.13.2, 1.12.4 or earlier may consume excessive amounts of memory when proxying HTTP/2 requests or responses with many small (i.e. 1 byte) data frames.
- affected < 1.14.2fixed 1.14.2
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 *.examp
- affected < 1.12.3fixed 1.12.3
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, possib
- affected <= 1.13.0
CNCF Envoy through 1.13.0 has incorrect Access Control when using SDS with Combined Validation Context. Using the same secret (e.g. trusted CA) across many resources together with the combined validation context could lead to the “static” part of the validation context to be not
- affected <= 1.13.0
CNCF Envoy through 1.13.0 may consume excessive amounts of memory when responding internally to pipelined requests.
- affected <= 1.13.0
CNCF Envoy through 1.13.0 may consume excessive amounts of memory when proxying HTTP/1.1 requests or responses with many small (i.e. 1 byte) chunks.
Page 6 of 6