Advisory

GHSA-qwph-4952-7xr6

Also known as: CVE-2022-23540

Summary

jsonwebtoken vulnerable to signature validation bypass due to insecure default algorithm in jwt.verify()

Details

Overview

In versions <=8.5.1 of jsonwebtoken library, lack of algorithm definition and a falsy secret or key in the jwt.verify() function can lead to signature validation bypass due to defaulting to the none algorithm for signature verification.

Am I affected?
You will be affected if all the following are true in the jwt.verify() function:

  • a token with no signature is received
  • no algorithms are specified
  • a falsy (e.g. null, false, undefined) secret or key is passed

How 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 none algorithm. If you need 'none' algorithm, you have to explicitly specify that in jwt.verify() options.

Severity

Medium Basis: The source's own band: MODERATE

Dates

Published
2022-12-22 03:32 UTC
Modified
2025-02-13 18:33 UTC

Affected packages and fixes

jsonwebtoken

npm · All systems

Affected

  • introduced 0, fixed 9.0.0 (semver)

Fixed versions

9.0.0

Fix

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences