-
Notifications
You must be signed in to change notification settings - Fork 679
fix(auth): fail closed on non-finite JWT nbf and exp #8895
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
SashaMIT
wants to merge
2
commits into
thirdweb-dev:main
Choose a base branch
from
SashaMIT:fix/auth-jwt-fail-closed-exp-nbf
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+104
−4
Open
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,5 @@ | ||
| --- | ||
| "thirdweb": patch | ||
| --- | ||
|
|
||
| Reject JWTs whose nbf or exp is missing or not a finite number instead of skipping the time-bound checks. |
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🔒 Security & Privacy | 🟡 Minor | ⚡ Quick win
🧩 Analysis chain
🏁 Script executed:
Repository: thirdweb-dev/js
Length of output: 28977
🏁 Script executed:
Repository: thirdweb-dev/js
Length of output: 6617
🌐 Web query:
RFC 7519 Section 4.1.4 exp claim current date and time MUST be before expiration time💡 Result:
According to Section 4.1.4 of RFC 7519, the exp (expiration time) claim identifies the time on or after which the JSON Web Token (JWT) must not be accepted for processing [1][2]. The specification explicitly states that the processing of this claim requires that the current date and time must be before the expiration date and time listed in the exp claim [1][2]. Implementers are permitted to provide for small amounts of leeway—typically no more than a few minutes—to account for clock skew between systems [2].
Citations:
Reject JWTs at the
expboundary.Use
currentTime >= expbecause JWTs must not be accepted when the current time equalsexp. Add a fixed-clock test for this boundary.🤖 Prompt for AI Agents