CVE-2018-13585
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe mintToken function of a smart contract implementation for CHERRYCOIN, an Ethereum token, has an integer overflow that allows the owner of the contract to set the balance of an arbitrary user to any value.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe mintToken function in the CHERRYCOIN Ethereum token contract contains an integer overflow vulnerability that enables the contract owner to manipulate the token balance of any user to an arbitrary value. This combines an arithmetic flaw with an authorization weakness, allowing privilege abuse.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE dataall versionsCVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Locate the CHERRYCOIN token contract addressCheck your records or blockchain explorers (Etherscan, Etherscope) for the deployed CHERRYCOIN contract address that you or your organization controls or holds tokens fromAffected if You have deployed or interact with a contract at the CHERRYCOIN token address that contains the vulnerable mintToken function
-
Verify if mintToken function existsQuery the deployed contract bytecode or source code for the function signature 0x40c1d064 (keccak256 of mintToken(uint256)) using web3.js/web3.py or a block explorerAffected if The function signature 0x40c1d064 is present in the contract, indicating the vulnerable mintToken function exists
-
Check source code for integer overflow protectionIf source code is available (verified on block explorer), search for SafeMath library usage or explicit overflow checks in the mintToken function - absence indicates vulnerabilityAffected if The mintToken function lacks SafeMath library or explicit bounds checking before arithmetic operations on the balance variable
-
Verify contract ownership structureCheck if the contract has an owner role that can call mintToken - look for require statements or onlyOwner modifiers in the mintToken functionAffected if The contract owner role can call mintToken and there are no additional safeguards preventing arbitrary balance manipulation
-
Inspect balance manipulation capabilityCall the mintToken function with a test value (if you are the owner) or analyze the function logic to confirm it adds the input value directly to any target balance without overflow protectionAffected if The function allows setting any address balance to an arbitrary value by directly adding the input to existing balance without modulo/overflow checks
Your environment is affected if you have deployed or hold CHERRYCOIN tokens from a contract where the mintToken function exists without SafeMath protection and allows the owner to arbitrarily manipulate user balances.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataFix the integer overflow in mintToken using SafeMath library or explicit bounds checking; if already deployed, plan for contract migration or upgrade mechanism to a patched version.
- Consultation2.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,096.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-13585 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2018-13585 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data