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.
NGINX heap overflow via alias and $request_filename
A heap buffer overflow (CWE-122) exists in NGINX Plus and NGINX Open Source when a location uses the alias directive together with rewrite and a set or return directive that references $request_filename, or when $request_filename is used in an access-log format. An unauthenticated remote attacker can send crafted HTTP requests, but only if those configuration conditions are already present, and overflow a buffer in the NGINX worker process. The worker can crash and restart, causing a denial of service, and code execution may be possible on systems where ASLR is disabled or can be bypassed; this is a data-plane issue only, with no control-plane exposure. Exact affected version ranges are not stated in the provided advisory data, and End-of-Technical-Support releases were not evaluated. It is not listed in CISA KEV, and no public proof-of-concept is known.
What to do: Apply the vendor's fixed NGINX Open Source and NGINX Plus builds as soon as they are available for your supported release, and treat End-of-Technical-Support releases as unassessed. Until then, review location blocks that combine alias with rewrite and set or return using $request_filename, and access_log formats that reference $request_filename, and remove or change those patterns. Keep ASLR enabled and watch worker processes for unexpected restarts.
| Product | Affected |
|---|---|
| F5 NGINX Open Source | — |
| F5 NGINX Plus | — |
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 location is configured that uses the alias directive together with rewrite and a set or return directive referencing the $request_filename variable. Alternatively, the same result could be achieved when the $request_filename variable is used in an access log format directive. 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.
Canada’s Cyber Centre urges updates for multiple NGINX and F5 products affected by three new CVEs.
Today 2.2K readers · 2.8K views · 404 reads · all time 108K views