CVE-2024-58133
First published: Sun Apr 06 2025(Updated: )
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.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| ChainMaker | <2.4.0 |
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-58133?
CVE-2024-58133 has a severity rating that indicates a potential for panic during concurrent writes due to mishandled logging.
How do I fix CVE-2024-58133?
To fix CVE-2024-58133, upgrade to ChainMaker chainmaker-go version 2.4.0 or later.
What systems are affected by CVE-2024-58133?
CVE-2024-58133 affects all versions of ChainMaker chainmaker-go prior to 2.4.0.
What kind of conflict does CVE-2024-58133 cause?
CVE-2024-58133 causes a read-write conflict due to concurrent log writes while updating the configuration.
What should I do if I cannot upgrade to a fixed version for CVE-2024-58133?
If upgrading is not possible for CVE-2024-58133, consider limiting concurrent writes and monitoring for any logging issues.
- collector/mitre-cve
- source/MITRE
- agent/description
- agent/type
- agent/first-publish-date
- agent/references
- agent/guess-ai
- agent/software-canonical-lookup
- agent/software-canonical-lookup-request
- agent/softwarecombine
- collector/nvd-api
- source/NVD
- agent/severity
- agent/last-modified-date
- agent/weakness
- agent/author
- agent/source
- agent/tags
- agent/event
- vendor/chainmaker
- canonical/chainmaker