Auth bypass in Vercel Next.js
CVE-2024-51479
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.
Published · last modified .
CVSS v3 metric
CVSS v3 base score 7.5 (High). Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N.
EPSS exploit prediction
EPSS 0.040, 90.7th percentile (scored ); unchanged over 30 days. About EPSS.
Affected products
- Vercel Next.js — versions >= 9.5.5, < 14.2.15
Weakness classification (CWE)
Public exploits and proof-of-concept code
Also mentioned in 13 other repositories (12442RF/POC, adysec/POC, ARPSyndicate/cve-scores, …). These reference the CVE in a list, notes or a scanner and are not exploit code for it.
References
- https://github.com/vercel/next.js/security/advisories/GHSA-7gfc-8cq8-jh5f (Vendor Advisory)
- https://github.com/vercel/next.js/releases/tag/v14.2.15 (Release Notes)