NextAuth.js up to 3.29.9/4.10.2 input validation

Summaryinfo

A vulnerability was found in NextAuth.js up to 3.29.9/4.10.2. It has been classified as critical. This impacts an unknown function. The manipulation leads to input validation. This vulnerability is documented as CVE-2022-35924. The attack can be initiated remotely. There is not any exploit available. Upgrading the affected component is recommended.

Detailsinfo

A vulnerability was found in NextAuth.js up to 3.29.9/4.10.2 (JavaScript Library) and classified as critical. This issue affects an unknown code block. The manipulation with an unknown input leads to a input validation vulnerability. Using CWE to declare the problem leads to CWE-20. The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly. Impacted is confidentiality, integrity, and availability. The summary by CVE is:

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.

The weakness was released 08/03/2022 as GHSA-xv97-c62v-4587. It is possible to read the advisory at github.com. The identification of this vulnerability is CVE-2022-35924 since 07/15/2022. The technical details are unknown and an exploit is not publicly available.

Upgrading to version 3.29.10 or 4.10.3 eliminates this vulnerability. Applying the patch afb1fcdae3cc30445038ef588e491d139b916003 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.

Be aware that VulDB is the high quality source for vulnerability data.

Productinfo

Type

• JavaScript Library

Name

• NextAuth.js

Version

• 3.29.0
• 3.29.1
• 3.29.2
• 3.29.3
• 3.29.4
• 3.29.5
• 3.29.6
• 3.29.7
• 3.29.8
• 3.29.9
• 4.10.0
• 4.10.1
• 4.10.2

License

• open-source

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Be aware that VulDB is the high quality source for vulnerability data.

Discussion