NULL pointer dereference in Envoyproxy Envoy
CVE-2024-53270
Envoy is a cloud-native high-performance edge/middle/service proxy. In affected versions `sendOverloadError` is going to assume the active request exists when `envoy.load_shed_points.http1_server_abort_dispatch` is configured. If `active_request` is nullptr, only onMessageBeginImpl() is called. However, the `onMessageBeginImpl` will directly return ok status if the stream is already reset leading to the nullptr reference. The downstream reset can actually happen during the H/2 upstream reset. As a result envoy may crash. This issue has been addressed in releases 1.32.3, 1.31.5, 1.30.9, and 1.29.12. Users are advised to upgrade. Users unable to upgrade may disable `http1_server_abort_dispatch` load shed point and/or use a high threshold.
Published · last modified .
CVSS v3 metric
CVSS v3 base score 7.5 (High). Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H.
EPSS exploit prediction
EPSS 0.007, 53.6th percentile (scored ); unchanged over 30 days. About EPSS.
Affected products
- Envoyproxy Envoy — versions >= 1.32.0, < 1.32.3, >= 1.31.0, < 1.31.5, >= 1.30.0, < 1.30.9
Weakness classification (CWE)
Public exploits and proof-of-concept code
Also mentioned in 1 other repository (fkie-cad/nvd-json-data-feeds). These reference the CVE in a list, notes or a scanner and are not exploit code for it.
References
- https://github.com/envoyproxy/envoy/security/advisories/GHSA-q9qv-8j52-77p3 (Exploit, Third Party Advisory, Mitigation)
- https://github.com/envoyproxy/envoy/pull/37743/commits/6cf8afda956ba67c9afad185b962325a5242ef02 (Patch)