CVE-2022-31127: Improper handling of email input in next-auth
nextauthjs · next-auth
Vendor fix available · Affected: nextauthjs next-auth · Exploitation: possible (1 to 10%)
Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.
Higher than 66% of scored CVEs
DescriptionCVE.org
NextAuth.js is a complete open source authentication solution for Next.js applications. An attacker can pass a compromised input to the e-mail [signin endpoint](https://next-auth.js.org/getting-started/rest-api#post-apiauthsigninprovider) that contains some malicious HTML, tricking the e-mail server to send it to the user, so they can perform a phishing attack. Eg.: `balazs@email.com, <a href="http://attacker.com">Before signing in, claim your money!</a>`. This was previously sent to `balazs@email.com`, and the content of the email containing a link to the attacker's site was rendered in the HTML. This has been remedied in the following releases, by simply not rendering that e-mail in the HTML, since it should be obvious to the receiver what e-mail they used: next-auth v3 users before version 3.29.8 are impacted. (We recommend upgrading to v4, as v3 is considered unmaintained. next-auth v4 users before version 4.9.0 are impacted. If for some reason you cannot upgrade, the workaround requires you to sanitize the `email` parameter that is passed to `sendVerificationRequest` and rendered in the HTML. If you haven't created a custom `sendVerificationRequest`, you only need to upgrade. Otherwise, make sure to either exclude `email` from the HTML body or efficiently sanitize it.
Affected products1
From the CVE record. A product or version that is not listed is unknown, not unaffected.
- nextauthjs · next-auth< 3.29.8; >= 4.0.0, < 4.9.0
On the Atlas
Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.
- Exploitation
- Possible (1 to 10%). EPSS between 1% and 10%.
- CISA KEV
- Not listed
- Public check
- No public nuclei template
- Weakness
- Cross-site Scripting
- Vendor
- nextauthjs
- Published
- July 2022
CoverageNo articles yet
No CyberSIXT article names CVE-2022-31127 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.
References
- NVD entrynvd.nist.gov
- CVE recordcve.org
- Weakness CWE-79cwe.mitre.org
- next-auth.js.org/getting-started/upgrade-v4next-auth.js.org
- github.com/nextauthjs/next-auth/security/advisories/GHSA-pgjx-7fgithub.com
- github.com/nextauthjs/next-auth/commit/ae834f1e08a4a9915665eecb9github.com
- github.com/nextauthjs/next-auth/releases/tag/next-auth%40v4.9.0github.com
- next-auth.js.org/providers/email#customizing-emailsnext-auth.js.org