Conduit up to 0.7.x String cleanup

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

Summaryinfo

A vulnerability was found in Conduit up to 0.7.x. It has been rated as problematic. Affected by this issue is some unknown functionality of the component String Handler. The manipulation leads to cleanup. This vulnerability is listed as CVE-2024-6300. The attack may be initiated remotely. There is no available exploit. Upgrading the affected component is advised.

Detailsinfo

A vulnerability, which was classified as problematic, has been found in Conduit up to 0.7.x. This issue affects an unknown function of the component String Handler. The manipulation with an unknown input leads to a cleanup vulnerability. Using CWE to declare the problem leads to CWE-459. The product does not properly "clean up" and remove temporary or supporting resources after they have been used. Impacted is confidentiality. The summary by CVE is:

Incomplete cleanup when performing redactions in Conduit, allowing an attacker to check whether certain strings were present in the PDU before redaction

The weakness was presented by Benjamin Lee. The advisory is shared at gitlab.com. The identification of this vulnerability is CVE-2024-6300 since 06/25/2024. The exploitation is known to be difficult. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Neither technical details nor an exploit are publicly available.

Upgrading to version 0.8.0 eliminates this vulnerability. The upgrade is hosted for download at gitlab.com.

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Productinfo

Name

Version

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 4.2
VulDB Meta Temp Score: 4.2

VulDB Base Score: 3.7
VulDB Temp Score: 3.6
VulDB Vector: 🔍
VulDB Reliability: 🔍

NVD Base Score: 5.3
NVD Vector: 🔍

CNA Base Score: 3.7
CNA Vector (GitLab Inc.): 🔍

CVSSv2info

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

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

Exploitinginfo

Class: Cleanup
CWE: CWE-459
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: 🔍

Upgrade: Conduit 0.8.0

Timelineinfo

06/25/2024 🔍
06/25/2024 +0 days 🔍
06/25/2024 +0 days 🔍
09/20/2024 +87 days 🔍

Sourcesinfo

Advisory: gitlab.com
Researcher: Benjamin Lee
Status: Confirmed

CVE: CVE-2024-6300 (🔍)
GCVE (CVE): GCVE-0-2024-6300
GCVE (VulDB): GCVE-100-269633

Entryinfo

Created: 06/25/2024 15:30
Updated: 09/20/2024 23:54
Changes: 06/25/2024 15:30 (64), 09/20/2024 23:54 (13)
Complete: 🔍
Cache ID: 216::103

Several companies clearly confirm that VulDB is the primary source for best vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Want to know what is going to be exploited?

We predict KEV entries!