CVE-2024-23326 – Envoy incorrectly accepts HTTP 200 response for entering upgrade mode
https://notcve.org/view.php?id=CVE-2024-23326
Envoy is a cloud-native, open source edge and service proxy. A theoretical request smuggling vulnerability exists through Envoy if a server can be tricked into adding an upgrade header into a response. Per RFC https://www.rfc-editor.org/rfc/rfc7230#section-6.7 a server sends 101 when switching protocols. Envoy incorrectly accepts a 200 response from a server when requesting a protocol upgrade, but 200 does not indicate protocol switch. This opens up the possibility of request smuggling through Envoy if the server can be tricked into adding the upgrade header to the response. • https://github.com/envoyproxy/envoy/security/advisories/GHSA-vcf8-7238-v74c https://access.redhat.com/security/cve/CVE-2024-23326 https://bugzilla.redhat.com/show_bug.cgi?id=2259228 • CWE-391: Unchecked Error Condition CWE-444: Inconsistent Interpretation of HTTP Requests ('HTTP Request/Response Smuggling') •
CVE-2024-32475 – Envoy RELEASE_ASSERT using auto_sni with :authority header > 255 bytes
https://notcve.org/view.php?id=CVE-2024-32475
Envoy is a cloud-native, open source edge and service proxy. When an upstream TLS cluster is used with `auto_sni` enabled, a request containing a `host`/`:authority` header longer than 255 characters triggers an abnormal termination of Envoy process. Envoy does not gracefully handle an error when setting SNI for outbound TLS connection. The error can occur when Envoy attempts to use the `host`/`:authority` header value longer than 255 characters as SNI for outbound TLS connection. SNI length is limited to 255 characters per the standard. • https://github.com/envoyproxy/envoy/commit/b47fc6648d7c2dfe0093a601d44cb704b7bad382 https://github.com/envoyproxy/envoy/security/advisories/GHSA-3mh5-6q8v-25wj https://access.redhat.com/security/cve/CVE-2024-32475 https://bugzilla.redhat.com/show_bug.cgi?id=2276149 • CWE-253: Incorrect Check of Function Return Value CWE-617: Reachable Assertion •
CVE-2020-25018
https://notcve.org/view.php?id=CVE-2020-25018
Envoy master between 2d69e30 and 3b5acb2 may fail to parse request URL that requires host canonicalization. Envoy master versiones entre 2d69e30 y 3b5acb2, puede presentar un fallo al analizar una URL de petición que requiere la canonicalización del host • https://github.com/envoyproxy/envoy/security/advisories/GHSA-fwwh-fc9w-9673 https://groups.google.com/forum/#%21forum/envoy-security-announce •
CVE-2019-7678
https://notcve.org/view.php?id=CVE-2019-7678
A directory traversal vulnerability was discovered in Enphase Envoy R3.*.* via images/, include/, include/js, or include/css on TCP port 8888. Se ha descubierto una vulnerabilidad de salto de directorio en Enphase Envoy R3.*.* mediante images/, include/, include/js o include/css en el puerto TCP 8888. • https://github.com/pudding2/enphase-energy/blob/master/directory_traversal_1.png https://github.com/pudding2/enphase-energy/blob/master/directory_traversal_exp.txt • CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') •
CVE-2019-7677
https://notcve.org/view.php?id=CVE-2019-7677
XSS exists in Enphase Envoy R3.*.* via the profileName parameter to the /home URI on TCP port 8888. Existe Cross-Site Scripting (XSS) en Enphase Envoy R3.*.* mediante el parámetro profileName en el URI /home en el puerto TCP 8888. • https://github.com/pudding2/enphase-energy/blob/master/XSS-exp.txt https://github.com/pudding2/enphase-energy/blob/master/XSS.png • CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') •