CVSS: 7.5EPSS: 0%CPEs: 3EXPL: 0CVE-2020-8659 – envoy: Excessive CPU and/or memory usage when proxying HTTP/1.1
https://notcve.org/view.php?id=CVE-2020-8659
CNCF Envoy through 1.13.0 may consume excessive amounts of memory when proxying HTTP/1.1 requests or responses with many small (i.e. 1 byte) chunks. CNCF Envoy versiones hasta 1.13.0, puede consumir cantidades excesivas de memoria cuando se hace proxy a peticiones o respuestas HTTP/1.1 con muchos fragmentos pequeños (es decir, 1 byte). A resource consumption vulnerability was found in the servicemesh-proxy in Envoy. An attacker could send specially crafted small HTTP/1.1 packets that, when processed, could cause excessive amounts of memory to be used, possibly degrading or crashing the application. • https://access.redhat.com/errata/RHSA-2020:0734 https://github.com/envoyproxy/envoy/security/advisories/GHSA-jwcm-4pwp-c2qv https://lists.debian.org/debian-lts-announce/2022/05/msg00025.html https://www.envoyproxy.io/docs/envoy/v1.13.1/intro/version_history https://access.redhat.com/security/cve/CVE-2020-8659 https://bugzilla.redhat.com/show_bug.cgi?id=1802539 • CWE-400: Uncontrolled Resource Consumption CWE-770: Allocation of Resources Without Limits or Throttling •
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
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 https://blog.envoyproxy.io https://github.com/envoyproxy/envoy/commits/master https://github.com/envoyproxy/envoy/security/advisories/GHSA-gxvv-x4p2-rppp https://groups.google.com/forum/#%21forum/envoy-users https://access.redhat.com/security/cve/CVE-2019-18801 https://bugzilla.redhat.com/show_bug.cgi?id=1773444 • 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
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 https://blog.envoyproxy.io https://github.com/envoyproxy/envoy/commits/master https://github.com/envoyproxy/envoy/security/advisories/GHSA-356m-vhw2-wcm4 https://groups.google.com/forum/#%21forum/envoy-users https://access.redhat.com/security/cve/CVE-2019-18802 https://bugzilla.redhat.com/show_bug.cgi?id=1773447 • 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
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.12.0. • https://blog.envoyproxy.io https://github.com/envoyproxy/envoy/commits/master https://github.com/envoyproxy/envoy/security/advisories/GHSA-f2rv-4w6x-rwhc https://groups.google.com/forum/#%21forum/envoy-users https://access.redhat.com/security/cve/CVE-2019-18838 https://bugzilla.redhat.com/show_bug.cgi?id=1773449 • CWE-358: Improperly Implemented Security Check for Standard CWE-476: NULL Pointer Dereference •
CVSS: 7.8EPSS: 0%CPEs: 16EXPL: 0CVE-2019-15226
https://notcve.org/view.php?id=CVE-2019-15226
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-service attack. Al recibir los datos de cada encabezado de petición entrante, Envoy iterará sobre los encabezados de petición existentes para comprobar que el tamaño total de los encabezados permanezca por debajo del límite máximo. La implementación en las versiones 1.10.0 hasta 1.11.1 para el tráfico HTTP/1.x y todas las versiones de Envoy para el tráfico HTTP/2 tenían características de rendimiento O(n^2). • https://github.com/envoyproxy/envoy/commit/afc39bea36fd436e54262f150c009e8d72db5014 https://github.com/envoyproxy/envoy/commits/master https://github.com/envoyproxy/envoy/issues/8520 • CWE-400: Uncontrolled Resource Consumption •