CVE-2023-48223: JWT Algorithm Confusion
(updated )
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, is 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.
References
- github.com/advisories/GHSA-c2ff-88x2-x9pg
- github.com/nearform/fast-jwt/blob/master/src/crypto.js
- github.com/nearform/fast-jwt/commit/15a6e92c9adb39acde41a9b11cec0cbde8ad763b
- github.com/nearform/fast-jwt/releases/tag/v3.3.2
- github.com/nearform/fast-jwt/security/advisories/GHSA-c2ff-88x2-x9pg
- nvd.nist.gov/vuln/detail/CVE-2023-48223
Detect and mitigate CVE-2023-48223 with GitLab Dependency Scanning
Secure your software supply chain by verifying that all open source dependencies used in your projects contain no disclosed vulnerabilities. Learn more about Dependency Scanning →