Fix broken JWT expiration check in SEP-10 authentication#226
Open
CassioMG wants to merge 2 commits intorelease/1.10.0from
Open
Fix broken JWT expiration check in SEP-10 authentication#226CassioMG wants to merge 2 commits intorelease/1.10.0from
CassioMG wants to merge 2 commits intorelease/1.10.0from
Conversation
There was a problem hiding this comment.
Pull request overview
This pull request fixes a critical security bug in the SEP-10 authentication flow where JWT token expiration was never validated due to accessing a non-existent property on the decoded JWT object.
Changes:
- Fixed JWT expiration validation to correctly access
parsedToken.payload.expinstead of the non-existentparsedToken.expiresAt - Exported
validateTokenfunction with@internalJSDoc annotation for testing purposes - Added
stripInternal: trueto tsconfig.json to prevent internal APIs from appearing in public type declarations - Added comprehensive test suite for JWT decoding and token validation
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated 2 comments.
| File | Description |
|---|---|
| @stellar/typescript-wallet-sdk/src/walletSdk/Auth/index.ts | Fixed JWT expiration check to access correct property path and exported validateToken for testing |
| @stellar/typescript-wallet-sdk/test/auth.test.ts | Added comprehensive tests for JWT structure and token validation including expiration checks |
| @stellar/typescript-wallet-sdk/tsconfig.json | Added stripInternal flag to exclude @internal APIs from type declarations |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 3 out of 3 changed files in this pull request and generated no new comments.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
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.
Fix broken JWT expiration check in SEP-10 authentication
Summary
The
validateTokenfunction in the SEP-10 auth flow never rejected expired tokens. This was caused by accessing a non-existent property on the decoded JWT object, which silently evaluated toundefined— and sinceundefined < numberis alwaysfalsein JavaScript, the expiration check was a no-op.Bug
jws.decode()returns{ header, payload, signature }, but the code was readingparsedToken.expiresAt— a property that doesn't exist on the decoded object. Theexpclaim actually lives atparsedToken.payload.exp.Before (broken):
After (fixed):
Notably,
AuthToken.from()inTypes/auth.tsalready readsdecoded.payload.expcorrectly thus returning a token with a validexpiresAtvalue.