In versions `<=8.5.1` of `jsonwebtoken` library, lack of algorithm definition in the `jwt.verify()` function can lead to signature validation bypass due to defaulting to the `none` algorithm for signature verification. Users are affected if you do not specify algorithms in the `jwt.verify()` function. This issue has been fixed, please update to version 9.0.0 which removes the default support for the none algorithm in the `jwt.verify()` method. There will be no impact, if you update to version 9.0.0 and you don’t need to allow for the `none` algorithm. If you need 'none' algorithm, you have to explicitly specify that in `jwt.verify()` options.
oryginał ENCVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:H/A:LAuth0 Jsonwebtoken
APPAuth0≤ 8.5.1
Powiązane podatności
In jsonwebtoken node module before 4.2.2 it is possible for an attacker to bypass verification when a token di...
Versions `<=8.5.1` of `jsonwebtoken` library could be misconfigured so that legacy, insecure key types are use...
jsonwebtoken is an implementation of JSON Web Tokens. Versions `<= 8.5.1` of `jsonwebtoken` library can be mis...
An issue was discovered in the Login by Auth0 plugin before 4.0.0 for WordPress. It has numerous fields that c...
Auth0 Auth0-WCF-Service-JWT before 1.0.4 leaks the expected JWT signature in an error message when it cannot s...