dbcve.org
Nginx Open SourceWeb server / proxy · F5

CVE-2024-34161

MEDIUM · 5.3 CVSS v3.1 Published 2024-05-29
Fix available
A fix is available. Upgrade to 1.26.1 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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 · unedited
When NGINX Plus or NGINX OSS are configured to use the HTTP/3 QUIC module and the network infrastructure supports a Maximum Transmission Unit (MTU) of 4096 or greater without fragmentation, undisclosed QUIC packets can cause NGINX worker processes to leak previously freed memory.

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 confidence

When NGINX Plus or NGINX OSS are configured with the HTTP/3 QUIC module enabled and the network supports an MTU of 4096 or greater without fragmentation, specific undisclosed QUIC packets can cause NGINX worker processes to leak previously freed memory. This is a use-after-free style memory leak specific to the QUIC implementation.

MitigationIf HTTP/3 QUIC is not required in the deployment, disable the QUIC module in NGINX configuration. Otherwise, monitor for NGINX security updates addressing this issue and apply them when available.

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
Affected:>= 1.25.0, < 1.26.1
Nginx PlusWeb server / proxy
Affected:= r30= r31
FedoraOperating system
Affected:= 39= 40

CVSS 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
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

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 checks

Work through these to decide whether this CVE applies to you.

  1. Determine NGINX installation version
    Run 'nginx -v' or 'nginx -V 2>&1' to identify the installed NGINX version
    Affected if The version falls within 1.25.0 to 1.26.0 for Open Source, or is r30 or r31 for Plus
  2. Verify if QUIC module is loaded
    Run 'nginx -V 2>&1' and examine the compiled modules list for '--with-http_v3_module' or '--with-http_quic_module'
    Affected if The http_v3_module or http_quic_module is listed in the compiled modules
  3. Check if QUIC is enabled in configuration
    Examine nginx.conf and included configuration files for 'listen' directives containing the 'quic' parameter, for example: 'listen 443 quic'
    Affected if Any 'listen' directive includes the 'quic' parameter enabling HTTP/3 over QUIC
  4. Assess network MTU configuration context
    Review network configuration and NGINX quic directives (such as quic_retry, quic_gso) to determine if the environment supports high MTU (4096+) without fragmentation
    Affected if The deployment uses high MTU values (4096 or greater) without fragmentation support, combined with QUIC-enabled NGINX

User is affected if NGINX version is 1.25.0-1.26.0 (OSS) or r30/r31 (Plus) AND the HTTP/3 QUIC module is both compiled in and enabled via configuration listen directives in an environment with high MTU network conditions.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 1.26.1 or later
Fixed in 1.26.1
Interim mitigation

If HTTP/3 QUIC is not required in the deployment, disable the QUIC module in NGINX configuration. Otherwise, monitor for NGINX security updates addressing this issue and apply them when available.

Recommended fix High confidence

Nginx Open Source 1.26.1 or later; Nginx Plus r32 or later

  1. 1. Check current Nginx version with: nginx -v or nginx -V
  2. 2. Stop Nginx service: systemctl stop nginx (or nginx -s stop)
  3. 3. For Nginx Open Source: Upgrade to version 1.26.1 or later using your package manager or compiling from source
  4. 4. For Nginx Plus: Upgrade to r32 or later from F5 repositories
  5. 5. For Fedora systems: Run 'dnf update nginx' to get patched packages for versions 39/40
  6. 6. Verify the installed version: nginx -v
  7. 7. Start Nginx service: systemctl start nginx
  8. 8. Test HTTP/3 QUIC functionality to confirm normal operation

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Nginx Open Source Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,120
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,392.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-34161 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-34161 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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