CVE-2024-34351: Next.js Server-Side Request Forgery in Server Actions
vercel · next.js
Affected: vercel next.js · Exploitation: check available, not yet exploited
Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.
Higher than 92% of scored CVEs
DescriptionCVE.org
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`.
Affected products1
From the CVE record. A product or version that is not listed is unknown, not unaffected.
- vercel · next.js>= 13.4.0, < 14.1.1
On the Atlas
Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.
- Exploitation
- Check available, not yet exploited. A public nuclei template can confirm it on a system you are authorised to test.
- CISA KEV
- Not listed
- Public check
- Next.js - Server Side Request Forgery (SSRF) · nuclei template in projectdiscovery/nuclei-templates
- Weakness
- Server-Side Request Forgery
- Vendor
- vercel
- Published
- May 2024
CoverageNo articles yet
No CyberSIXT article names CVE-2024-34351 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.