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 •
CVSS: 7.4EPSS: 0%CPEs: 1EXPL: 0CVE-2022-21656 – X.509 subjectAltName matching bypass in Envoy
https://notcve.org/view.php?id=CVE-2022-21656
Envoy is an open source edge and service proxy, designed for cloud-native applications. The default_validator.cc implementation used to implement the default certificate validation routines has a "type confusion" bug when processing subjectAltNames. This processing allows, for example, an rfc822Name or uniformResourceIndicator to be authenticated as a domain name. This confusion allows for the bypassing of nameConstraints, as processed by the underlying OpenSSL/BoringSSL implementation, exposing the possibility of impersonation of arbitrary servers. As a result Envoy will trust upstream certificates that should not be trusted. • https://github.com/envoyproxy/envoy/commit/bb95af848c939cfe5b5ee33c5b1770558077e64e https://github.com/envoyproxy/envoy/security/advisories/GHSA-c9g7-xwcv-pjx2 • CWE-295: Improper Certificate Validation CWE-843: Access of Resource Using Incompatible Type ('Type Confusion') •
CVSS: 6.5EPSS: 0%CPEs: 2EXPL: 0CVE-2022-23606 – Crash when a cluster is deleted in Envoy
https://notcve.org/view.php?id=CVE-2022-23606
Envoy is an open source edge and service proxy, designed for cloud-native applications. When a cluster is deleted via Cluster Discovery Service (CDS) all idle connections established to endpoints in that cluster are disconnected. A recursion was introduced in the procedure of disconnecting idle connections that can lead to stack exhaustion and abnormal process termination when a cluster has a large number of idle connections. This infinite recursion causes Envoy to crash. Users are advised to upgrade. • https://github.com/envoyproxy/envoy/commit/4b6dd3b53cd5c6d4d4df378a2fc62c1707522b31 https://github.com/envoyproxy/envoy/security/advisories/GHSA-9vp2-4cp7-vvxf https://access.redhat.com/security/cve/CVE-2022-23606 https://bugzilla.redhat.com/show_bug.cgi?id=2050758 • CWE-674: Uncontrolled Recursion CWE-770: Allocation of Resources Without Limits or Throttling •
CVSS: 7.5EPSS: 0%CPEs: 4EXPL: 0CVE-2021-43824 – Null pointer dereference in envoy
https://notcve.org/view.php?id=CVE-2021-43824
Envoy is an open source edge and service proxy, designed for cloud-native applications. In affected versions a crafted request crashes Envoy when a CONNECT request is sent to JWT filter configured with regex match. This provides a denial of service attack vector. The only workaround is to not use regex in the JWT filter. Users are advised to upgrade. • https://github.com/envoyproxy/envoy/commit/9371333230b1a6e1be2eccf4868771e11af6253a https://github.com/envoyproxy/envoy/security/advisories/GHSA-vj5m-rch8-5r2p https://access.redhat.com/security/cve/CVE-2021-43824 https://bugzilla.redhat.com/show_bug.cgi?id=2050744 • CWE-476: NULL Pointer Dereference •
CVSS: 8.6EPSS: 0%CPEs: 6EXPL: 0CVE-2021-39206 – Incorrect Authorization with specially crafted requests
https://notcve.org/view.php?id=CVE-2021-39206
Pomerium is an open source identity-aware access proxy. Envoy, which Pomerium is based on, contains two authorization related vulnerabilities CVE-2021-32777 and CVE-2021-32779. This may lead to incorrect routing or authorization policy decisions. With specially crafted requests, incorrect authorization or routing decisions may be made by Pomerium. Pomerium v0.14.8 and v0.15.1 contain an upgraded envoy binary with these vulnerabilities patched. • https://github.com/envoyproxy/envoy/security/advisories/GHSA-6g4j-5vrw-2m8h https://github.com/envoyproxy/envoy/security/advisories/GHSA-r222-74fw-jqr9 https://github.com/pomerium/pomerium/security/advisories/GHSA-cfc2-wjcm-c8fm https://groups.google.com/g/envoy-announce/c/5xBpsEZZDfE/m/wD05NZBbAgAJ • CWE-863: Incorrect Authorization •