NGINX map directive and regex matching vulnerability
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 1%. Fixed in NGINX Open Source 1.30.6, NGINX Open Source 1.31.7, NGINX Plus * and 2 more.
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
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| F5 | NGINX Open Source | >=1.30.0 <1.30.6, >=1.31.2 <1.31.7 | 1.30.6, 1.31.7 |
| F5 | NGINX Plus | =R33, =R34, =R35, =R36, >=37.0.0 <37.0.5.1, >=37.1.0 <37.1.0.1 | *, 37.0.5.1, 37.1.0.1 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in F5, strongest first
Embed
A live severity badge for an advisory, README or ticket