JWT up to 3.4.5/4.0.3/4.1.4 Token data authenticity

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
4.0$0-$5k0.00

Summaryinfo

A vulnerability classified as problematic has been found in JWT up to 3.4.5/4.0.3/4.1.4. Affected by this issue is some unknown functionality of the component Token Handler. Performing a manipulation results in data authenticity. This vulnerability is known as CVE-2021-41106. Attacking locally is a requirement. No exploit is available. It is recommended to upgrade the affected component.

Detailsinfo

A vulnerability was found in JWT up to 3.4.5/4.0.3/4.1.4. It has been classified as problematic. This affects some unknown processing of the component Token Handler. The manipulation with an unknown input leads to a data authenticity vulnerability. CWE is classifying the issue as CWE-345. The product does not sufficiently verify the origin or authenticity of data, in a way that causes it to accept invalid data. This is going to have an impact on confidentiality, and integrity.

The weakness was published 09/29/2021 as GHSA-7322-jrq4-x5hf. The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2021-41106 since 09/15/2021. Neither technical details nor an exploit are publicly available.

Upgrading to version 3.4.6, 4.0.4 or 4.1.5 eliminates this vulnerability. Applying the patch 8175de5b841fbe3fd97d2d49b3fc15c4ecb39a73 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Name

Version

License

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 4.0
VulDB Meta Temp Score: 4.0

VulDB Base Score: 4.4
VulDB Temp Score: 4.2
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 3.3
NVD Vector: 🔍

CNA Base Score: 4.4
CNA Vector (GitHub, Inc.): 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

NVD Base Score: 🔍

Exploitinginfo

Class: Data authenticity
CWE: CWE-345
CAPEC: 🔍
ATT&CK: 🔍

Physical: Partially
Local: Yes
Remote: No

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔍

Upgrade: JWT 3.4.6/4.0.4/4.1.5
Patch: 8175de5b841fbe3fd97d2d49b3fc15c4ecb39a73

Timelineinfo

09/15/2021 🔍
09/29/2021 +14 days 🔍
09/29/2021 +0 days 🔍
11/18/2025 +1511 days 🔍

Sourcesinfo

Advisory: GHSA-7322-jrq4-x5hf
Status: Confirmed
Confirmation: 🔍

CVE: CVE-2021-41106 (🔍)
GCVE (CVE): GCVE-0-2021-41106
GCVE (VulDB): GCVE-100-183525

Entryinfo

Created: 09/29/2021 07:50
Updated: 11/18/2025 16:30
Changes: 09/29/2021 07:50 (50), 10/03/2021 16:48 (2), 10/03/2021 16:55 (1), 11/18/2025 16:30 (33)
Complete: 🔍
Cache ID: 216::103

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Do you need the next level of professionalism?

Upgrade your account now!