Page 3 of 48 results (0.010 seconds)

CVSS: 7.5EPSS: 0%CPEs: 4EXPL: 0

22 Feb 2022 — 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 • CWE-670: Always-Incorrect Control Flow Implementation •

CVSS: 6.8EPSS: 0%CPEs: 3EXPL: 0

22 Feb 2022 — 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 accepte... • https://github.com/envoyproxy/envoy/pull/630 • CWE-295: Improper Certificate Validation •

CVSS: 7.4EPSS: 0%CPEs: 1EXPL: 0

22 Feb 2022 — 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 possibi... • https://github.com/envoyproxy/envoy/commit/bb95af848c939cfe5b5ee33c5b1770558077e64e • CWE-295: Improper Certificate Validation CWE-843: Access of Resource Using Incompatible Type ('Type Confusion') •

CVSS: 7.5EPSS: 0%CPEs: 4EXPL: 0

22 Feb 2022 — 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 • CWE-476: NULL Pointer Dereference •

CVSS: 8.6EPSS: 0%CPEs: 6EXPL: 0

09 Sep 2021 — 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 • CWE-863: Incorrect Authorization •

CVSS: 7.5EPSS: 0%CPEs: 6EXPL: 0

09 Sep 2021 — Pomerium is an open source identity-aware access proxy. Envoy, which Pomerium is based on, incorrectly handles resetting of HTTP/2 streams with excessive complexity. This can lead to high CPU utilization when a large number of streams are reset. This can result in a DoS condition. Pomerium versions 0.14.8 and 0.15.1 contain an upgraded envoy binary with this vulnerability patched. • https://github.com/envoyproxy/envoy/security/advisories/GHSA-3xh3-33v5-chcc • CWE-834: Excessive Iteration •

CVSS: 8.6EPSS: 0%CPEs: 3EXPL: 0

09 Sep 2021 — Pomerium is an open source identity-aware access proxy. Envoy, which Pomerium is based on, can abnormally terminate if an H/2 GOAWAY and SETTINGS frame are received in the same IO event. This can lead to a DoS in the presence of untrusted *upstream* servers. 0.15.1 contains an upgraded envoy binary with this vulnerability patched. If only trusted upstreams are configured, there is not substantial risk of this condition being triggered. Pomerium es un proxy de acceso de código abierto consciente de la identi... • https://github.com/envoyproxy/envoy/security/advisories/GHSA-j374-mjrw-vvp8 • CWE-754: Improper Check for Unusual or Exceptional Conditions •

CVSS: 8.3EPSS: 0%CPEs: 4EXPL: 0

12 May 2021 — Envoy is a cloud-native edge/middle/service proxy. Envoy does not decode escaped slash sequences `%2F` and `%5C` in HTTP URL paths in versions 1.18.2 and before. A remote attacker may craft a path with escaped slashes, e.g. `/something%2F..%2Fadmin`, to bypass access control, e.g. a block on `/admin`. A backend server could then decode slash sequences and normalize path and provide an attacker access beyond the scope provided for by the access control policy. ### Impact Escalation of Privileges when using R... • https://github.com/envoyproxy/envoy/security/advisories/GHSA-4987-27fx-x6cf • CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') CWE-863: Incorrect Authorization •

CVSS: 8.8EPSS: 0%CPEs: 1EXPL: 0

15 Dec 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). Envoy versiones anteriores a 1.16.1, registra una dirección posterior incorrecta porque considera solo al peer conectado directamente, no la información en el encabezado proxy protocol. Esto afecta situaciones con tcp-proxy como filtro de red (no filtros HTTP) • https://github.com/envoyproxy/envoy/compare/v1.16.0...v1.16.1 •

CVSS: 7.5EPSS: 0%CPEs: 1EXPL: 1

15 Dec 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. Envoy versiones anteriores a 1.16.1, maneja inapropiadamente datagramas perdidos y truncados, como es demostrado por un fallo de segmentación para un tamaño de paquete UDP más largo que 1500 • https://github.com/envoyproxy/envoy/compare/v1.16.0...v1.16.1 •