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
04 Mar 2020 — 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 ... • https://access.redhat.com/errata/RHSA-2020:0734 • CWE-400: Uncontrolled Resource Consumption CWE-770: Allocation of Resources Without Limits or Throttling •
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: 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: 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.8EPSS: 0%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 •
CVSS: 8.3EPSS: 0%CPEs: 2EXPL: 2CVE-2019-9900 – istio/envoy: Authorization bypass via null characters injection in HTTP/1.x
https://notcve.org/view.php?id=CVE-2019-9900
11 Apr 2019 — When parsing HTTP/1.x header values, Envoy 1.9.0 and before does not reject embedded zero characters (NUL, ASCII 0x0). This allows remote attackers crafting header values containing embedded NUL characters to potentially bypass header matching rules, gaining access to unauthorized resources. Al analizar los valores de encabezado HTTP/1.x, Envoy versión 1.9.0 y anteriores, no rechazan los caracteres de cero incrustados (NUL, ASCII 0x0). Esto permite que los atacantes remotos que crean valores de encabezado q... • https://access.redhat.com/errata/RHSA-2019:0741 • CWE-20: Improper Input Validation CWE-74: Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection') •
CVSS: 10.0EPSS: 0%CPEs: 1EXPL: 0CVE-2019-9901 – istio/envoy: Path traversal via URL Patch manipulation in HTTP/1.x header
https://notcve.org/view.php?id=CVE-2019-9901
11 Apr 2019 — Envoy 1.9.0 and before does not normalize HTTP URL paths. A remote attacker may craft a relative path, e.g., something/../admin, to bypass access control, e.g., a block on /admin. A backend server could then interpret the non-normalized path and provide an attacker access beyond the scope provided for by the access control policy. Envoy versión 1.9.0 y anteriores no normalizan las path URL HTTP. • https://github.com/envoyproxy/envoy/issues/6435 • CWE-20: Improper Input Validation CWE-706: Use of Incorrectly-Resolved Name or Reference •