Possible user mocking that bypasses basic authentication
Impact
next-auth applications prior to version 4.24.5 that rely on the default Middleware authorization are affected.
A bad actor could create an empty/mock user, by getting hold of a NextAuth.js-issued JWT from an interrupted OAuth sign-in flow (state, PKCE or nonce).
Manually overriding the next-auth.session-token cookie value with this non-related JWT would let the user simulate a logged in user, albeit having no user information associated with it. (The only property on this user is an opaque randomly generated string).
This vulnerability does not give access to other users' data, neither to resources that require proper authorization via scopes or other means. The created mock user has no information associated with it (ie. no name, email, access_token, etc.)
This vulnerability can be exploited by bad actors to peek at logged in user states (e.g. dashboard layout).
Note: Regardless of the vulnerability, the existence of a NextAuth.js session state can provide simple authentication, but not authorization in your applications. For role-based access control, you can check out our guide.
Patches
We patched the vulnerability in next-auth v4.24.5. To upgrade, run one of the following:
npm i next-auth@latestyarn add next-auth@latestpnpm add next-auth@latestWorkarounds
Upgrading to latest is the recommended way to fix this issue. However, using a custom authorization callback for Middleware, developers can manually do a basic authentication:
// middleware.ts
import { withAuth } from "next-auth/middleware"
export default withAuth(/*your middleware function*/, {
// checking the existence of any property - besides `value` which might be a random string - on the `token` object is sufficient to prevent this vulnerability
callbacks: { authorized: ({ token }) => !!token?.email }
})References
Betroffene Software
Klicken Sie auf eine Technologie, um alle zugehörigen Schwachstellen anzuzeigen.
| Plattform | Paket | Anfällige Versionen | Behoben in |
|---|---|---|---|
| npm-Paket | next-auth | < 4.24.5 | 4.24.5 |
Verweise
- https://github.com/nextauthjs/next-auth/security/advisories/GHSA-v64w-49xw-qq89
- https://nvd.nist.gov/vuln/detail/CVE-2023-48309
- https://github.com/nextauthjs/next-auth/commit/d237059b6d0cb868c041ba18b698e0cee20a2f10
- https://authjs.dev/guides/basics/role-based-access-control
- https://github.com/nextauthjs/next-auth
- https://next-auth.js.org/configuration/nextjs#advanced-usage
- https://next-auth.js.org/configuration/nextjs#middlewar
- CVSS-Vektor
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N- Schwäche (CWE)
CWE-285- Plattform
- npm
- Paket
next-auth- Veröffentlicht
- 20.11.2023
- Aktualisiert
- 11.10.2026 10:22
Quellen und Lizenzen
OSV / GitHub Advisory Database - GHSA-v64w-49xw-qq89 - CC BY 4.0
Schwachstellenhistorie: next-auth
Alle veröffentlichten Schwachstellen dieses Pakets (npm-Paket), neueste zuerst. Zeigt, ob es ein einmaliger Ausrutscher ist oder ein Paket, das man im Auge behalten muss.
- Einträge insgesamt
- 14
- Erste → letzte
- 02.2021 07.2026
- Ohne Fix
- 0
- In Angriffen ausgenutzt
- 0
Verteilung nach Schweregrad
- Kritisch 3
- Hoch 4
- Mittel 5
- Niedrig 2
Veröffentlichungen pro Jahr
- 2021: 1
- 2022: 6
- 2023: 2
- 2024: 0
- 2025: 1
- 2026: 4
-
Possible user mocking that bypasses basic authentication dieser Eintrag
Erkennen Sie Schwachstellen in Ihrer Anwendung
Mit der DockRay-Integration und aktivierter Softwareinventarisierung prüft DockRay gemeldete Komponentenversionen auf bekannte Schwachstellen und benachrichtigt Sie über bestätigte Treffer. Die Abdeckung hängt von der unterstützten Technologie und den verfügbaren Meldungen ab.