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.
Metrics
Affected Vendors & Products
References
| Link | Providers |
|---|---|
| https://git.chainmaker.org.cn/chainmaker/issue/-/issues/1228 |
|
History
Mon, 07 Apr 2025 17:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Sun, 06 Apr 2025 03:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Weaknesses | CWE-821 | |
| Metrics |
cvssV3_1
|
Sun, 06 Apr 2025 03:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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. | |
| References |
|
Status: PUBLISHED
Assigner: mitre
Published: 2025-04-06T00:00:00.000Z
Updated: 2025-04-07T16:24:00.157Z
Reserved: 2025-04-06T00:00:00.000Z
Link: CVE-2024-58133
Updated: 2025-04-07T16:23:56.152Z
Status : Awaiting Analysis
Published: 2025-04-06T03:15:15.437
Modified: 2025-04-07T14:17:50.220
Link: CVE-2024-58133
No data.