CVE-2021-21310 Token verification bug in next-auth
Attackers can sign in as other users by exploiting a token verification flaw in the Prisma adapter with Email provider.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- A user has to click or open something
- Fix
- Available
What is CVE-2021-21310?
CVE-2021-21310 is a medium-severity authentication bypass vulnerability in nextauthjs next-auth, published on 11 Feb 2021. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Official 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.
Weakness: CWE-290
Which versions are affected by CVE-2021-21310?
2 open source packages ship an affected version, including next-auth. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
next-auth npm | All versions | 3.3.0 |
next-auth npm | All versions | 3.3.0 |
Products include Nextauth.js Next-Auth.
How do I fix CVE-2021-21310?
Upgrade next-auth to 3.3.0 or later.
Upgrade, and rotate credentials and sessions that may have been exposed. More about Authentication bypass.
Is CVE-2021-21310 being exploited?
There is no known exploitation of CVE-2021-21310 in the wild and no public exploit code.
Other vulnerabilities in nextauthjs next-auth
- CVE-2022-35924 Verification requests (magic link) sent to unwanted emails
- CVE-2023-27490 Missing proper state, nonce and PKCE checks for OAuth authentication in next-auth
- CVE-2022-31093 Improper Handling of `callbackUrl` parameter in next-auth
- CVE-2022-31127 Improper handling of email input in next-auth
- CVE-2022-39263 NextAuth.js Upstash Adapter missing token verification
Sources
Also known as GHSA-pg53-56cg-4m8q.