fast-jwt is vulnerable to Insufficient Session Expiration
59
Medium Risk
The verifier's clockTolerance option only rejects negative numbers and does not reject a non-finite value, so configuring it as infinite disables both expiry and not-before validation. The tolerance flows into the date-claim comparisons as positive and negative infinity, making every time-based check pass unconditionally. Before the fix, expired or not-yet-active tokens are accepted as valid, and the poisoned values also corrupt the verifier's cache so affected entries stay valid until eviction. The fix requires clockTolerance to be a finite non-negative number.
You are affected if you are using a version that falls within the vulnerable range and you configure the verifier's clockTolerance option to a non-finite value such as Infinity.
fast-jwt is vulnerable to Insufficient Session Expiration in versions 1.5.0 - 6.2.4.
Upgrade the fast-jwt library to the patch version.
Connect your repositories to instantly see whether vulnerable or malicious packages exist in your codebase.
Free. No credit card required.

I consent to receiving marketing communications based on Aikido’s Privacy Policy.
SOC 2Compliant
ISO 27001Compliant