CVE-2021-21310
In next-auth before version 3.3.0 there is a token verification vulnerability.
Does this matter?
Lower severity and a low EPSS score (1.67%). Track it; it rarely justifies an emergency change on its own.
Description
NextAuth.js (next-auth) is am open source authentication solution for Next.js applications. In next-auth before version 3.3.0 there is a token verification vulnerability. Implementations using the Prisma database adapter in conjunction with the Email provider are impacted. Implementations using the Email provider with the default database adapter are not impacted. Implementations using the Prisma database adapter but not using the Email provider are not impacted. The Prisma database adapter was checking the verification token, but was not verifying the email address associated with that token. This made it possible to use a valid token to sign in as another user when using the Prima adapter in conjunction with the Email provider. This issue is specific to the community supported Prisma adapter. This issue is fixed in version 3.3.0.
- CVSS 3.1
- 5.9 MEDIUMCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N
- EPSS
- 1.67% probability · 75th percentile
- CISA KEV
- Not listed
- Weakness
- CWE-290
- Affected
- nextauth.js/next-auth
- Source
- security-advisories@github.com
References
- https://github.com/nextauthjs/next-auth/releases/tag/v3.3.0Third Party Advisory
- https://github.com/nextauthjs/next-auth/security/advisories/GHSA-pg53-56cg-4m8qExploit, Third Party Advisory
- https://www.npmjs.com/package/next-authProduct, Third Party Advisory
- https://github.com/nextauthjs/next-auth/releases/tag/v3.3.0Third Party Advisory
- https://github.com/nextauthjs/next-auth/security/advisories/GHSA-pg53-56cg-4m8qExploit, Third Party Advisory
- https://www.npmjs.com/package/next-authProduct, Third Party Advisory
Source: NVD record, EPSS from FIRST.org, KEV from CISA. Refreshed daily.