Vulnerabilities · 2024 · Vercel
CVE-2024-51479
Vercel Next.js vulnerability
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.
Affected products
Next.js. The exact versions are in the references.
What to do now
- Check your exposureFind out whether Vercel Next.js runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- github.com/vercel/next.js/security/advisories/GHSA-7gfc-8cq8-jh5f · Vendor Advisory
- github.com/vercel/next.js/releases/tag/v14.2.15
- github.com/vercel/next.js/commit/1c8234eb20bc8afd396b89999a00f06b61d72d7b
- nvd.nist.gov/vuln/detail/CVE-2024-51479
- github.com/advisories/GHSA-7gfc-8cq8-jh5f
- nvd.nist.gov/vuln/detail/CVE-2024-51479
- cve.org/CVERecord?id=CVE-2024-51479
More vulnerabilities in Vercel products
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.