GitLab Branch Source Plugin up to 684.vea_fa_7c1e2fe3 on Jenkins Webhook Token comparison

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.9$0-$5k0.00

Summaryinfo

A vulnerability has been found in GitLab Branch Source Plugin up to 684.vea_fa_7c1e2fe3 on Jenkins and classified as problematic. This issue affects some unknown processing of the component Webhook Token Handler. Performing a manipulation results in comparison. This vulnerability was named CVE-2024-23903. The attack may be initiated remotely. There is no available exploit. The affected component should be upgraded.

Detailsinfo

A vulnerability, which was classified as problematic, was found in GitLab Branch Source Plugin up to 684.vea_fa_7c1e2fe3 on Jenkins (Bug Tracking Software). This affects an unknown part of the component Webhook Token Handler. The manipulation with an unknown input leads to a comparison vulnerability. CWE is classifying the issue as CWE-697. The product compares two entities in a security-relevant context, but the comparison is incorrect, which may lead to resultant weaknesses. This is going to have an impact on integrity.

The weakness was presented 01/24/2024. It is possible to read the advisory at jenkins.io. This vulnerability is uniquely identified as CVE-2024-23903. The technical details are unknown and an exploit is not publicly available.

Upgrading eliminates this vulnerability.

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Type

Name

Version

License

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 5.0
VulDB Meta Temp Score: 4.9

VulDB Base Score: 4.3
VulDB Temp Score: 4.1
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 5.3
NVD Vector: 🔍

CNA Base Score: 5.3
CNA Vector: 🔍

CVSSv2info

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

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

Exploitinginfo

Class: Comparison
CWE: CWE-697
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

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: 🔍

Timelineinfo

01/23/2024 🔍
01/24/2024 +1 days 🔍
01/24/2024 +0 days 🔍
08/30/2024 +219 days 🔍

Sourcesinfo

Advisory: jenkins.io
Status: Confirmed

CVE: CVE-2024-23903 (🔍)
GCVE (CVE): GCVE-0-2024-23903
GCVE (VulDB): GCVE-100-252003

Entryinfo

Created: 01/24/2024 19:11
Updated: 08/30/2024 04:51
Changes: 01/24/2024 19:11 (37), 02/18/2024 09:46 (2), 02/18/2024 09:50 (11), 08/30/2024 04:51 (27)
Complete: 🔍
Cache ID: 216::103

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Do you want to use VulDB in your project?

Use the official API to access entries easily!