Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2024-31079 Overview
CVE-2024-31079 affects NGINX Plus and NGINX Open Source when configured to use the experimental HTTP/3 QUIC module. Undisclosed HTTP/3 requests can terminate NGINX worker processes or cause other potential impact. The flaw is associated with stack-based buffer overflow [CWE-121] and out-of-bounds write [CWE-787] conditions during HTTP/3 request handling.
Exploitation requires precise timing during the connection draining process, which the attacker cannot directly observe and has limited ability to influence. F5 published advisory K000139611 and Fedora released package updates for Fedora 39 and 40.
Critical Impact
A remote unauthenticated attacker can trigger NGINX worker process termination, resulting in service disruption for connections handled by the affected worker.
Affected Products
- F5 NGINX Open Source with HTTP/3 QUIC module enabled
- F5 NGINX Plus R30 (including p1, p2) and R31 (including p1)
- Fedora Project Fedora 39 and 40
Discovery Timeline
- 2024-05-29 - CVE-2024-31079 published to NVD
- 2024-05-30 - Public discussion on Openwall OSS Security mailing list
- 2025-01-24 - Last updated in NVD database
Technical Details for CVE-2024-31079
Vulnerability Analysis
The vulnerability resides in the HTTP/3 QUIC module shipped with NGINX. When the module processes specifically crafted HTTP/3 requests timed against an active connection draining state, the worker process can write outside the bounds of an allocated stack buffer. This results in memory corruption leading to worker termination.
The HTTP/3 QUIC module is marked experimental in upstream NGINX. Operators who explicitly enable QUIC listeners and the http_v3_module are exposed. Successful exploitation does not require authentication or user interaction, but the attack complexity is high because the request must align with the connection draining window.
Root Cause
The root cause involves improper bounds checking during HTTP/3 request processing, classified as a stack-based buffer overflow [CWE-121] and out-of-bounds write [CWE-787]. NGINX worker processes handle untrusted client data through the QUIC state machine without sufficient validation when a connection enters the draining state, allowing memory corruption.
Attack Vector
The attack vector is network-based. A remote attacker sends crafted HTTP/3 requests to an NGINX endpoint listening on a QUIC port. The attacker must time the requests to coincide with the connection draining phase. Since the attacker has no visibility into draining state transitions, exploitation typically requires repeated attempts. Successful exploitation terminates the worker process or causes other undefined behavior.
No public proof-of-concept exploit code is available for this vulnerability. Refer to the F5 Security Article K000139611 and the Openwall OSS Security Discussion for vendor technical details.
Detection Methods for CVE-2024-31079
Indicators of Compromise
- Unexpected NGINX worker process crashes or restarts logged in system journals or error.log entries referencing ngx_http_v3 or quic modules.
- Repeated short-lived HTTP/3 connections from a single source followed by abnormal connection resets during draining.
- Core dumps generated by NGINX worker processes on hosts with QUIC listeners enabled.
Detection Strategies
- Monitor NGINX error.log for worker process exit messages, SIGSEGV signals, or QUIC-related assertion failures.
- Inspect process supervisor logs (systemd, supervisord) for unexpected NGINX worker respawns on hosts running affected versions.
- Compare deployed NGINX versions against the F5 advisory K000139611 and flag hosts running R30, R30 p1, R30 p2, R31, or R31 p1 with HTTP/3 enabled.
Monitoring Recommendations
- Track worker process uptime metrics and alert on abnormal termination rates on QUIC-enabled hosts.
- Capture QUIC traffic patterns at the network edge and baseline normal HTTP/3 request volumes per source.
- Enable verbose logging on ngx_http_v3_module in non-production to identify malformed HTTP/3 frame patterns for tuning detections.
How to Mitigate CVE-2024-31079
Immediate Actions Required
- Upgrade NGINX Plus to R31 p2 or R32, or upgrade NGINX Open Source to a version that includes the HTTP/3 QUIC fix as documented in F5 advisory K000139611.
- Apply the Fedora package updates referenced in the Fedora package announcements for Fedora 39 and 40.
- If patching cannot be performed immediately, disable the HTTP/3 QUIC module on production NGINX instances.
Patch Information
F5 published remediation guidance in advisory K000139611. Fedora published updated packages through the Fedora Package Announcement for Fedora 39 and the Fedora Package Announcement for Fedora 40. Verify installed package versions after applying updates.
Workarounds
- Remove listen ... quic directives from nginx.conf server blocks to disable HTTP/3 endpoints until patches are applied.
- Rebuild NGINX Open Source without the --with-http_v3_module compile flag where HTTP/3 is not required.
- Block inbound UDP traffic on QUIC ports (typically UDP/443) at upstream firewalls if HTTP/3 is not in use.
# Configuration example - disable HTTP/3 QUIC listener in nginx.conf
server {
listen 443 ssl;
# listen 443 quic reuseport; # <-- comment out to disable HTTP/3
# http3 on; # <-- comment out to disable HTTP/3
server_name example.com;
ssl_certificate /etc/nginx/certs/example.crt;
ssl_certificate_key /etc/nginx/certs/example.key;
}
# Reload NGINX after editing
sudo nginx -t && sudo systemctl reload nginx
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

