cloudflare-workers-and-pages[bot]
commented
1 year ago Deploying with 
Cloudflare Pages
| Latest commit: |
27e7d32
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://bab68efd.blink.pages.dev |
| Branch Preview URL: | https://renovate-npm-jsonwebtoken-vu.blink.pages.dev |
vercel[bot]
This PR contains the following updates:
8.5.1->9.0.0GitHub Vulnerability Alerts
CVE-2022-23539
Overview
Versions
<=8.5.1ofjsonwebtokenlibrary could be misconfigured so that legacy, insecure key types are used for signature verification. For example, DSA keys could be used with the RS256 algorithm.Am I affected?
You are affected if you are using an algorithm and a key type other than the combinations mentioned below
And for Elliptic Curve algorithms:
algHow do I fix it?
Update to version 9.0.0. This version validates for asymmetric key type and algorithm combinations. Please refer to the above mentioned algorithm / key type combinations for the valid secure configuration. After updating to version 9.0.0, If you still intend to continue with signing or verifying tokens using invalid key type/algorithm value combinations, you’ll need to set the
allowInvalidAsymmetricKeyTypesoption totruein thesign()and/orverify()functions.Will the fix impact my users?
There will be no impact, if you update to version 9.0.0 and you already use a valid secure combination of key type and algorithm. Otherwise, use the
allowInvalidAsymmetricKeyTypesoption totruein thesign()andverify()functions to continue usage of invalid key type/algorithm combination in 9.0.0 for legacy compatibility.CVE-2022-23540
Overview
In versions
<=8.5.1ofjsonwebtokenlibrary, lack of algorithm definition in thejwt.verify()function can lead to signature validation bypass due to defaulting to thenonealgorithm for signature verification.Am I affected?
You will be affected if you do not specify algorithms in the
jwt.verify()functionHow do I fix it?
Update to version 9.0.0 which removes the default support for the none algorithm in the
jwt.verify()method.Will the fix impact my users?
There will be no impact, if you update to version 9.0.0 and you don’t need to allow for the
nonealgorithm. If you need 'none' algorithm, you have to explicitly specify that injwt.verify()options.CVE-2022-23541
Overview
Versions
<=8.5.1ofjsonwebtokenlibrary can be misconfigured so that passing a poorly implemented key retrieval function (referring to thesecretOrPublicKeyargument from the readme link) will result in incorrect verification of tokens. There is a possibility of using a different algorithm and key combination in verification than the one that was used to sign the tokens. Specifically, tokens signed with an asymmetric public key could be verified with a symmetric HS256 algorithm. This can lead to successful validation of forged tokens.Am I affected?
You will be affected if your application is supporting usage of both symmetric key and asymmetric key in jwt.verify() implementation with the same key retrieval function.
How do I fix it?
Update to version 9.0.0
Will the fix impact my users?
There is no impact for end users
CVE-2022-23529
Overview
For versions
<=8.5.1ofjsonwebtokenlibrary, if a malicious actor has the ability to modify the key retrieval parameter (referring to thesecretOrPublicKeyargument from the readme link) of thejwt.verify()function, they can gain remote code execution (RCE).Am I affected?
You are affected only if you allow untrusted entities to modify the key retrieval parameter of the
jwt.verify()on a host that you control.How do I fix it?
Update to version 9.0.0
Will the fix impact my users?
The fix has no impact on end users.
Credits
Palo Alto Networks
Configuration
📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.