Next.js authorization bypass vulnerability
### Impact If a Next.js application is performing authorization in middleware based on pathname, it was possible for this authorization to be bypassed. ### Patches This issue was 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. ### Workarounds There are no official workarounds for this vulnerability. #### Credits We'd like to thank [tyage](http://github.com/tyage) (GMO CyberSecurity by IERAE) for responsible disclosure of this issue.
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2024-51479US | —OT elevated | — | ||
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… | ||||
references
External citations — patches, advisories, analysis.
- https://github.com/vercel/next.jsPACKAGE
- https://github.com/vercel/next.js/commit/1c8234eb20bc8afd396b89999a00f06b61d72d7bWEB
- https://github.com/vercel/next.js/releases/tag/v14.2.15WEB
- https://github.com/vercel/next.js/security/advisories/GHSA-7gfc-8cq8-jh5fWEB
- https://nvd.nist.gov/vuln/detail/CVE-2024-51479ADVISORY
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan