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.5EPSS: 0%CPEs: 2EXPL: 2CVE-2019-18836
https://notcve.org/view.php?id=CVE-2019-18836
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_timeout es usada. • https://blog.envoyproxy.io https://github.com/envoyproxy/envoy/security/advisories/GHSA-3xvf-4396-cj46 https://github.com/istio/istio/issues/18229 https://groups.google.com/forum/#%21forum/envoy-users • CWE-835: Loop with Unreachable Exit Condition ('Infinite Loop') •
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 •
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 •