CVSS: 7.5EPSS: 0%CPEs: 4EXPL: 0CVE-2021-43826 – Crash when tunneling TCP over HTTP in Envoy
https://notcve.org/view.php?id=CVE-2021-43826
Envoy is an open source edge and service proxy, designed for cloud-native applications. In affected versions of Envoy a crash occurs when configured for :ref:`upstream tunneling <envoy_v3_api_field_extensions.filters.network.tcp_proxy.v3.TcpProxy.tunneling_config>` and the downstream connection disconnects while the the upstream connection or http/2 stream is still being established. There are no workarounds for this issue. Users are advised to upgrade. Envoy es un proxy de borde y servicio de código abierto, diseñado para aplicaciones nativas de la nube. • https://github.com/envoyproxy/envoy/commit/ce0ae309057a216aba031aff81c445c90c6ef145 https://github.com/envoyproxy/envoy/security/advisories/GHSA-cmx3-fvgf-83mf https://access.redhat.com/security/cve/CVE-2021-43826 https://bugzilla.redhat.com/show_bug.cgi?id=2050748 • CWE-416: Use After Free •
CVSS: 7.5EPSS: 0%CPEs: 4EXPL: 0CVE-2021-43825 – Use-after-free in Envoy
https://notcve.org/view.php?id=CVE-2021-43825
Envoy is an open source edge and service proxy, designed for cloud-native applications. Sending a locally generated response must stop further processing of request or response data. Envoy tracks the amount of buffered request and response data and aborts the request if the amount of buffered data is over the limit by sending 413 or 500 responses. However when the buffer overflows while response is processed by the filter chain the operation may not be aborted correctly and result in accessing a freed memory block. If this happens Envoy will crash resulting in a denial of service. • https://github.com/envoyproxy/envoy/commit/148de954ed3585d8b4298b424aa24916d0de6136 https://github.com/envoyproxy/envoy/security/advisories/GHSA-h69p-g6xg-mhhh https://access.redhat.com/security/cve/CVE-2021-43825 https://bugzilla.redhat.com/show_bug.cgi?id=2050746 • CWE-416: Use After Free •
CVSS: 7.5EPSS: 0%CPEs: 4EXPL: 0CVE-2022-21655 – Incorrect handling of internal redirects results in crash in Envoy
https://notcve.org/view.php?id=CVE-2022-21655
Envoy is an open source edge and service proxy, designed for cloud-native applications. The envoy common router will segfault if an internal redirect selects a route configured with direct response or redirect actions. This will result in a denial of service. As a workaround turn off internal redirects if direct response entries are configured on the same listener. Envoy es un proxy de borde y servicio de código abierto, diseñado para aplicaciones nativas de la nube. • https://github.com/envoyproxy/envoy/commit/177d608155ba8b11598b9bbf8240e90d8c350682 https://github.com/envoyproxy/envoy/security/advisories/GHSA-7r5p-7fmh-jxpg https://access.redhat.com/security/cve/CVE-2022-21655 https://bugzilla.redhat.com/show_bug.cgi?id=2050757 • CWE-670: Always-Incorrect Control Flow Implementation •
CVSS: 9.8EPSS: 0%CPEs: 4EXPL: 0CVE-2022-21654 – Incorrect configuration handling allows TLS session re-use without re-validation in Envoy
https://notcve.org/view.php?id=CVE-2022-21654
Envoy is an open source edge and service proxy, designed for cloud-native applications. Envoy's tls allows re-use when some cert validation settings have changed from their default configuration. The only workaround for this issue is to ensure that default tls settings are used. Users are advised to upgrade. Envoy es un proxy de borde y servicio de código abierto, diseñado para aplicaciones nativas de la nube. • https://github.com/envoyproxy/envoy/commit/e9f936d85dc1edc34fabd0a1725ec180f2316353 https://github.com/envoyproxy/envoy/security/advisories/GHSA-5j4x-g36v-m283 https://access.redhat.com/security/cve/CVE-2022-21654 https://bugzilla.redhat.com/show_bug.cgi?id=2050753 • CWE-295: Improper Certificate Validation CWE-367: Time-of-check Time-of-use (TOCTOU) Race Condition •
CVSS: 6.8EPSS: 0%CPEs: 3EXPL: 0CVE-2022-21657 – X.509 Extended Key Usage and Trust Purposes bypass in Envoy
https://notcve.org/view.php?id=CVE-2022-21657
Envoy is an open source edge and service proxy, designed for cloud-native applications. In affected versions Envoy does not restrict the set of certificates it accepts from the peer, either as a TLS client or a TLS server, to only those certificates that contain the necessary extendedKeyUsage (id-kp-serverAuth and id-kp-clientAuth, respectively). This means that a peer may present an e-mail certificate (e.g. id-kp-emailProtection), either as a leaf certificate or as a CA in the chain, and it will be accepted for TLS. This is particularly bad when combined with the issue described in pull request #630, in that it allows a Web PKI CA that is intended only for use with S/MIME, and thus exempted from audit or supervision, to issue TLS certificates that will be accepted by Envoy. As a result Envoy will trust upstream certificates that should not be trusted. • https://github.com/envoyproxy/envoy/pull/630 https://github.com/envoyproxy/envoy/security/advisories/GHSA-837m-wjrv-vm5g • CWE-295: Improper Certificate Validation •