CVSS: 7.5EPSS: 0%CPEs: 1EXPL: 1CVE-2019-15225
https://notcve.org/view.php?id=CVE-2019-15225
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 atacante remoto puede enviar una petición con una URI muy larga para resultar en una denegación de servicio (consumo de memoria). • https://github.com/envoyproxy/envoy/issues/7728 • CWE-770: Allocation of Resources Without Limits or Throttling •
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
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 https://github.com/envoyproxy/envoy/security/advisories/GHSA-xcx5-93pw-jw2w https://groups.google.com/forum/#%21topic/envoy-announce/VoHfnDqZiAM https://www.envoyproxy.io/docs/envoy/v1.9.1/intro/version_history https://access.redhat.com/security/cve/CVE-2019-9901 https://bugzilla.redhat.com/show_bug.cgi?id=1698025 • CWE-20: Improper Input Validation CWE-706: Use of Incorrectly-Resolved Name or Reference •
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
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 que contienen caracteres NUL insertados puedan omitir potencialmente las reglas de coincidencia de encabezado, logrando el acceso a recursos no autorizados. A flaw was found in Envoy version 1.9.0 and older, where Envoy does not reject embedded zero characters (NUL, ASCII 0x0) when processing HTTP/1.x header values. • https://access.redhat.com/errata/RHSA-2019:0741 https://github.com/envoyproxy/envoy/issues/6434 https://github.com/envoyproxy/envoy/security/advisories/GHSA-x74r-f4mw-c32h https://groups.google.com/forum/#%21topic/envoy-announce/VoHfnDqZiAM https://www.envoyproxy.io/docs/envoy/v1.9.1/intro/version_history https://access.redhat.com/security/cve/CVE-2019-9900 https://bugzilla.redhat.com/show_bug.cgi?id=1698020 • CWE-20: Improper Input Validation CWE-74: Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection') •