dbcve.org
Next.jsApplication · Vercel

CVE-2024-56332

MEDIUM · 5.3 CVSS v3.1 Published 2025-01-03
Fix available
A fix is available. Upgrade to 13.5.8 / 14.2.21 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
Next.js is a React framework for building full-stack web applications. Starting in version 13.0.0 and prior to versions 13.5.8, 14.2.21, and 15.1.2, Next.js is vulnerable to a Denial of Service (DoS) attack that allows attackers to construct requests that leaves requests to Server Actions hanging until the hosting provider cancels the function execution. This vulnerability can also be used as a Denial of Wallet (DoW) attack when deployed in providers billing by response times. (Note: Next.js server is idle during that time and only keeps the connection open. CPU and memory footprint are low during that time.). Deployments without any protection against long running Server Action invocations are especially vulnerable. Hosting providers like Vercel or Netlify set a default maximum duration on function execution to reduce the risk of excessive billing. This is the same issue as if the incoming HTTP request has an invalid `Content-Length` header or never closes. If the host has no other mitigations to those then this vulnerability is novel. This vulnerability affects only Next.js deployments using Server Actions. The issue was resolved in Next.js 13.5.8, 14.2.21, and 15.1.2. We recommend that users upgrade to a safe version. There are no official workarounds.

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 · high confidence

Next.js versions prior to 13.5.8, 14.2.21, and 15.1.2 contain a vulnerability in Server Actions where specially crafted HTTP requests can leave connections open indefinitely, causing resource exhaustion through hanging requests. Attackers can exploit this to create DoS or DoW (Denial of Wallet) attacks with minimal resource usage on their end.

MitigationUpgrade to Next.js 13.5.8, 14.2.21, or 15.1.2 or later. For deployments without hosting provider timeout protections, implement request timeouts at the load balancer or edge level as an additional safeguard.

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
Next.jsApplication
Affected:>= 13.0.0, < 13.5.8>= 14.0.0, < 14.2.21>= 15.0.0, < 15.1.2

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

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

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. Identify installed Next.js version
    Run 'npm list next' or check the 'next' dependency version in your package.json file
    Affected if The version is 13.0.0 through 13.5.7, 14.0.0 through 14.2.20, or 15.0.0 through 15.1.1 (i.e., it falls within any of the affected ranges)
  2. Confirm Server Actions are in use
    Search your codebase for 'use server' directives in client components or check for exported functions marked with 'use server' in your action files. Also check if your next.config.js has 'serverActions' configuration enabled
    Affected if Server Actions are enabled or used in your application
  3. Check for hanging connections
    Monitor active connections to your Next.js server during normal operation. Use netstat or your cloud provider's connection metrics to observe if connections remain in ESTABLISHED state beyond expected request completion times
    Affected if Connections remain open significantly longer than your expected response times, especially for requests to Server Action endpoints
  4. Review deployment timeout settings
    Check your load balancer, API gateway, or edge configuration (e.g., Vercel project settings, AWS ALB, Cloudflare) for request timeout values applied to Next.js routes
    Affected if No timeout is configured at the infrastructure layer, or timeouts are set to values higher than your normal response expectations

You are affected if your Next.js version falls within any of the affected ranges AND Server Actions are enabled in your application, particularly if you lack infrastructure-level request timeouts.

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 13.5.8 / 14.2.21 / 15.1.2 or later
Fixed in 13.5.814.2.2115.1.2
Interim mitigation

Upgrade to Next.js 13.5.8, 14.2.21, or 15.1.2 or later. For deployments without hosting provider timeout protections, implement request timeouts at the load balancer or edge level as an additional safeguard.

Recommended fix High confidence

Next.js 13.5.8 (for 13.x), 14.2.21 (for 14.x), or 15.1.2 (for 15.x)

  1. If using Next.js 13.x: Upgrade to version 13.5.8 or later by running: npm install [email protected] (or npm install next@latest to get the latest safe 13.x version)
  2. If using Next.js 14.x: Upgrade to version 14.2.21 or later by running: npm install [email protected] (or npm install next@latest to get the latest safe 14.x version)
  3. If using Next.js 15.x: Upgrade to version 15.1.2 or later by running: npm install [email protected] (or npm install next@latest to get the latest safe 15.x version)
  4. After upgrading, verify Server Actions continue to function correctly in your application

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

Fix this in Next.js Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,340
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-56332 — 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-56332 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