MyCryptoChamp
Approved changes feed: RSS · Atom
cpe:2.3:a:mycryptochamp:mycryptochamp:-:*:*:*:*:*:*:*part: a version: - update: *
| Vendor | Mycryptochamp (4fd2f5c7-73d8-5709-a0d3-0be234cb2b66) |
|---|---|
| Product | Mycryptochamp (f7164251-9014-5fac-ba5f-9a20d6f60c34) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
Notes
Imported from NVD CPE 2.0 feed
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-2018-12885 |
vulnerable | 2026-06-08 05:10:42.085929 |
Details available
The randMod() function of the smart contract implementation for MyCryptoChamp, an Ethereum game, generates a random value with publicly readable variables such as the current block information and a private variable, (which can be read with a getStorageAt call). Therefore, attackers can get powerful champs/items and get rewards.
Published: 2018-08-07T15:00:00.000Z
Updated: 2024-08-05T08:45:02.506Z |
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.