Skip to content

Next.js Allows a Denial of Service (DoS) with Server Actions

Moderate severity GitHub Reviewed Published Jan 3, 2025 in vercel/next.js • Updated Jan 3, 2025

Package

npm next (npm)

Affected versions

>= 13.0.0, < 13.5.8
>= 14.0.0, < 14.2.21
>= 15.0.0, < 15.1.2

Patched versions

13.5.8
14.2.21
15.1.2

Description

Impact

A Denial of Service (DoS) attack allows attackers to construct requests that leaves requests to Server Actions hanging until the hosting provider cancels the function execution.

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.

Patches

This vulnerability was resolved in Next.js 14.2.21, 15.1.2, and 13.5.8. We recommend that users upgrade to a safe version.

Workarounds

There are no official workarounds for this vulnerability.

Credits

Thanks to the PackDraw team for responsibly disclosing this vulnerability.

References

@ztanner ztanner published to vercel/next.js Jan 3, 2025
Published to the GitHub Advisory Database Jan 3, 2025
Reviewed Jan 3, 2025
Published by the National Vulnerability Database Jan 3, 2025
Last updated Jan 3, 2025

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
Low

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

EPSS score

0.043%
(11th percentile)

Weaknesses

CVE ID

CVE-2024-56332

GHSA ID

GHSA-7m27-7ghc-44w9

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.