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

Goal: 1000 CNY · Raised: 1359 CNY

100%
Buy Us a Coffee

CVE-2022-23540— jsonwebtoken vulnerable to signature validation bypass due to insecure default algorithm in jwt.verify()

Quick assessment

Affected
auth0 node-jsonwebtoken
Exploitation
Public or AI PoC available; prioritize validation
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版本及之前版本存在数据伪造问题漏洞，该漏洞源于默认使用“none”算法进行签名验证，jwt.verify 函数中缺少算法定义，可能会导致绕过签名验证。

CVSS 6.4 · Medium EPSS 0.55% · P44

Possible ATT&CK Techniques 1 AI

T1550 · Use Alternate Authentication Material
Get alerts for future matching vulnerabilities Log in to subscribe

I. Basic Information for CVE-2022-23540

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 vulnerable to signature validation bypass due to insecure default algorithm in jwt.verify()
Source: CVE Program / CVE List V5
Vulnerability Description
In versions `<=8.5.1` of `jsonwebtoken` library, lack of algorithm definition in the `jwt.verify()` function can lead to signature validation bypass due to defaulting to the `none` algorithm for signature verification. Users are affected if you do not specify algorithms in the `jwt.verify()` function. This issue has been fixed, please update to version 9.0.0 which removes the default support for the none algorithm in the `jwt.verify()` method. 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.
Source: CVE Program / CVE List V5
CVSS Information
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:H/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版本及之前版本存在数据伪造问题漏洞，该漏洞源于默认使用“none”算法进行签名验证，jwt.verify 函数中缺少算法定义，可能会导致绕过签名验证。
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-23540

# POC Description Source Link Shenlong Link
1 CVE-2022-23540 - jwt.verify() method https://github.com/jsirichai/CVE-2022-23540-PoC POC Details
AI-Generated POC Premium

No public POC found.

Login to generate AI POC

III. Intelligence Information for CVE-2022-23540

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

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

Vendor Advisories for CVE-2022-23540 (2)

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

CVE-2022-23539 5.9 MEDIUM jsonwebtoken unrestricted key type could lead to legacy keys usage
CVE-2022-23541 5.0 MEDIUM jsonwebtoken's insecure implementation of key retrieval function could lead to Forgeable P

IV. Related Vulnerabilities

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

V. Comments for CVE-2022-23540

No comments yet

Leave a comment