F5 NGINX Plus
NGINX map directive and regex matching vulnerability
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.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- >= 37.1.0, < 37.1.0.1
- >= 37.0.0, < 37.0.5.1
- >= R36, < *
- >= R35, < *
- >= R34, < *
- >= R33, < *
Fixed in 37.1.0.1, 37.0.5.1, *
- >= 1.31.2, < 1.31.7
- >= 1.30.0, < 1.30.6
Fixed in 1.31.7, 1.30.6
Mitigation
Upgrade NGINX Plus to 37.1.0.1 or 37.0.5.1 or * or later.
Upgrade NGINX Open Source to 1.31.7 or 1.30.6 or later.
Workaround
To mitigate this vulnerability, do not use unnamed captures. Use named captures instead and limit their usage to the block with the regex match.
References
- Vendor advisory my.f5.com/manage/s/article/K000162607
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.