Threats Tagged 'cve-2024-30255'

Red Hat OpenShift Service Mesh is Red Hat's distribution of the Istio service mesh project, tailored for installation into an OpenShift Container Platform installation. Security Fix(es): * send: Code Execution Vulnerability in Send Library (CVE-2024-43799) * serve-static: Improper Sanitization in serve-static (CVE-2024-43800) * webpack: DOM Clobbering vulnerability in AutoPublicPathRuntimeModule (CVE-2024-43788) * envoy: Envoy incorrectly accepts HTTP 200 response for entering upgrade mode (CVE-2024-23326) * body-parser: Denial of Service Vulnerability in body-parser (CVE-2024-45590) * envoy: Brotli decompressor infinite loop (CVE-2024-32976) * envoy: abnormal termination when using auto_sni with authority header longer than 255 characters (CVE-2024-32475) * envoy: HTTP/2 CPU exhaustion due to CONTINUATION frame flood (CVE-2024-30255) * envoy: Potential to manipulate `x-envoy` headers from external sources (CVE-2024-45806) For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.

Envoy is a cloud-native, open source edge and service proxy. The HTTP/2 protocol stack in Envoy versions prior to 1.29.3, 1.28.2, 1.27.4, and 1.26.8 are vulnerable to CPU exhaustion due to flood of CONTINUATION frames. Envoy's HTTP/2 codec allows the client to send an unlimited number of CONTINUATION frames even after exceeding Envoy's header map limits. This allows an attacker to send a sequence of CONTINUATION frames without the END_HEADERS bit set causing CPU utilization, consuming approximately 1 core per 300Mbit/s of traffic and culminating in denial of service through CPU exhaustion. Users should upgrade to version 1.29.3, 1.28.2, 1.27.4, or 1.26.8 to mitigate the effects of the CONTINUATION flood. As a workaround, disable HTTP/2 protocol for downstream connections.

MediumVulnerabilityGermanyUnited KingdomFrance+5#cve#cve-2024-30255#cwe-390