NGINX ngx_http_core_module vulnerability
F5 NGINX Plus · F5 NGINX Open Source
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| F5 NGINX Plus |
| No fix yet |
| F5 NGINX Open Source |
|
F5 NGINX Plus · F5 NGINX Open Source
| Product | Affected | Fixed in |
|---|---|---|
| F5 NGINX Plus |
| No fix yet |
| F5 NGINX Open Source |
|
| No fix yet |
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.
From the CVE record · f5
NGINX Plus and NGINX Open Source are vulnerable when a location combines alias and rewrite with set or return referencing $request_filename, or when an access log format references that variable. Under conditions beyond their control, an unauthenticated remote attacker can send crafted HTTP requests that cause a worker-process restart; code execution is also possible if ASLR is disabled or bypassed. This is a data-plane issue, not a control-plane exposure.
Operators running F5 NGINX Plus or F5 NGINX Open Source should check their deployments; affected versions were not specified.