CVE-2024-56332
Next.js Vulnerable to Denial of Service (DoS) with Server Actions
In short
Next.js applications using Server Actions can be attacked by sending specially crafted requests that hang indefinitely, consuming resources and potentially causing billing issues on serverless platforms. This vulnerability allows attackers to disrupt service availability without much effort.
Technical detail
Next.js versions 13.0.0–13.5.7, 14.0.0–14.2.20, and 15.0.0–15.1.1 are vulnerable to DoS via malformed Server Action requests that remain open until timeout. The attack exploits improper handling of request lifecycle (CWE-770: Allocation of Resources Without Limits), leaving connections idle and triggering excessive billing on metered hosting (Denial of Wallet). Mitigated in 13.5.8, 14.2.21, and 15.1.2.
Summary generated and translated by AI from the official description.
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.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L