CVE-2018-13204
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 sell function of a smart contract implementation for ETHERCASH (ETC), an Ethereum token, has an integer overflow in which "amount * sellPrice" can be zero, consequently reducing a seller's assets.
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 confidenceInteger overflow vulnerability in the ETHERCASH smart contract's sell function where multiplying amount by sellPrice can overflow to zero, causing sellers to lose their tokens without receiving payment.
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.
-
Identify deployed Ethercash contractQuery your blockchain node or block explorer for any deployed contracts matching the Ethercash token standard. Search for contracts with name 'Ethercash' or associated contract addresses in your environment's deployment artifacts.Affected if An Ethercash contract is deployed and the sell function handles token-to-ether conversions.
-
Locate the sell function source codeRetrieve the Solidity source code for the deployed contract. Check for a function named 'sell' or 'sellToken' that accepts an 'amount' parameter and calculates payout using a 'sellPrice' variable.Affected if The contract contains a sell function that multiplies amount by sellPrice without overflow protection.
-
Verify overflow protection is absentInspect the sell function body. Search for the multiplication operation 'amount * sellPrice' or 'amount * price'. Check whether SafeMath library is imported and used for this multiplication, or whether the contract uses Solidity version 0.8 or higher which has built-in overflow checks.Affected if The multiplication uses direct arithmetic operators (*) without SafeMath and the Solidity version is below 0.8.
-
Confirm sellPrice is user-controlled or can be set to high valuesExamine whether sellPrice is a public state variable that can be modified by anyone, set by an owner, or derived from market logic that could allow unusually high values.Affected if sellPrice can be set to a value such that amount * sellPrice exceeds the maximum uint256 value, causing overflow to zero.
Your environment is affected if you have deployed the Ethercash contract with a sell function that performs amount * sellPrice without SafeMath or Solidity 0.8+, and sellPrice can be set to values that trigger integer overflow.
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 dataUpdate Solidity version to 0.8+ for built-in overflow checks or use SafeMath library for arithmetic operations; implement proper validation to ensure sellPrice and amount are within safe bounds before multiplication.
- Consultation4.0 h
- Implementation4.0 h
- Testing8.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-13204 — 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-13204 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