CVE-2024-34351
Next.js Server-Side Request Forgery in Server Actions
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](https://github.com/vercel/next.js/pull/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
How to fix CVE-2024-34351
To remediate CVE-2024-34351, upgrade the affected package to a fixed version below.
- —upgrade to 14.1.1 or later
Is CVE-2024-34351 being exploited?
Likely — EPSS is 92.8%, placing CVE-2024-34351 in the top tier of vulnerabilities by exploitation probability. Prioritise patching.
Affected packages (1)
- >= 13.4.0, < 14.1.1