Vulnerability Description
Next.js is a React framework for building full-stack web applications. In affected versions if a Next.js application is performing authorization in middleware based on pathname, it was possible for this authorization to be bypassed for pages directly under the application's root directory. For example: * [Not affected] `https://example.com/` * [Affected] `https://example.com/foo` * [Not affected] `https://example.com/foo/bar`. This issue is patched in Next.js `14.2.15` and later. If your Next.js application is hosted on Vercel, this vulnerability has been automatically mitigated, regardless of Next.js version. There are no official workarounds for this vulnerability.
CVSS Score
HIGH
Affected Products
| Vendor | Product | Versions |
|---|---|---|
| Vercel | Next.Js | >= 9.5.5, < 14.2.15 |
Related Weaknesses (CWE)
References
- https://github.com/vercel/next.js/releases/tag/v14.2.15Release Notes
- https://github.com/vercel/next.js/security/advisories/GHSA-7gfc-8cq8-jh5fVendor Advisory
FAQ
What is CVE-2024-51479?
CVE-2024-51479 is a vulnerability with a CVSS score of 7.5 (HIGH). Next.js is a React framework for building full-stack web applications. In affected versions if a Next.js application is performing authorization in middleware based on pathname, it was possible for th...
How severe is CVE-2024-51479?
CVE-2024-51479 has been rated HIGH with a CVSS base score of 7.5/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2024-51479?
Check the references section above for vendor advisories and patch information. Affected products include: Vercel Next.Js.