Authorization bypass in Next.js
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.
AI Insight
LLM-synthesized narrative grounded in this CVE's description and references.
Affected packages
Versions sourced from the GitHub Security Advisory.
| Package | Affected versions | Patched versions |
|---|---|---|
nextnpm | >= 9.5.5, < 14.2.15 | 14.2.15 |
Affected products
2Patches
Vulnerability mechanics
References
5- github.com/advisories/GHSA-7gfc-8cq8-jh5fghsaADVISORY
- nvd.nist.gov/vuln/detail/CVE-2024-51479ghsaADVISORY
- github.com/vercel/next.js/commit/1c8234eb20bc8afd396b89999a00f06b61d72d7bghsaWEB
- github.com/vercel/next.js/releases/tag/v14.2.15ghsax_refsource_MISCWEB
- github.com/vercel/next.js/security/advisories/GHSA-7gfc-8cq8-jh5fghsax_refsource_CONFIRMWEB
News mentions
0No linked articles in our index yet.