GHSA-pgjx-7f9g-9463

Dashboard / Vulnerabilities / GHSA-pgjx-7f9g-9463

GHSA-pgjx-7f9g-9463

Summary: Improper handling of email input

Details: ### Impact 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.: `[email protected], <a href="http://attacker.com">Before signing in, claim your money!</a>`. This was previously sent to `[email protected]`, 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. See our [migration guide](https://next-auth.js.org/getting-started/upgrade-v4)) next-auth v4 users before version 4.8.0 are impacted. ### Patches We've released patches for this vulnerability in: - v3 - `3.29.8` - v4 - `4.9.0` You can do: ```sh npm i next-auth@latest # or yarn add next-auth@latest # pnpm add next-auth@latest ``` (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.) ### Workarounds 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. Check out https://next-auth.js.org/providers/email#customizing-emails ### References Related documentation: - https://next-auth.js.org/providers/email#customizing-emails - https://next-auth.js.org/getting-started/upgrade-v4 A test case has been added so this kind of issue will be checked before publishing. See: https://github.com/nextauthjs/next-auth/blob/cd6ccfde898037290ae949d500ace8a378376cd8/packages/next-auth/tests/email.test.ts ### For more information If you have any concerns, we request responsible disclosure, outlined here: https://next-auth.js.org/security#reporting-a-vulnerability ### Timeline The issue was reported 2022 June 29th, a response was sent out to the reporter in less than 1 hour, and after identifying the issue a patch was published within 4 working days.

References: https://github.com/nextauthjs/next-auth/security/advisories/GHSA-pgjx-7f9g-9463, https://nvd.nist.gov/vuln/detail/CVE-2022-31127, https://github.com/nextauthjs/next-auth/commit/ae834f1e08a4a9915665eecb9479c74c6b039c9c, https://github.com/nextauthjs/next-auth, https://github.com/nextauthjs/next-auth/releases/tag/next-auth%40v4.9.0, https://next-auth.js.org/getting-started/upgrade-v4, https://next-auth.js.org/providers/email#customizing-emails