GitHub Advisoryadvisory · npm

GHSA-fr5h-rqp8-mj6g Next.js Server-Side Request Forgery in Server Actions

HIGH Published 2024-05-09 Modified 2025-09-10 Official page ↗
Aliases
CVE-2024-34351
Ecosystem
npm
Packages
next
Severity
High
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Weaknesses
CWE-918
Reviewed
2024-05-09

Affected packages

• npm next: >= 13.4.0, < 14.1.1 → fixed in 14.1.1

Description

Impact A Server-Side Request Forgery (SSRF) vulnerability was identified in Next.js Server Actions by security researchers at Assetnote. 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. Prerequisites • Next.js (`<14.1.1`) is running in a self-hosted* manner. • The Next.js application makes use of Server Actions. • The Server Action performs a redirect to a relative path which starts with a `/`. \* Many hosting providers (including Vercel) route requests based on the Host header, so we do not believe that this vulnerability affects any Next.js applications where routing is done in this manner. Patches This vulnerability was patched in #62561 and fixed in Next.js `14.1.1`. Workarounds There are no official workarounds for this vulnerability. We recommend upgrading to Next.js `14.1.1`. Credit Vercel and the Next.js team thank Assetnote for responsibly disclosing this issue to us, and for working with us to verify the fix. Thanks to: Adam Kues - Assetnote Shubham Shah - Assetnote

Related

Alias · CVE (1)

  • CVE-2024-34351 Next.js is a React framework that can provide building blocks to create web applications. vulnerability

Weakness · CWE (1)

  • CWE-918 Server-Side Request Forgery weakness

References