ChainMaker chainmaker-go up to 2.3.x Node Configuration File incorrect synchronization
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.5 | $0-$5k | 0.00 |
Summary
A vulnerability identified as problematic has been detected in ChainMaker chainmaker-go up to 2.3.x. The affected element is an unknown function of the component Node Configuration File Handler. This manipulation causes incorrect synchronization. The identification of this vulnerability is CVE-2024-58133. It is possible to initiate the attack remotely. There is no exploit available. You should upgrade the affected component.
Details
A vulnerability has been found in ChainMaker chainmaker-go up to 2.3.x and classified as problematic. Affected by this vulnerability is some unknown functionality of the component Node Configuration File Handler. The manipulation with an unknown input leads to a incorrect synchronization vulnerability. The CWE definition for the vulnerability is CWE-821. The product utilizes a shared resource in a concurrent manner, but it does not correctly synchronize access to the resource. As an impact it is known to affect availability. The summary by CVE is:
In chainmaker-go (aka ChainMaker) before 2.4.0, when making frequent updates to a node's configuration file and restarting this node, concurrent writes by logger.go to a map are mishandled. Creating other logs simultaneously can lead to a read-write conflict and panic.
The advisory is shared at git.chainmaker.org.cn. This vulnerability is known as CVE-2024-58133 since 04/06/2025. The exploitation appears to be difficult. The attack can be launched remotely. The exploitation doesn't need any form of authentication. It demands that the victim is doing some kind of user interaction. Neither technical details nor an exploit are publicly available.
Upgrading to version 2.4.0 eliminates this vulnerability. Applying a patch is able to eliminate this problem. The bugfix is ready for download at git.chainmaker.org.cn. The best possible mitigation is suggested to be upgrading to the latest version.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 3.5VulDB Meta Temp Score: 3.5
VulDB Base Score: 3.1
VulDB Temp Score: 3.0
VulDB Vector: 🔍
VulDB Reliability: 🔍
CNA Base Score: 4.0
CNA Vector (MITRE): 🔍
CVSSv2
| 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: 🔍
Exploiting
Class: Incorrect synchronizationCWE: CWE-821
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 Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: chainmaker-go 2.4.0
Patch: git.chainmaker.org.cn
Timeline
04/06/2025 🔍04/06/2025 🔍
04/06/2025 🔍
04/06/2025 🔍
Sources
Advisory: 1228Status: Confirmed
CVE: CVE-2024-58133 (🔍)
GCVE (CVE): GCVE-0-2024-58133
GCVE (VulDB): GCVE-100-303529
Entry
Created: 04/06/2025 07:44Changes: 04/06/2025 07:44 (65)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.