CVSS: 5.3EPSS: 0%CPEs: 4EXPL: 2CVE-2024-30255 – HTTP/2: CPU exhaustion due to CONTINUATION frame flood
https://notcve.org/view.php?id=CVE-2024-30255
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. • https://github.com/lockness-Ko/CVE-2024-27316 https://github.com/blackmagic2023/Envoy-CPU-Exhaustion-Vulnerability-PoC http://www.openwall.com/lists/oss-security/2024/04/03/16 http://www.openwall.com/lists/oss-security/2024/04/05/3 https://github.com/envoyproxy/envoy/security/advisories/GHSA-j654-3ccm-vfmm https://access.redhat.com/security/cve/CVE-2024-30255 https://bugzilla.redhat.com/show_bug.cgi?id=2272986 • CWE-390: Detection of Error Condition Without Action •
CVSS: 7.5EPSS: 0%CPEs: 4EXPL: 0CVE-2024-23322 – Envoy crashes when idle and request per try timeout occur within the backoff interval
https://notcve.org/view.php?id=CVE-2024-23322
Envoy is a high-performance edge/middle/service proxy. Envoy will crash when certain timeouts happen within the same interval. The crash occurs when the following are true: 1. hedge_on_per_try_timeout is enabled, 2. per_try_idle_timeout is enabled (it can only be done in configuration), 3. per-try-timeout is enabled, either through headers or configuration and its value is equal, or within the backoff interval of the per_try_idle_timeout. This issue has been addressed in released 1.29.1, 1.28.1, 1.27.3, and 1.26.7. Users are advised to upgrade. • https://github.com/envoyproxy/envoy/commit/843f9e6a123ed47ce139b421c14e7126f2ac685e https://github.com/envoyproxy/envoy/security/advisories/GHSA-6p83-mfmh-qv38 • CWE-416: Use After Free •
CVSS: 5.3EPSS: 0%CPEs: 4EXPL: 0CVE-2024-23323 – Excessive CPU usage when URI template matcher is configured using regex in Envoy
https://notcve.org/view.php?id=CVE-2024-23323
Envoy is a high-performance edge/middle/service proxy. The regex expression is compiled for every request and can result in high CPU usage and increased request latency when multiple routes are configured with such matchers. This issue has been addressed in released 1.29.1, 1.28.1, 1.27.3, and 1.26.7. Users are advised to upgrade. There are no known workarounds for this vulnerability. • https://github.com/envoyproxy/envoy/commit/71eeee8f0f0132f39e402b0ee23b361ee2f4e645 https://github.com/envoyproxy/envoy/security/advisories/GHSA-x278-4w4x-r7ch • CWE-400: Uncontrolled Resource Consumption CWE-1176: Inefficient CPU Computation •
CVSS: 8.6EPSS: 0%CPEs: 4EXPL: 0CVE-2024-23324 – Envoy ext auth can be bypassed when Proxy protocol filter sets invalid UTF-8 metadata
https://notcve.org/view.php?id=CVE-2024-23324
Envoy is a high-performance edge/middle/service proxy. External authentication can be bypassed by downstream connections. Downstream clients can force invalid gRPC requests to be sent to ext_authz, circumventing ext_authz checks when failure_mode_allow is set to true. This issue has been addressed in released 1.29.1, 1.28.1, 1.27.3, and 1.26.7. Users are advised to upgrade. • https://github.com/envoyproxy/envoy/commit/29989f6cc8bfd8cd2ffcb7c42711eb02c7a5168a https://github.com/envoyproxy/envoy/security/advisories/GHSA-gq3v-vvhj-96j6 • CWE-20: Improper Input Validation •
CVSS: 7.5EPSS: 0%CPEs: 4EXPL: 0CVE-2024-23325 – Envoy crashes when using an address type that isn’t supported by the OS
https://notcve.org/view.php?id=CVE-2024-23325
Envoy is a high-performance edge/middle/service proxy. Envoy crashes in Proxy protocol when using an address type that isn’t supported by the OS. Envoy is susceptible to crashing on a host with IPv6 disabled and a listener config with proxy protocol enabled when it receives a request where the client presents its IPv6 address. It is valid for a client to present its IPv6 address to a target server even though the whole chain is connected via IPv4. This issue has been addressed in released 1.29.1, 1.28.1, 1.27.3, and 1.26.7. • https://github.com/envoyproxy/envoy/commit/bacd3107455b8d387889467725eb72aa0d5b5237 https://github.com/envoyproxy/envoy/security/advisories/GHSA-5m7c-mrwr-pm26 • CWE-248: Uncaught Exception CWE-755: Improper Handling of Exceptional Conditions •