VDB-258802 · CVE-2024-31033 · Bug 930

JJWT up to 0.12.5 setSigningKey privilege escalation

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.
5.6	$0-$5k	0.00

Summaryinfo

A vulnerability described as problematic has been identified in JJWT up to 0.12.5. Impacted is the function setSigningKey. Executing a manipulation can lead to an unknown weakness. This vulnerability is tracked as CVE-2024-31033. No exploit exists.

Detailsinfo

A vulnerability was found in JJWT up to 0.12.5. It has been declared as problematic. The impact remains unknown. CVE summarizes:

JJWT (aka Java JWT) through 0.12.5 ignores certain characters and thus a user might falsely conclude that they have a strong key. The impacted code is the setSigningKey() method within the DefaultJwtParser class and the signWith() method within the DefaultJwtBuilder class.

The advisory is available at github.com. This vulnerability was named CVE-2024-31033 since 03/27/2024. The exploitation appears to be difficult. Technical details are known, but there is no available exploit.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

If you want to get best quality of vulnerability data, you may have to visit VulDB.

Productinfo

Name

JJWT

Version

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 5.7
VulDB Meta Temp Score: 5.6

VulDB Base Score: 4.6
VulDB Temp Score: 4.5
VulDB Vector: 🔍
VulDB Reliability: 🔍

CNA Base Score: 6.8
CNA Vector: 🔍

CVSSv2info

AV	AC	Au	C	I	A
💳	💳	💳	💳	💳	💳
💳	💳	💳	💳	💳	💳
💳	💳	💳	💳	💳	💳

Vector	Complexity	Authentication	Confidentiality	Integrity	Availability
Unlock	Unlock	Unlock	Unlock	Unlock	Unlock
Unlock	Unlock	Unlock	Unlock	Unlock	Unlock
Unlock	Unlock	Unlock	Unlock	Unlock	Unlock

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

Exploitinginfo

Class: Privilege escalation
CWE: Unknown
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

Availability: 🔍
Status: Not defined

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-Day	Unlock	Unlock	Unlock	Unlock
Today	Unlock	Unlock	Unlock	Unlock

Threat Intelligenceinfo

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

Countermeasuresinfo

Recommended: no mitigation known
Status: 🔍

0-Day Time: 🔍

Timelineinfo

03/27/2024 🔍
04/01/2024 +4 days 🔍
04/01/2024 +0 days 🔍
08/28/2024 +148 days 🔍

Sourcesinfo

Advisory: 930
Status: Not defined

CVE: CVE-2024-31033 (🔍)
GCVE (CVE): GCVE-0-2024-31033
GCVE (VulDB): GCVE-100-258802

Entryinfo

Created: 04/01/2024 07:56
Updated: 08/28/2024 01:11
Changes: 04/01/2024 07:56 (49), 05/08/2024 11:20 (1), 08/02/2024 18:37 (1), 08/28/2024 01:11 (11)
Complete: 🔍
Cache ID: 216::103