NGINX map directive and regex matching 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 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.
From the CVE record · f5
NGINX Plus and NGINX Open Source are vulnerable when specific map regex capture variables are referenced before the map output variable, or under certain conditions involving a non-cacheable variable in a string expression. An unauthenticated remote attacker can send crafted HTTP requests to trigger a heap buffer overflow and restart the worker process, causing a denial of service. Code execution is also possible if ASLR is disabled or the attacker can bypass it.
Operators of F5 NGINX Plus or F5 NGINX Open Source should check their deployments; affected versions were not specified.