Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1359 CNY

100%
Buy Us a Coffee

CVE-2022-23541— jsonwebtoken's insecure implementation of key retrieval function could lead to Forgeable Public/Private Tokens from RSA to HMAC

Quick assessment

Affected
auth0 node-jsonwebtoken
Exploitation
No confirmed in-the-wild exploitation; assess based on exposure
Recommended action
Check the vendor advisory and references for a fixed version. If immediate upgrade is impossible, restrict exposure and increase monitoring.

jsonwebtoken是Auth0开源的一个 JSON Web 令牌的实现。 jsonwebtoken 8.5.1版本及之前版本存在安全漏洞，该漏洞源于密钥检索函数将导致令牌验证错误。

CVSS 5.0 · Medium EPSS 0.77% · P54

Possible ATT&CK Techniques 1 AI

T1190 · Exploit Public-Facing Application
Get alerts for future matching vulnerabilities Log in to subscribe

I. Basic Information for CVE-2022-23541

Vulnerability Information
Have questions about the vulnerability? See if Shenlong's analysis helps!
View Shenlong Deep Dive ↗

Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.

Vulnerability Title
jsonwebtoken's insecure implementation of key retrieval function could lead to Forgeable Public/Private Tokens from RSA to HMAC
Source: CVE Program / CVE List V5
Vulnerability Description
jsonwebtoken is an implementation of JSON Web Tokens. Versions `<= 8.5.1` of `jsonwebtoken` library can be misconfigured so that passing a poorly implemented key retrieval function referring to the `secretOrPublicKey` argument from the readme link will result in incorrect verification of tokens. There is a possibility of using a different algorithm and key combination in verification, other than the one that was used to sign the tokens. Specifically, tokens signed with an asymmetric public key could be verified with a symmetric HS256 algorithm. This can lead to successful validation of forged tokens. If your application is supporting usage of both symmetric key and asymmetric key in jwt.verify() implementation with the same key retrieval function. This issue has been patched, please update to version 9.0.0.
Source: CVE Program / CVE List V5
CVSS Information
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:L
Source: CVE Program / CVE List V5
Vulnerability Type
认证机制不恰当
Source: CVE Program / CVE List V5
Vulnerability Title
jsonwebtoken 安全漏洞
Source: CNNVD (China National Vulnerability Database)
Vulnerability Description
jsonwebtoken是Auth0开源的一个 JSON Web 令牌的实现。 jsonwebtoken 8.5.1版本及之前版本存在安全漏洞，该漏洞源于密钥检索函数将导致令牌验证错误。
Source: CNNVD (China National Vulnerability Database)
CVSS Information
N/A
Source: CNNVD (China National Vulnerability Database)
Vulnerability Type
N/A
Source: CNNVD (China National Vulnerability Database)

Affected Products

Vendor Product Affected Versions CPE Subscribe
auth0 node-jsonwebtoken <= 8.5.1 -

II. Public POCs for CVE-2022-23541

# POC Description Source Link Shenlong Link
AI-Generated POC Premium

No public POC found.

Login to generate AI POC

III. Intelligence Information for CVE-2022-23541

请登录查看更多情报信息。

Patches & Fixes for CVE-2022-23541 (1)

Vendor Advisories for CVE-2022-23541 (2)

Other References for CVE-2022-23541 (1)

Same Patch Batch · auth0 · 2022-12-22 · 3 CVEs total

CVE-2022-23540 6.4 MEDIUM jsonwebtoken vulnerable to signature validation bypass due to insecure default algorithm i
CVE-2022-23539 5.9 MEDIUM jsonwebtoken unrestricted key type could lead to legacy keys usage

IV. Related Vulnerabilities

Same product: node-jsonwebtoken
Same vendor: auth0
Same weakness: CWE-287

V. Comments for CVE-2022-23541

No comments yet

Leave a comment