VYPR
Medium severity5.9NVD Advisory· Published Nov 20, 2023· Updated Jun 17, 2026

CVE-2023-48223

CVE-2023-48223

Description

fast-jwt provides fast JSON Web Token (JWT) implementation. Prior to version 3.3.2, the fast-jwt library does not properly prevent JWT algorithm confusion for all public key types. The 'publicKeyPemMatcher' in 'fast-jwt/src/crypto.js' does not properly match all common PEM formats for public keys. To exploit this vulnerability, an attacker needs to craft a malicious JWT token containing the HS256 algorithm, signed with the public RSA key of the victim application. This attack will only work if the victim application utilizes a public key containing the BEGIN RSA PUBLIC KEY header. Applications using the RS256 algorithm, a public key with a BEGIN RSA PUBLIC KEY header, and calling the verify function without explicitly providing an algorithm, are vulnerable to this algorithm confusion attack which allows attackers to sign arbitrary payloads which will be accepted by the verifier. Version 3.3.2 contains a patch for this issue. As a workaround, change line 29 of blob/master/src/crypto.js to include a regular expression.

AI Insight

LLM-synthesized narrative grounded in this CVE's description and references.

Affected packages

Versions sourced from the GitHub Security Advisory.

PackageAffected versionsPatched versions
fast-jwtnpm
< 3.3.23.3.2

Affected products

3
  • Nearform/Fast JWT2 versions
    cpe:2.3:a:nearform:fast-jwt:*:*:*:*:*:node.js:*:*+ 1 more
    • cpe:2.3:a:nearform:fast-jwt:*:*:*:*:*:node.js:*:*range: <3.3.2
    • (no CPE)range: < 3.3.2
  • ghsa-coords
    Range: < 3.3.2

Patches

Vulnerability mechanics

References

6

News mentions

0

No linked articles in our index yet.