CVE-2024-34351
A Server-Side Request Forgery (SSRF) vulnerability was identified in Next.js Server Actions.
Does this matter?
High impact if exploited, but EPSS currently rates exploitation as unlikely (5.45%). Schedule it in the normal patch cycle and watch for a rise in EPSS or a public exploit.
Description
Next.js is a React framework that can provide building blocks to create web applications. A Server-Side Request Forgery (SSRF) vulnerability was identified in Next.js Server Actions. If the `Host` header is modified, and the below conditions are also met, an attacker may be able to make requests that appear to be originating from the Next.js application server itself. The required conditions are 1) Next.js is running in a self-hosted manner; 2) the Next.js application makes use of Server Actions; and 3) the Server Action performs a redirect to a relative path which starts with a `/`. This vulnerability was fixed in Next.js `14.1.1`.
- CVSS 3.1
- 7.5 HIGHCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
- EPSS
- 5.45% probability · 92th percentile
- CISA KEV
- Not listed
- Weakness
- CWE-918
- Affected
- vercel/next.js
- Source
- security-advisories@github.com
References
- https://github.com/vercel/next.js/commit/8f7a6ca7d21a97bc9f7a1bbe10427b5ad74b9085Patch
- https://github.com/vercel/next.js/pull/62561Issue Tracking, Patch
- https://github.com/vercel/next.js/security/advisories/GHSA-fr5h-rqp8-mj6gVendor Advisory
- https://github.com/vercel/next.js/commit/8f7a6ca7d21a97bc9f7a1bbe10427b5ad74b9085Patch
- https://github.com/vercel/next.js/pull/62561Issue Tracking, Patch
- https://github.com/vercel/next.js/security/advisories/GHSA-fr5h-rqp8-mj6gVendor Advisory
Source: NVD record, EPSS from FIRST.org, KEV from CISA. Refreshed daily.