F5 ships out-of-band patches for critical NGINX flaws
Three critical bugs can crash NGINX or, if ASLR is off or bypassed, allow code execution; F5 reports no exploitation.
Heap buffer overflow in NGINX map regex handling
NGINX Open Source and NGINX Plus contain a heap buffer overflow (CWE-122) in the worker process when a map directive uses regex matching and root or an access-log format references the map's regex capture variables before the map output variable, or when a non-cacheable variable is used in a string expression under certain conditions. An unauthenticated remote attacker can trigger it with crafted HTTP requests, but only when that configuration is already present—conditions the attacker does not control. Successful exploitation restarts the worker (denial of service) and can lead to code execution on systems where ASLR is disabled or can be bypassed; this is a data-plane issue only, with no control-plane exposure. Both NGINX Open Source and NGINX Plus are affected; exact version ranges were not published in the advisory data, and End of Technical Support releases were not evaluated. It is scored CVSS 4.0 9.2 (critical). It is not listed in CISA KEV, and no public proof-of-concept is known.
What to do: Apply the fixed NGINX Open Source and NGINX Plus builds from F5 as soon as they are available for your supported release; End of Technical Support versions were not evaluated. Until then, review configs for map blocks that use regex captures and for root or log_format (or other string expressions) that reference those capture variables before the map output variable, and remove or reorder that pattern. Keep ASLR enabled on NGINX hosts so a worker crash is limited to a restart rather than a realistic code-execution path.
| Product | Affected |
|---|---|
| F5 NGINX Open Source | Affected versions not enumerated in the advisory data; releases past End of Technical Support were not evaluated |
| F5 NGINX Plus | Affected versions not enumerated in the advisory data; releases past End of Technical Support were not evaluated |
Order-of-magnitude estimate by the model from install counts, market share and public scan data it knows; verify before quoting.
A vulnerability exists in NGINX Plus and NGINX Open Source when a map directive uses regex matching and the root directive or access log format references the map's regex capture variables before referencing the map output variable. Alternatively, the same result could be achieved by using a non-cacheable variable in a string expression under certain conditions. An unauthenticated attacker along with conditions beyond their control can exploit this vulnerability by sending crafted HTTP requests. This may cause a heap buffer overflow in the NGINX worker process leading to a restart. Additionally, attackers can execute code on systems with Address Space Layout Randomization (ASLR) disabled or when the attacker can bypass ASLR. Impact: This vulnerability may allow remote attackers to cause a denial-of-service (DoS) on the NGINX system or to possibly trigger a code execution. There is no control plane exposure; this is a data plane issue only. Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated.
Three critical bugs can crash NGINX or, if ASLR is off or bypassed, allow code execution; F5 reports no exploitation.
All three CVEs score 9.2; F5 says it has found no evidence of exploitation and urges upgrades.
F5 patched three critical NGINX flaws that can allow unauthenticated remote code execution.
NGINX 1.30.6 and 1.31.7 fix five flaws, including possible worker RCE and a TLS client-cert bypass.
An oss-security post says at least two F5-published nginx issues may allow remote code execution.
F5 and Juniper patched critical NGINX and Junos flaws that can lead to remote code execution.
Today 2.2K readers · 2.8K views · 404 reads · all time 108K views