chore(deps): update dependency next-auth to v4.24.12 [security]#55
Open
renovate[bot] wants to merge 1 commit intodevelopfrom
Open
chore(deps): update dependency next-auth to v4.24.12 [security]#55renovate[bot] wants to merge 1 commit intodevelopfrom
renovate[bot] wants to merge 1 commit intodevelopfrom
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
2f8aad8 to
6a0828b
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
4.24.5→4.24.12GitHub Vulnerability Alerts
GHSA-5jpx-9hw9-2fx4
Summary
NextAuth.js's email sign-in can be forced to deliver authentication emails to an attacker-controlled mailbox due to a bug in
nodemailer's address parser used by the project (fixed innodemailerv7.0.7). A crafted input such as:is parsed incorrectly and results in the message being delivered to
e@attacker.com(attacker) instead of"<e@attacker.com>@​victim.com"(the intended recipient atvictim.com) in violation of RFC 5321/5322 semantics. This allows an attacker to receive login/verification links or other sensitive emails intended for the victim.Affected NextAuthjs Version
POC
Example Setup showing misdelivery of email
Mitigation
Update to nodemailer 7.0.7
Credits
https://zeropath.com/ Helped identify this security issue
Release Notes
nextauthjs/next-auth (next-auth)
v4.24.12Compare Source
v4.24.11Compare Source
v4.24.10Compare Source
What's Changed
490a033Full Changelog: https://github.com/nextauthjs/next-auth/compare/next-auth@4.24.9...next-auth@4.24.10
v4.24.9Compare Source
What's Changed
awaitdynamic APIs as per Next.js 15 changes by @balazsorban44 in4d143c5New Contributors
Full Changelog: https://github.com/nextauthjs/next-auth/compare/next-auth@4.24.8...next-auth@4.24.9
v4.24.8Compare Source
What's Changed
identifier@auth/*-adaptersfor v4 by @balazsorban44 in #11562New Contributors
Full Changelog: https://github.com/nextauthjs/next-auth/compare/next-auth@4.24.7...next-auth@4.24.8
v4.24.7Compare Source
Others
v4.24.6Compare Source
Bugfixes
nodemailerimports (#9261) (fa287be)Configuration
📅 Schedule: Branch creation - "" (UTC), Automerge - "before 4am" (UTC).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.