CVE-2024-58132
First published: Sun Apr 06 2025(Updated: )
In chainmaker-go (aka ChainMaker) before 2.3.6, multiple updates to a single node's configuration can cause other normal nodes to perform concurrent read and write operations on a map, leading to a panic.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| ChainMaker | <2.3.6 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2024-58132?
CVE-2024-58132 has a moderate severity level due to potential panic conditions affecting node operations.
How do I fix CVE-2024-58132?
To fix CVE-2024-58132, upgrade to ChainMaker chainmaker-go version 2.3.6 or later.
What is the impact of CVE-2024-58132?
The impact of CVE-2024-58132 includes concurrent read and write operations causing node panic and instability.
In which versions of chainmaker-go is CVE-2024-58132 found?
CVE-2024-58132 is found in versions of chainmaker-go prior to 2.3.6.
What causes the vulnerability CVE-2024-58132?
CVE-2024-58132 is caused by multiple updates to a single node's configuration, leading to race conditions in map operations.
- collector/mitre-cve
- source/MITRE
- agent/references
- agent/weakness
- agent/description
- agent/type
- agent/first-publish-date
- agent/guess-ai
- agent/software-canonical-lookup
- agent/softwarecombine
- collector/nvd-api
- source/NVD
- agent/severity
- agent/last-modified-date
- agent/source
- agent/author
- agent/tags
- agent/event
- vendor/chainmaker
- canonical/chainmaker