fix(deps): update dependency next-auth to v4.24.5 [security]

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
next-auth (source)	4.22.5 -> 4.24.5

Review

• Updates have been tested and work
• If updates are AWS related, versions match the infrastructure (e.g. Lambda runtime, database, etc.)

GitHub Vulnerability Alerts

CVE-2023-48309

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:

// 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

---

Release Notes

nextauthjs/next-auth (next-auth)

v4.24.5

Compare Source

Bugfixes

• differentiate between issued JWTs

v4.24.4

Compare Source

Bugfixes

• allow Next.js 14 as peer dependency

v4.24.3

Compare Source

Bugfixes

• css build error

v4.24.2

Compare Source

Bugfixes

• css build error

v4.24.1

Compare Source

Bugfixes

• css build error

v4.24.0

Compare Source

Features

• tweak default sign-in page (#​8888)

v4.23.2

Compare Source

Bugfixes

• next: returns correct status for signing in with redirect: false for route handler (#​8775) (27b2519)
• ts: fix typo (d813c00)
• remove trailing ? from signIn URL (#​8466)

Other

• update security policy link

v4.23.1

Compare Source

Bugfixes

• ts: correctly expose next-auth/adapters (20c3fe3)
• use default submodules export in package.json (#​8330)

v4.23.0

Compare Source

Features

• providers: add Passage by 1Password (5a8aa2e)

Bugfixes

• ts: correctly export submodule types (05ff6ae)
• sort cookie chunks correctly (#​8284)

---

Configuration

📅 Schedule: Branch creation - "" in timezone America/Montreal, Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate. View repository job log here.