Chainmaker Go
Approved changes feed: RSS · Atom
cpe:2.3:a:chainmaker:chainmaker-go:*:*:*:*:*:*:*:*part: a version: * update: *
| Vendor | Chainmaker (486075fa-fa6a-536d-aa28-138851e4fdfd) |
|---|---|
| Product | Chainmaker Go (e4c50d26-26a7-5816-be67-96690d789973) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
Notes
Imported from gcve-enriched-dumps CVE data
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2024-58133 |
vulnerable | 2026-06-08 06:56:14.256468 |
Details available
MEDIUM (4)
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.
Published: 2025-04-06T00:00:00.000Z
Updated: 2025-04-07T16:24:00.157Z Reference links |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2024-58132 |
vulnerable | 2026-06-08 06:56:14.256055 |
Details available
MEDIUM (4)
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.
Published: 2025-04-06T00:00:00.000Z
Updated: 2025-04-07T14:11:04.837Z Reference links |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.
Inspect record JSON
Open this panel to browse, search, copy or download the JSON record.