CVE-2021-21310
Summary
| CVE | CVE-2021-21310 |
|---|
| State | PUBLIC |
|---|
| Assigner | [email protected] |
|---|
| Source Priority | CVE Program / NVD first with legacy fallback |
|---|
| Published | 2021-02-11 22:15:00 UTC |
|---|
| Updated | 2021-02-19 19:12:00 UTC |
|---|
| 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. |
|---|
NVD Known Affected Configurations (CPE 2.3)
References
| Reference | Source | Link | Tags |
|---|
| Release v3.3.0 · nextauthjs/next-auth · GitHub |
MISC |
github.com |
Third Party Advisory |
| Insecure email token verification in Prisma adapter · Advisory · nextauthjs/next-auth · GitHub |
CONFIRM |
github.com |
Exploit, Third Party Advisory |
| next-auth - npm |
MISC |
www.npmjs.com |
Product, Third Party Advisory |
| CVE Program record |
CVE.ORG |
www.cve.org |
canonical |
| NVD vulnerability detail |
NVD |
nvd.nist.gov |
canonical, analysis |
No vendor comments have been submitted for this CVE.
Legacy QID Mappings
- 982944 Nodejs (npm) Security Update for next-auth (GHSA-pg53-56cg-4m8q)
