F5 NGINX Plus and Open Source denial of service and possible RCE in HTTP/2
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 |
This issue affects NGINX Plus or NGINX Open Source configurations that use HTTP/2. When NGINX processes undisclosed traffic, the flow control window can exceed the allowed threshold, potentially resulting in a heap buffer overflow typically followed by an NGINX worker segmentation fault. Additionally, attackers can execute code on systems with Address Space Layout Randomization (ASLR) disabled or when the attacker can bypass ASLR.
Impact: An attacker could leverage this vulnerability to crash the NGINX worker process, corrupt its memory, or potentially execute code remotely. 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 configurations using HTTP/2 are vulnerable when processing undisclosed data-plane traffic. A remote attacker could crash an NGINX worker or corrupt its memory, and could potentially execute code if ASLR is disabled or bypassed. The input does not specify whether authentication or user interaction is required.
Operators running F5 NGINX Plus or F5 NGINX Open Source with HTTP/2 should check their deployments; affected versions are not specified, and versions past End of Technical Support were not evaluated.