Bug 2335479 (CVE-2024-56332) - CVE-2024-56332 next.js: Next.js Vulnerable to Denial of Service (DoS) with Server Actions
Summary: CVE-2024-56332 next.js: Next.js Vulnerable to Denial of Service (DoS) with Se...
Keywords:
Status: NEW
Alias: CVE-2024-56332
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Product Security DevOps Team
QA Contact:
URL:
Whiteboard:
Depends On: 2335760 2335748 2335749 2335750 2335751 2335752 2335753 2335754 2335755 2335756 2335757 2335758 2335759 2335761
Blocks:
TreeView+ depends on / blocked
 
Reported: 2025-01-03 21:01 UTC by OSIDB Bzimport
Modified: 2025-01-06 14:09 UTC (History)
15 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2025-01-06 10:17:38 UTC
Embargoed:


Attachments (Terms of Use)

Description OSIDB Bzimport 2025-01-03 21:01:05 UTC
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.

Comment 2 Miroslav Lichvar 2025-01-06 10:17:38 UTC
The conky upstream tarball includes the source code of the upstream website, which seems to be using next.js, but that is not included in the rpms we build for Fedora.

Comment 3 Miroslav Lichvar 2025-01-06 10:19:04 UTC
I closed the wrong bug. Sorry for the noise.


Note You need to log in before you can comment on or make changes to this bug.