Skip to content
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

[NEUTRAL] Update dependency jsonwebtoken to v9 #4

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

mend-for-github-com[bot]
Copy link

@mend-for-github-com mend-for-github-com bot commented Jan 23, 2024

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
jsonwebtoken 0.4.0 -> 9.0.0 age adoption passing confidence
@types/jsonwebtoken (source) ^8.5.0 -> ^9.0.0 age adoption passing confidence

By merging this PR, the issue #22 will be automatically resolved and closed:

Severity CVSS Score CVE Reachability
Critical Critical 9.8 CVE-2015-9235
High High 7.1 WS-2018-0096
Medium Medium 6.4 CVE-2022-23540
Medium Medium 5.9 CVE-2022-23539
Medium Medium 5.0 CVE-2022-23541
Medium Medium 4.6 CVE-2016-1000223

Release Notes

auth0/node-jsonwebtoken (jsonwebtoken)

v9.0.0

Compare Source

Breaking changes: See Migration from v8 to v9

Breaking changes
Security fixes
  • security: fixes Arbitrary File Write via verify function - CVE-2022-23529
  • security: fixes Insecure default algorithm in jwt.verify() could lead to signature validation bypass - CVE-2022-23540
  • security: fixes Insecure implementation of key retrieval function could lead to Forgeable Public/Private Tokens from RSA to HMAC - CVE-2022-23541
  • security: fixes Unrestricted key type could lead to legacy keys usage - CVE-2022-23539

v8.5.1

Compare Source

Bug fix
Docs

v8.5.0

Compare Source

New Functionality
Test Improvements
Docs

v8.4.0

Compare Source

New Functionality
Bug Fixes
Docs
Test Improvements
CI

v8.3.0

Compare Source

v8.2.2

Compare Source

v8.2.1

Compare Source

v8.2.0

Compare Source

v8.1.1

Compare Source

v8.1.0

Compare Source

v8.0.1

Compare Source

v8.0.0

Compare Source

Breaking changes: See Migration notes from v7

v7.4.3

Compare Source

  • Fix breaking change on 7.4.2 for empty secret + "none" algorithm (sync code style) (PR 386)

v7.4.2

Compare Source

v7.4.1

Compare Source

v7.4.0

Compare Source

v7.3.0

Compare Source

v7.2.1

Compare Source

v7.2.0

Compare Source

v7.1.10

Compare Source

v7.1.9

Compare Source

v7.1.8

Compare Source

v7.1.7

Compare Source

v7.1.6

Compare Source

v7.1.5

Compare Source

v7.1.3

Compare Source

v7.1.1

Compare Source

v7.1.0

Compare Source

v7.0.1

Compare Source

v7.0.0

Compare Source

v6.2.0

Compare Source

v6.1.2

Compare Source

v6.1.1

Compare Source

v6.1.0

Compare Source

v6.0.1

Compare Source

This was an immediate change after publishing 6.0.0.

v6.0.0

Compare Source

v5.7.0

Compare Source

v5.6.2

Compare Source

v5.6.0

Compare Source

v5.5.4

Compare Source

v5.5.3

Compare Source

v5.5.2

Compare Source

v5.5.1

Compare Source

v5.5.0

Compare Source

v5.4.1

Compare Source

v5.4.0

Compare Source

v5.3.1

Compare Source

v5.2.0

Compare Source

v5.1.0

Compare Source

v5.0.5

Compare Source

v5.0.4

Compare Source

v5.0.3

Compare Source

v5.0.2

Compare Source

v5.0.1

Compare Source

v5.0.0

Compare Source

Changed
  • [sign] Only set defautl iat if the user does not specify that argument.

auth0/node-jsonwebtoken@e900282
auth0/node-jsonwebtoken@35036b1
auth0/node-jsonwebtoken@954bd7a
auth0/node-jsonwebtoken@24a3700
auth0/node-jsonwebtoken@a77df6d

Security
  • [verify] Update to jws@^3.0.0 and renaming header.alg mismatch exception to invalid algorithm and adding more mismatch tests.

As jws@3.0.0 changed the verify method signature to be jws.verify(signature, algorithm, secretOrKey), the token header must be decoded first in order to make sure that the alg field matches one of the allowed options.algorithms. After that, the now validated header.alg is passed to jws.verify

As the order of steps has changed, the error that was thrown when the JWT was invalid is no longer the jws one:

{ [Error: Invalid token: no header in signature 'a.b.c'] code: 'MISSING_HEADER', signature: 'a.b.c' }

That old error (removed from jws) has been replaced by a JsonWebTokenError with message invalid token.

Important: versions >= 4.2.2 this library are safe to use but we decided to deprecate everything < 5.0.0 to prevent security warnings from library node-jws when doing npm install.

auth0/node-jsonwebtoken@634b8ed
auth0/node-jsonwebtoken@9f24ffd
auth0/node-jsonwebtoken@19e6cc6
auth0/node-jsonwebtoken@1e46234
auth0/node-jsonwebtoken@954bd7a
auth0/node-jsonwebtoken@24a3700
auth0/node-jsonwebtoken@a77df6d

v4.2.2

Compare Source

Fixed

v4.2.1

Compare Source

Fixed

v4.2.0

[Compare Source](https://redirect.github.com/aut

@mend-for-github-com mend-for-github-com bot added the security fix Security fix generated by Mend label Jan 23, 2024
@mend-for-github-com mend-for-github-com bot force-pushed the whitesource-remediate/jsonwebtoken-9.x branch from 5cd5fcb to b0d8255 Compare January 26, 2024 16:33
@mend-for-github-com mend-for-github-com bot changed the title Update dependency jsonwebtoken to v9 [NEUTRAL] Update dependency jsonwebtoken to v9 Jan 26, 2024
@mend-for-github-com mend-for-github-com bot force-pushed the whitesource-remediate/jsonwebtoken-9.x branch from b0d8255 to ec39cd5 Compare March 17, 2024 05:30
@mend-for-github-com mend-for-github-com bot force-pushed the whitesource-remediate/jsonwebtoken-9.x branch from ec39cd5 to 45cc2a3 Compare April 16, 2024 05:39
@mend-for-github-com mend-for-github-com bot force-pushed the whitesource-remediate/jsonwebtoken-9.x branch from 45cc2a3 to 44f6162 Compare May 15, 2024 07:05
@mend-for-github-com mend-for-github-com bot force-pushed the whitesource-remediate/jsonwebtoken-9.x branch 2 times, most recently from 3c47ba0 to fa2d766 Compare June 2, 2024 21:17
@mend-for-github-com mend-for-github-com bot force-pushed the whitesource-remediate/jsonwebtoken-9.x branch from fa2d766 to cff9229 Compare June 11, 2024 17:03
@mend-for-github-com mend-for-github-com bot force-pushed the whitesource-remediate/jsonwebtoken-9.x branch from cff9229 to 110003d Compare June 11, 2024 18:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
security fix Security fix generated by Mend
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants