Authenticated token forgery via algorithm confusion
Published Dec 22, 2022 · Updated Feb 13, 2025
Improper authentication in Auth0 node-jsonwebtoken 8.5.1 and earlier allows remote authenticated users to forge JWTs via algorithm confusion. The jwt.verify key-retrieval path accepts an asymmetric public key while permitting HS256 verification, so a token signed with the public key can pass symmetric validation. Exposure requires one retrieval function to serve both symmetric and asymmetric keys; forged claims can then be accepted as valid by the consuming application.
Summary
What happened
Improper authentication in Auth0 node-jsonwebtoken 8.5.1 and earlier allows remote authenticated users to forge JWTs via algorithm confusion. The jwt.verify key-retrieval path accepts an asymmetric public key while permitting HS256 verification, so a token signed with the public key can pass symmetric validation. Exposure requires one retrieval function to serve both symmetric and asymmetric keys; forged claims can then be accepted as valid by the consuming application.
The record
- CVE
- CVE-2022-23541
- Published
- Dec 22, 2022
- Updated
- Feb 13, 2025
- Vendor
- Auth0
- Product
- node-jsonwebtoken
- Classifications
- CWE-1259, CWE-287, T1606.001
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 22, 2022CVE publishedPublication date reported by the CVE source.
- Feb 13, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=<= 8.5.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo