Page 4 of 57 results (0.008 seconds)

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

24 Aug 2021 — Envoy is an open source L7 proxy and communication bus designed for large modern service oriented architectures. In affected versions envoy incorrectly handled a URI '#fragment' element as part of the path element. Envoy is configured with an RBAC filter for authorization or similar mechanism with an explicit case of a final "/admin" path element, or is using a negative assertion with final path element of "/admin". The client sends request to "/app1/admin#foo". In Envoy prior to 1.18.0, or 1.18.0+ configur... • https://github.com/envoyproxy/envoy/security/advisories/GHSA-r222-74fw-jqr9 • CWE-551: Incorrect Behavior Order: Authorization Before Parsing and Canonicalization CWE-697: Incorrect Comparison CWE-863: Incorrect Authorization •

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

24 Aug 2021 — Envoy is an open source L7 proxy and communication bus designed for large modern service oriented architectures. In affected versions envoy’s procedure for resetting a HTTP/2 stream has O(N^2) complexity, leading to high CPU utilization when a large number of streams are reset. Deployments are susceptible to Denial of Service when Envoy is configured with high limit on H/2 concurrent streams. An attacker wishing to exploit this vulnerability would require a client opening and closing a large number of H/2 s... • https://github.com/envoyproxy/envoy/security/advisories/GHSA-3xh3-33v5-chcc • CWE-834: Excessive Iteration •

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

24 Aug 2021 — Envoy is an open source L7 proxy and communication bus designed for large modern service oriented architectures. In affected versions when ext-authz extension is sending request headers to the external authorization service it must merge multiple value headers according to the HTTP spec. However, only the last header value is sent. This may allow specifically crafted requests to bypass authorization. Attackers may be able to escalate privileges when using ext-authz extension or back end service that uses mu... • https://github.com/envoyproxy/envoy/security/advisories/GHSA-6g4j-5vrw-2m8h • CWE-551: Incorrect Behavior Order: Authorization Before Parsing and Canonicalization CWE-863: Incorrect Authorization •

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: 7.5EPSS: 0%CPEs: 4EXPL: 0

22 Apr 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. Se detectó un problema en Envoy versión 1.14.0. Se presenta un bloqueo explotable remoto para unos metadatos HTTP2, porque un mapa de METADATOS vacío desencadena un Reachable Assertion A flaw was found in envoyproxy. An attacker, able to craft an HTTP2 request that specifies an empty metadata map, can crash envoy resulting in a denial of servic... • https://blog.envoyproxy.io • CWE-476: NULL Pointer Dereference CWE-617: Reachable Assertion •

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

22 Apr 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. Se detectó un problema en Envoy versiones hasta 1.71.1. presenta un desbordamiento de enteros explotable remoto en el que un valor de grpc-timeout muy grande conlleva a cálculos de tiempo de espera inesperados A flaw was found in envoyproxy/envoy. An attacker, able to craft a packet which specifies a large grpc-timeout, can ... • https://blog.envoyproxy.io • CWE-190: Integer Overflow or Wraparound •

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 •

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

30 Sep 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. Envoy versiones hasta 1.15.0, solo considera el primer valor cuando múltiples valores de encabezado están presentes para algunos encabezados HTTP. La API de mapa de encabezado de la función setCopy() de Envoy no reemplaza todas las ocurrencias existentes de un encabezado no en línea An incorre... • https://github.com/envoyproxy/envoy/security/advisories/GHSA-2v25-cjjq-5f4w • CWE-284: Improper Access Control •

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

14 Jul 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.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 vulnerability is only a... • https://github.com/envoyproxy/envoy/security/advisories/GHSA-w5f5-6qhq-hhrg • CWE-297: Improper Validation of Certificate with Host Mismatch CWE-346: Origin Validation Error •