Quick answers
- Is This vulnerability exploited in the wild?
- No. Junglewise Threat Intelligence has no report of This vulnerability being exploited in the wild.
- How severe is This vulnerability?
- Informational severity, published 3 August 2020.
- Which products and versions are affected?
- Hokaccha Node-Jwt-Simple before 0.3.1; jwt-simple (npm) SEMVER:introduced=0,fixed=0.3.1.
- Is there a fix for This vulnerability?
- Yes. jwt-simple (npm): upgrade to 0.3.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is This vulnerability attacked?
- It is attacked over the network, in a software library.
- Am I affected?
- Check whether you run Hokaccha Node-Jwt-Simple or jwt-simple (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- jwt-simple (npm): upgrade to 0.3.1 or later
npm install jwt-simple@0.3.1
Technical details
The vulnerability involved improper algorithm handling in the JWT decode/verification method. The library initially did not properly enforce or validate the algorithm parameter during token verification, potentially allowing an attacker to specify or override the algorithm used for signature validation. This advisory was withdrawn as a duplicate of GHSA-vgrx-w6rg-8fqf, indicating the same issue was tracked elsewhere. The fix involved adding an explicit algorithm parameter to the decode method that overrides the token's embedded algorithm specification and performs verification with the specified algorithm.
Affected products
- hokaccha node-jwt-simple before 0.3.1
Timeline
- 2020-08-03: disclosed
- other: Advisory withdrawn as duplicate of GHSA-vgrx-w6rg-8fqf