fix: Update jsonwebtoken to v9.0.0 #2025
Merged
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.
Bumps jsonwebtoken from 8.5.1 to 9.0.0.
verify()
function no longer accepts unsigned tokens by default. Updated the unit tests and the emulator signature verifier to explicitly set{ algorithms: ['none'] }
.rs
key types now must havers
type algorithm in header. Updated the tests to set a custom secret for unsigned (alg: none
) mock keys.HS*
algorithms must use asymmetric keys. Updated theinvalid algorithm
tests toinvalid-rs type
algorithms, instead.jsonwebtoken
v9.0.0 patches the following security fixes:Resolves: #2023
RELEASE NOTES: Bumped the
jsonwebtoken
package tov9.0.0
to address the security issues.