F5 NGINX Plus and Open Source denial of service and possible RCE in mail proxy
F5 NGINX Plus · F5 NGINX Open Source
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| F5 NGINX Plus |
| No fix yet |
| F5 NGINX Open Source |
| No fix yet |
F5 NGINX Plus · F5 NGINX Open Source
| Product | Affected | Fixed in |
|---|---|---|
| F5 NGINX Plus |
| No fix yet |
| F5 NGINX Open Source |
| No fix yet |
When NGINX Plus or NGINX Open Source is configured as a mail proxy, undisclosed traffic can cause a use-after-free in an nginx worker process. Additionally, attackers can execute code on systems with Address Space Layout Randomization (ASLR) disabled or when the attacker can bypass ASLR.
Impact: A remote unauthenticated attacker may crash an nginx worker process or corrupt its memory, disrupting service. Remote code execution is a potential impact. 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 configured as mail proxies have a use-after-free in an nginx worker process. A remote, unauthenticated attacker can send traffic that crashes a worker or corrupts its memory, disrupting service. Code execution is possible if ASLR is disabled or the attacker can bypass it; this affects the data plane, not the control plane.
Operators of F5 NGINX Plus or F5 NGINX Open Source configured as mail proxies should check their deployments; affected versions were not specified.