What is the vulnerability ID for this vulnerability?

The vulnerability ID for this vulnerability is CVE-2022-24858.

Which versions of next-auth are impacted by this vulnerability?

next-auth v3 users before version 3.29.2 and next-auth version 4 users before version 4.3.2 are impacted by this vulnerability.

How can I fix this vulnerability?

You can fix this vulnerability by upgrading to version 3.29.2 if you are using next-auth v3, or upgrading to version 4.3.2 if you are using next-auth version 4.

What should I do if I am not able to upgrade to the recommended versions?

If you are not able to upgrade, you can add a configuration to your callbacks option or follow the suggested alternatives in the official documentation.

Where can I find more information about this vulnerability?

You can find more information about this vulnerability on the official GitHub Security Advisory and the Next-auth documentation.

Vulnerability/
CVE-2022-24858

medium

6.1

CWE

601 290

19/4/2022

3/8/2024

CVE-2022-24858: Default redirect callback vulnerable to open redirects

First published: Tue Apr 19 2022(Updated: )

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`.

Credit: security-advisories@github.com

Affected Software	Affected Version	How to fix
Nextauth.js Next-auth	>=3.0.0<3.29.2
Nextauth.js Next-auth	>=4.0.0<4.3.2

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the vulnerability ID for this vulnerability?
The vulnerability ID for this vulnerability is CVE-2022-24858.
Which versions of next-auth are impacted by this vulnerability?
next-auth v3 users before version 3.29.2 and next-auth version 4 users before version 4.3.2 are impacted by this vulnerability.
How can I fix this vulnerability?
You can fix this vulnerability by upgrading to version 3.29.2 if you are using next-auth v3, or upgrading to version 4.3.2 if you are using next-auth version 4.
What should I do if I am not able to upgrade to the recommended versions?
If you are not able to upgrade, you can add a configuration to your callbacks option or follow the suggested alternatives in the official documentation.
Where can I find more information about this vulnerability?
You can find more information about this vulnerability on the official GitHub Security Advisory and the Next-auth documentation.

collector/nvd-index
agent/type
agent/weakness
agent/softwarecombine
collector/mitre-cve
source/MITRE
agent/title
agent/last-modified-date
agent/severity
agent/references
agent/author
agent/description
agent/first-publish-date
agent/event
agent/tags
vendor/nextauth.js
canonical/nextauth.js next-auth
version/nextauth.js next-auth/3.0.0
version/nextauth.js next-auth/4.0.0

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co

By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.