CVE-2022-35924: Next auth NextAuth.js Before 4.10.3 And 3.29.10 Vulnerability
CRITICALCVE-2022-35924 is a CRITICAL (CVSS 9.1) nextauth.js before 4.10.3 and 3.29.10 vulnerability (CWE-20: Improper Input Validation) affecting Next auth libraries in the npm ecosystem. The issue involves nextauth.js before 4.10.3 and 3.29.10 sending verification requests (magic link) to unwanted emails. Remediation is available by upgrading affected packages to version 4.10.3, 3.29.10.
CVE-2022-35924 at a Glance
Security Impact
CVSS: 9.1
The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N).
How to Fix CVE-2022-35924
To remediate this vulnerability, upgrade all affected Next auth dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
npm install next-auth@4.10.3
npm install next-auth@3.29.10
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
npm ls next-auth
How to Check if You Are Affected
To determine whether your Node.js application is affected by CVE-2022-35924, inspect your project dependencies using npm:
npm ls next-auth
Analyze the terminal output to locate any version of Next auth in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 4.10.3), your application is affected.
Note: The npm ls next-auth command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-20: Improper Input Validation, where 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. In Next auth, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
CVE-2022-35924 Affected Next auth Versions
2 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
next-auth
|
npm |
≥ 4.0.0
< 4.10.3
|
4.10.3
|
|
next-auth
|
npm |
< 3.29.10
|
3.29.10
|
References
Frequently Asked Questions
What is CVE-2022-35924?
Which Next auth versions are affected?
What version fixes CVE-2022-35924?
Is next-auth affected?
What is the CVSS score of CVE-2022-35924?
What CWE is associated with CVE-2022-35924?
How can I check npm dependencies for CVE-2022-35924?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-xv97-c62v-4587",
"modified" : "2022-08-11T22:13:10Z",
"published" : "2022-08-02T18:00:33Z",
"aliases" : [ "CVE-2022-35924" ],
"summary" : "NextAuth.js before 4.10.3 and 3.29.10 sending verification requests (magic link) to unwanted emails",
"details" : "### Impact\n`next-auth` users who are using the `EmailProvider` either in versions before `4.10.3` or `3.29.10` are affected.\n\nIf an attacker could forge a request that sent a comma-separated list of emails (eg.: `attacker@attacker.com,victim@victim.com`) 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 `attacker@attacker.com,victim@victim.com`. 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.\n\n### Patches\nWe patched this vulnerability 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)\n\nTo upgrade, run one of the following:\n```sh\nnpm i next-auth@latest\n```\n```sh\nyarn add next-auth@latest\n```\n```sh\npnpm add next-auth@latest\n```\n\n(This will update to the latest v4 version, but you can change `latest` to `3` if you want to stay on v3. This is not recommended. v3 is unmaintained.)\n\n### Workarounds\nIf for some reason you cannot upgrade, you can normalize the incoming request like the following, using Advanced Initialization:\n```ts\n// pages/api/auth/[...nextauth].ts\n\nfunction normalize(identifier) {\n // Get the first two elements only,\n // separated by `@` from user input.\n let [local, domain] = identifier.toLowerCase().trim().split(\"@\")\n // The part before \"@\" can contain a \",\"\n // but we remove it on the domain part\n domain = domain.split(\",\")[0]\n return `${local}@${domain}`\n}\n\nexport default async function handler(req, res) {\n if (req.body.email) req.body.email = normalize(req.body.email)\n return await NextAuth(req, res, {/* your options */ })\n}\n```\n\n### References\n- EmailProvider: https://next-auth.js.org/providers/email\n- Normalize the email address: https://next-auth.js.org/providers/email#normalizing-the-email-address\n- Email syntax: https://en.wikipedia.org/wiki/Email_address#Local-part\n- `signIn` callback: https://next-auth.js.org/configuration/callbacks#sign-in-callback\n- Advanced Initialization: https://next-auth.js.org/configuration/initialization#advanced-initialization\n- `nodemailer` address: https://nodemailer.com/message/addresses\n\n### For more information\n\nIf you have any concerns, we request responsible disclosure, outlined here: https://next-auth.js.org/security#reporting-a-vulnerability\n\n### Timeline\n\nThe issue was reported 26th of July, a response was sent out in less than 1 hour and after identifying the issue a patch was published within 5 working days.\n\n### Acknowledgments\n\nWe would like to thank [Socket](https://socket.dev) for disclosing this vulnerability in a responsible manner and following up until it got published.",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "npm",
"name" : "next-auth"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "4.0.0"
}, {
"fixed" : "4.10.3"
} ]
} ]
}, {
"package" : {
"ecosystem" : "npm",
"name" : "next-auth"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"fixed" : "3.29.10"
} ]
} ]
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/nextauthjs/next-auth/security/advisories/GHSA-xv97-c62v-4587"
}, {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2022-35924"
}, {
"type" : "WEB",
"url" : "https://github.com/nextauthjs/next-auth/commit/afb1fcdae3cc30445038ef588e491d139b916003"
}, {
"type" : "WEB",
"url" : "https://en.wikipedia.org/wiki/Email_address#Local-part"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/nextauthjs/next-auth"
}, {
"type" : "WEB",
"url" : "https://next-auth.js.org/configuration/callbacks#sign-in-callback"
}, {
"type" : "WEB",
"url" : "https://next-auth.js.org/configuration/initialization#advanced-initialization"
}, {
"type" : "WEB",
"url" : "https://next-auth.js.org/providers/email"
}, {
"type" : "WEB",
"url" : "https://next-auth.js.org/providers/email#normalizing-the-e-mail-address"
}, {
"type" : "WEB",
"url" : "https://next-auth.js.org/providers/email#normalizing-the-email-address"
}, {
"type" : "WEB",
"url" : "https://nodemailer.com/message/addresses"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-20", "CWE-863" ],
"severity" : "CRITICAL",
"github_reviewed" : true,
"github_reviewed_at" : "2022-08-02T18:00:33Z",
"nvd_published_at" : "2022-08-02T18:15:00Z"
}
}