REDHAT-BUG-2575981: Use After Free
This issue occurs when NGINX Plus or NGINX Open Source is configured as a proxy, the proxied server name includes variables, and a Server Side Includes (SSI) or mirror directive sends a subrequest to a location that resolves the same server name. Under these conditions, a specially crafted HTTP request may cause a use-after-free condition in a worker process. An attacker may also be able to execute code if Address Space Layout Randomization (ASLR) is disabled or the attacker can bypass ASLR.
Impact: An attacker could leverage this vulnerability to crash the NGINX worker process, corrupt its memory, or perform remote code execution (RCE)
Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated.
Affected Software
Event History
Frequently Asked Questions
Which deployments are exposed to this issue?
Deployments of NGINX Plus or NGINX Open Source are exposed only when configured as a proxy with variables in the proxied server name, and an SSI or mirror directive can send a subrequest to a location that resolves that same server name.
What does an attacker need to do to trigger the vulnerability?
An attacker needs to send a specially crafted HTTP request to a deployment meeting the affected configuration conditions. The issue is triggered through the resulting subrequest behavior and can cause a use-after-free condition in an NGINX worker process.
Is remote code execution always possible?
No. The issue can crash a worker process or corrupt memory, while code execution may be possible if ASLR is disabled or if the attacker can bypass ASLR.
What configuration should be reviewed while patching is pending?
Review proxy configurations for proxied server names containing variables, then identify SSI or mirror directives that generate subrequests to locations resolving to the same server name. Configurations that do not combine these conditions are not described as affected.