GitHub Advisoryadvisory · npm
GHSA-v64w-49xw-qq89 Possible user mocking that bypasses basic authentication
MEDIUM
Official page ↗
- Aliases
- CVE-2023-48309
- Ecosystem
- npm
- Packages
- next-auth
- Severity
- Moderate
- CVSS vector
- CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
- Weaknesses
- CWE-285
- Reviewed
- 2023-11-20
Affected packages
• npm next-auth: < 4.24.5 → fixed in 4.24.5
Description
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@latest
```
```
yarn add next-auth@latest
```
```
pnpm add next-auth@latest
```
Workarounds
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:
```ts
// 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
• NextAuth.js Middleware
• Role-based access contorl (RBAC) guide
Related
Alias · CVE (1)
- CVE-2023-48309 NextAuth.js provides authentication for Next.js. vulnerability
Weakness · CWE (1)
- CWE-285 Improper Authorization weakness
References
- https://github.com/nextauthjs/next-auth/security/advisories/GHSA-v64w-49xw-qq89 web
- https://nvd.nist.gov/vuln/detail/CVE-2023-48309 advisory
- https://github.com/nextauthjs/next-auth/commit/d237059b6d0cb868c041ba18b698e0cee20a2f10 web
- https://authjs.dev/guides/basics/role-based-access-control web
- https://github.com/nextauthjs/next-auth package
- https://next-auth.js.org/configuration/nextjs#advanced-usage web
- https://next-auth.js.org/configuration/nextjs#middlewar web