First published: Thu Feb 11 2021(Updated: )
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.
Credit: security-advisories@github.com
Affected Software | Affected Version | How to fix |
---|---|---|
Nextauth.js Next-auth | <3.3.0 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2021-21310 is a token verification vulnerability in NextAuth.js (next-auth) before version 3.3.0.
CVE-2021-21310 has a severity keyword of 'medium' and a numerical severity value of 5.9.
Implementations using NextAuth.js (next-auth) before version 3.3.0 with the Prisma database adapter in conjunction with the Email provider are impacted.
To fix CVE-2021-21310, users should upgrade to version 3.3.0 or later of NextAuth.js (next-auth).
More information about CVE-2021-21310 can be found at the following references: [link1](https://github.com/nextauthjs/next-auth/releases/tag/v3.3.0), [link2](https://github.com/nextauthjs/next-auth/security/advisories/GHSA-pg53-56cg-4m8q), [link3](https://www.npmjs.com/package/next-auth).