fix(auth): restrict non-secure cookie fallback to development environment#3171
Open
nyxsky404 wants to merge 2 commits into
Open
fix(auth): restrict non-secure cookie fallback to development environment#3171nyxsky404 wants to merge 2 commits into
nyxsky404 wants to merge 2 commits into
Conversation
GSSoC Label Checklist 🏷️@Priyanshu-byte-coder — please apply the appropriate labels before merging: Difficulty (pick one):
Quality (optional):
Validation (required to score):
|
d57fa3c to
7567504
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 removes the fallback to the non-secure
next-auth.session-tokenin production environments. Previously, if the__Secure-next-auth.session-tokenwas missing in production, the middleware would attempt to read the insecure cookie by explicitly settingsecureCookie: false. This introduces a severe Session Hijacking vulnerability via Cookie Tossing, allowing attackers to inject insecure session cookies on production instances. The fallback is now strictly limited to development environments, ensuring production requests without the secure cookie are appropriately treated as unauthenticated. Fixes #3167.