Nginx Open SourceWeb server / proxy · F5
CVE-2024-24990
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedWhen NGINX Plus or NGINX OSS are configured to use the HTTP/3 QUIC module, undisclosed requests can cause NGINX worker processes to terminate. Note: The HTTP/3 QUIC module is not enabled by default and is considered experimental. For more information, refer to Support for QUIC and HTTP/3 https://nginx.org/en/docs/quic.html . Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceWhen NGINX Plus or NGINX OSS are configured to use the experimental HTTP/3 QUIC module, certain undisclosed requests can cause NGINX worker processes to terminate, resulting in denial of service. This is a remote denial-of-service vulnerability specific to QUIC-enabled configurations.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Nginx Open SourceWeb server / proxy
>= 1.25.0, < 1.25.4
Nginx PlusWeb server / proxy
= r30= r31CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check NGINX versionRun 'nginx -v' or 'nginx -V' to display the installed version numberAffected if The version is NGINX Open Source >= 1.25.0 and < 1.25.4, or NGINX Plus r30 or r31
-
Verify QUIC module is loadedRun 'nginx -V 2>&1 | grep -o http_quic_module' to check if the QUIC module is compiled inAffected if The http_quic_module is present in the NGINX build
-
Confirm QUIC is enabled in configurationSearch nginx.conf and included files for 'listen ... quic' or 'http3' directives that enable QUIC handlingAffected if A listen directive includes the 'quic' parameter or http3 is explicitly enabled
You are affected if NGINX is running a vulnerable version (Open Source 1.25.0-1.25.3, or Plus r30/r31) AND the QUIC/HTTP3 module is both loaded and actively configured in your nginx.conf.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped1.25.4
Update NGINX to a patched version that addresses this vulnerability, or if QUIC/HTTP3 is not required, disable the QUIC module in the configuration.
Nginx OSS 1.25.4+ or Nginx Plus r32+
- Check if HTTP/3 QUIC module is enabled in your nginx configuration (look for 'listen ... quic' directives)
- Schedule upgrade during a maintenance window
- Back up your current nginx configuration and binary
- Upgrade nginx Open Source to version 1.25.4 or later, or nginx Plus to r32 or later
- Verify the new version is installed: nginx -v
- Test configuration syntax: nginx -t
- Reload or restart nginx to apply changes: systemctl reload nginx or nginx -s reload
- Monitor worker processes for stability
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Nginx Open Source
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-24990 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-24990 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data