GHSA-7m27-7ghc-44w9
Vulnerability from github
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.
{ "affected": [ { "package": { "ecosystem": "npm", "name": "next" }, "ranges": [ { "events": [ { "introduced": "13.0.0" }, { "fixed": "13.5.8" } ], "type": "ECOSYSTEM" } ] }, { "package": { "ecosystem": "npm", "name": "next" }, "ranges": [ { "events": [ { "introduced": "14.0.0" }, { "fixed": "14.2.21" } ], "type": "ECOSYSTEM" } ] }, { "package": { "ecosystem": "npm", "name": "next" }, "ranges": [ { "events": [ { "introduced": "15.0.0" }, { "fixed": "15.1.2" } ], "type": "ECOSYSTEM" } ] } ], "aliases": [ "CVE-2024-56332" ], "database_specific": { "cwe_ids": [ "CWE-770" ], "github_reviewed": true, "github_reviewed_at": "2025-01-03T20:19:29Z", "nvd_published_at": "2025-01-03T21:15:13Z", "severity": "MODERATE" }, "details": "### Impact\nA 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.\n\n_Note: Next.js server is idle during that time and only keeps the connection open. CPU and memory footprint are low during that time._\n\nDeployments 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.\n\nThis 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.\n\nThis vulnerability affects only Next.js deployments using Server Actions.\n\n### Patches\n\nThis 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.\n\n### Workarounds\n\nThere are no official workarounds for this vulnerability.\n\n### Credits\n\nThanks to the PackDraw team for responsibly disclosing this vulnerability.", "id": "GHSA-7m27-7ghc-44w9", "modified": "2025-01-03T21:48:13Z", "published": "2025-01-03T20:19:29Z", "references": [ { "type": "WEB", "url": "https://github.com/vercel/next.js/security/advisories/GHSA-7m27-7ghc-44w9" }, { "type": "ADVISORY", "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-56332" }, { "type": "PACKAGE", "url": "https://github.com/vercel/next.js" } ], "schema_version": "1.4.0", "severity": [ { "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L", "type": "CVSS_V3" } ], "summary": "Next.js Allows a Denial of Service (DoS) with Server Actions" }
Sightings
Author | Source | Type | Date |
---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or seen somewhere by the user.
- Confirmed: The vulnerability is confirmed from an analyst perspective.
- Exploited: This vulnerability was exploited and seen by the user reporting the sighting.
- Patched: This vulnerability was successfully patched by the user reporting the sighting.
- Not exploited: This vulnerability was not exploited or seen by the user reporting the sighting.
- Not confirmed: The user expresses doubt about the veracity of the vulnerability.
- Not patched: This vulnerability was not successfully patched by the user reporting the sighting.