CVSS: 7.5EPSS: 0%CPEs: 3EXPL: 0CVE-2020-8663 – envoy: Resource exhaustion when accepting too many connections
https://notcve.org/view.php?id=CVE-2020-8663
01 Jul 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. Envoy versión 1.14.2, 1.13.2, 1.12.4 o anteriores, puede agotar los descriptores de archivo y/o memoria al aceptar demasiadas conexiones A flaw was found in envoy in versions through 1.14.1. Accepting too many connections may lead to an exhaustion of file descriptors and/or memory. The highest threat from this vulnerability is to system availability. Red Hat OpenShift Service Mesh ... • https://github.com/envoyproxy/envoy/security/advisories/GHSA-v8q7-fq78-4997 • CWE-400: Uncontrolled Resource Consumption •
CVSS: 7.5EPSS: 0%CPEs: 3EXPL: 0CVE-2020-12603 – envoy: Resource exhaustion when proxying HTTP/2 requests or responses with small data frames
https://notcve.org/view.php?id=CVE-2020-12603
01 Jul 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. Envoy versiones 1.14.2, 1.13.2, 1.12.4 o anteriores, puede consumir cantidades excesivas de memoria al hacer proxy de peticiones o respuestas HTTP/2 con muchas tramas de datos pequeños (es decir, 1 byte) A flaw was found in Envoy in versions through 1.14.1. An excessive amount of memory may be consumed when proxying HTTP/2 requests and ... • https://github.com/envoyproxy/envoy-setec/issues/80 • CWE-400: Uncontrolled Resource Consumption •
CVSS: 3.1EPSS: 0%CPEs: 2EXPL: 1CVE-2020-11767
https://notcve.org/view.php?id=CVE-2020-11767
15 Apr 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 *.example.com. The outcome should instead be 421 Misdirected Request. Imagine a shared caching forward proxy re-using an HTTP/2 connection for a large subnet with many users. If a victim is interacting with abc.example.com, and a server (f... • https://bugs.chromium.org/p/chromium/issues/detail?id=954160#c5 •
CVSS: 5.3EPSS: 0%CPEs: 2EXPL: 0CVE-2020-8660 – envoy: TLS inspector bypassc
https://notcve.org/view.php?id=CVE-2020-8660
04 Mar 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, possibly bypassing some security restrictions in the process. Una omisión del inspector TLS de CNCF Envoy versiones hasta 1.13.0. El inspector TLS podría haber sido omitido (no reconocido como cliente TLS) por un cliente que usa solo TLS ... • https://access.redhat.com/errata/RHSA-2020:0734 • CWE-345: Insufficient Verification of Data Authenticity CWE-358: Improperly Implemented Security Check for Standard •
CVSS: 9.8EPSS: 0%CPEs: 1EXPL: 1CVE-2019-18801 – envoy: an untrusted remote client may send HTTP/2 requests that write to the heap outside of the request buffers when the upstream is HTTP/1
https://notcve.org/view.php?id=CVE-2019-18801
12 Dec 2019 — An issue was discovered in Envoy 1.12.0. An untrusted remote client may send HTTP/2 requests that write to the heap outside of the request buffers when the upstream is HTTP/1. This may be used to corrupt nearby heap contents (leading to a query-of-death scenario) or may be used to bypass Envoy's access control mechanisms such as path based routing. An attacker can also modify requests from other users that happen to be proximal temporally and spatially. Se detectó un problema en Envoy versión 1.12.0. • https://access.redhat.com/errata/RHSA-2019:4222 • CWE-131: Incorrect Calculation of Buffer Size CWE-787: Out-of-bounds Write •
CVSS: 9.8EPSS: 0%CPEs: 1EXPL: 1CVE-2019-18802 – envoy: malformed request header may cause bypass of route matchers resulting in escalation of privileges or information disclosure
https://notcve.org/view.php?id=CVE-2019-18802
12 Dec 2019 — An issue was discovered in Envoy 1.12.0. An untrusted remote client may send an HTTP header (such as Host) with whitespace after the header content. Envoy will treat "header-value " as a different string from "header-value" so for example with the Host header "example.com " one could bypass "example.com" matchers. Se detectó un problema en Envoy versión 1.12.0. Un cliente remoto no confiable puede enviar un encabezado HTTP (como Host) con espacios en blanco después del contenido del encabezado. • http://lists.opensuse.org/opensuse-security-announce/2020-03/msg00034.html • CWE-284: Improper Access Control •
CVSS: 7.5EPSS: 0%CPEs: 1EXPL: 1CVE-2019-18838 – envoy: malformed HTTP request without the Host header may cause abnormal termination of the Envoy process
https://notcve.org/view.php?id=CVE-2019-18838
12 Dec 2019 — An issue was discovered in Envoy 1.12.0. Upon receipt of a malformed HTTP request without a Host header, it sends an internally generated "Invalid request" response. This internally generated response is dispatched through the configured encoder filter chain before being sent to the client. An encoder filter that invokes route manager APIs that access a request's Host header causes a NULL pointer dereference, resulting in abnormal termination of the Envoy process. Se detectó un problema en Envoy versión 1.1... • https://blog.envoyproxy.io • CWE-358: Improperly Implemented Security Check for Standard CWE-476: NULL Pointer Dereference •
CVSS: 7.5EPSS: 0%CPEs: 2EXPL: 2CVE-2019-18836
https://notcve.org/view.php?id=CVE-2019-18836
11 Nov 2019 — Envoy 1.12.0 allows a remote denial of service because of resource loops, as demonstrated by a single idle TCP connection being able to keep a worker thread in an infinite busy loop when continue_on_listener_filters_timeout is used." Envoy versión 1.12.0 permite una denegación de servicio remota debido a bucles de recursos, como es demostrado por una conexión TCP inactiva que es capaz de mantener un subproceso o hilo de trabajo en un bucle ocupado infinito cuando la función continue_on_listener_filters_time... • https://blog.envoyproxy.io • CWE-835: Loop with Unreachable Exit Condition ('Infinite Loop') •
CVSS: 7.8EPSS: 13%CPEs: 16EXPL: 0CVE-2019-15226
https://notcve.org/view.php?id=CVE-2019-15226
09 Oct 2019 — Upon receiving each incoming request header data, Envoy will iterate over existing request headers to verify that the total size of the headers stays below a maximum limit. The implementation in versions 1.10.0 through 1.11.1 for HTTP/1.x traffic and all versions of Envoy for HTTP/2 traffic had O(n^2) performance characteristics. A remote attacker may craft a request that stays below the maximum request header size but consists of many thousands of small headers to consume CPU and result in a denial-of-serv... • https://github.com/envoyproxy/envoy/commit/afc39bea36fd436e54262f150c009e8d72db5014 • CWE-400: Uncontrolled Resource Consumption •
CVSS: 7.5EPSS: 0%CPEs: 1EXPL: 1CVE-2019-15225
https://notcve.org/view.php?id=CVE-2019-15225
19 Aug 2019 — In Envoy through 1.11.1, users may configure a route to match incoming path headers via the libstdc++ regular expression implementation. A remote attacker may send a request with a very long URI to result in a denial of service (memory consumption). This is a related issue to CVE-2019-14993. En Envoy versiones hasta 1.11.1, los usuarios pueden configurar una ruta (path) para que coincida con los encabezados de ruta (path) entrantes por medio de la implementación de expresiones regulares libstdc++. Un atacan... • https://github.com/envoyproxy/envoy/issues/7728 • CWE-770: Allocation of Resources Without Limits or Throttling •