8.1
CWE
287
Advisory Published
Updated

CVE-2022-39263: NextAuth.js Upstash Adapter missing token verification

First published: Wed Sep 28 2022(Updated: )

`@next-auth/upstash-redis-adapter` is the Upstash Redis adapter for NextAuth.js, which provides authentication for Next.js. Applications that use `next-auth` Email Provider and `@next-auth/upstash-redis-adapter` before v3.0.2 are affected by this vulnerability. The Upstash Redis adapter implementation did not check for both the identifier (email) and the token, but only checking for the identifier when verifying the token in the email callback flow. An attacker who knows about the victim's email could easily sign in as the victim, given the attacker also knows about the verification token's expired duration. The vulnerability is patched in v3.0.2. A workaround is available. Using Advanced Initialization, developers can check the requests and compare the query's token and identifier before proceeding.

Credit: security-advisories@github.com

Affected SoftwareAffected VersionHow to fix
Nextauth.js Next-auth<3.0.2

Never miss a vulnerability like this again

Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.

Frequently Asked Questions

  • What is CVE-2022-39263?

    `CVE-2022-39263` is a vulnerability affecting `@next-auth/upstash-redis-adapter` in NextAuth.js, which provides authentication for Next.js applications using the Email Provider.

  • What is the severity of CVE-2022-39263?

    The severity of `CVE-2022-39263` is high with a severity value of 8.1.

  • How does CVE-2022-39263 impact applications?

    `CVE-2022-39263` can cause issues with authentication in Next.js applications that use the `next-auth` Email Provider and `@next-auth/upstash-redis-adapter` before version 3.0.2.

  • What is the recommended fix for CVE-2022-39263?

    To fix `CVE-2022-39263`, make sure to update `@next-auth/upstash-redis-adapter` to version 3.0.2 or later.

  • Where can I find more information about CVE-2022-39263?

    More information about `CVE-2022-39263` can be found in the following references: [GitHub Commit](https://github.com/nextauthjs/next-auth/commit/d16e04848ee703cf797724194d4ad2907fe125a9) and [GitHub Security Advisory](https://github.com/nextauthjs/next-auth/security/advisories/GHSA-4rxr-27mm-mxq9).

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2024 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203