next-auth v3 users before version 3.29.2 are impacted. next-auth version 4 users before version 4.3.2 are also impacted. Upgrading to 3.29.2 or 4.3.2 will patch this vulnerability. If you are not able to upgrade for any reason, you can add a configuration to your callbacks option. If you already have a `redirect` callback, make sure that you match the incoming `url` origin against the `baseUrl`.
This attack-focused weakness is caused by incorrectly implemented authentication schemes that are subject to spoofing attacks.
The web application accepts a user-controlled input that specifies a link to an external site, and uses that link in a redirect.
Link | Tags |
---|---|
https://github.com/nextauthjs/next-auth/security/advisories/GHSA-f9wg-5f46-cjmw | third party advisory mitigation |
https://next-auth.js.org/configuration/callbacks#redirect-callback | vendor advisory |
https://next-auth.js.org/getting-started/upgrade-v4 | vendor advisory |