Vulnerability Description
NextAuth.js is a complete open source authentication solution for Next.js applications. `next-auth` users who are using the `EmailProvider` either in versions before `4.10.3` or `3.29.10` are affected. If an attacker could forge a request that sent a comma-separated list of emails (eg.: `[email protected],[email protected]`) to the sign-in endpoint, NextAuth.js would send emails to both the attacker and the victim's e-mail addresses. The attacker could then login as a newly created user with the email being `[email protected],[email protected]`. This means that basic authorization like `email.endsWith("@victim.com")` in the `signIn` callback would fail to communicate a threat to the developer and would let the attacker bypass authorization, even with an `@attacker.com` address. This vulnerability has been patched in `v4.10.3` and `v3.29.10` by normalizing the email value that is sent to the sign-in endpoint before accessing it anywhere else. We also added a `normalizeIdentifier` callback on the `EmailProvider` configuration, where you can further tweak your requirements for what your system considers a valid e-mail address. (E.g.: strict RFC2821 compliance). Users are advised to upgrade. There are no known workarounds for this vulnerability. If for some reason you cannot upgrade, you can normalize the incoming request using Advanced Initialization.
CVSS Score
CRITICAL
Affected Products
| Vendor | Product | Versions |
|---|---|---|
| Nextauth.Js | Next-Auth | < 3.29.10 |
Related Weaknesses (CWE)
References
- https://en.wikipedia.org/wiki/Email_address#Local-partThird Party Advisory
- https://github.com/nextauthjs/next-auth/commit/afb1fcdae3cc30445038ef588e491d139PatchThird Party Advisory
- https://github.com/nextauthjs/next-auth/security/advisories/GHSA-xv97-c62v-4587MitigationThird Party Advisory
- https://next-auth.js.org/configuration/callbacks#sign-in-callbackVendor Advisory
- https://next-auth.js.org/configuration/initialization#advanced-initializationVendor Advisory
- https://next-auth.js.org/providers/emailVendor Advisory
- https://next-auth.js.org/providers/email#normalizing-the-e-mail-addressVendor Advisory
- https://nodemailer.com/message/addressesThird Party Advisory
- https://en.wikipedia.org/wiki/Email_address#Local-partThird Party Advisory
- https://github.com/nextauthjs/next-auth/commit/afb1fcdae3cc30445038ef588e491d139PatchThird Party Advisory
- https://github.com/nextauthjs/next-auth/security/advisories/GHSA-xv97-c62v-4587MitigationThird Party Advisory
- https://next-auth.js.org/configuration/callbacks#sign-in-callbackVendor Advisory
- https://next-auth.js.org/configuration/initialization#advanced-initializationVendor Advisory
- https://next-auth.js.org/providers/emailVendor Advisory
- https://next-auth.js.org/providers/email#normalizing-the-e-mail-addressVendor Advisory
FAQ
What is CVE-2022-35924?
CVE-2022-35924 is a vulnerability with a CVSS score of 9.1 (CRITICAL). NextAuth.js is a complete open source authentication solution for Next.js applications. `next-auth` users who are using the `EmailProvider` either in versions before `4.10.3` or `3.29.10` are affected...
How severe is CVE-2022-35924?
CVE-2022-35924 has been rated CRITICAL with a CVSS base score of 9.1/10. This is considered a critical vulnerability requiring immediate attention.
Is there a patch for CVE-2022-35924?
Check the references section above for vendor advisories and patch information. Affected products include: Nextauth.Js Next-Auth.