CVE-2018-13218
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 ICO Dollar (ICOD), 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 confidenceThe ICOD Ethereum token smart contract contains an integer overflow vulnerability in its sell function where the multiplication 'amount * sellPrice' can result in zero due to integer overflow, causing sellers to lose their assets unexpectedly.
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 if you have deployed the Ico Dollar token contractSearch your deployed smart contracts for an Ethereum token named 'Ico Dollar' or 'ICOD' - check your contract deployment records or block explorers for contracts with the symbol 'ICOD'Affected if You have deployed the Ico Dollar token contract from the Ico Dollar Project
-
Locate the sell function in the contractObtain the contract source code or decompiled bytecode and search for a function named 'sell' that handles token sales - this is typically a public function that accepts an 'amount' parameterAffected if The deployed contract contains a sell function handling token redemptions
-
Check for unsafe arithmetic in the sell functionReview the sell function code for the multiplication pattern 'amount * sellPrice' - examine whether SafeMath library functions (mul) are used or if raw arithmetic operators (*) are used without overflow protectionAffected if The code uses raw multiplication 'amount * sellPrice' without SafeMath library or Solidity 0.8+ overflow checks
-
Verify the sell function is accessibleConfirm the sell function is not marked as internal or private - check the function visibility modifier (public or external) and whether there are any access controls preventing its executionAffected if The sell function is publicly callable (public or external visibility) and can be invoked by anyone
-
Test for overflow behaviorIf you have a test environment, call the sell function with an amount value that would cause the multiplication to overflow when multiplied by sellPrice - for example, if sellPrice is known, use an amount that makes the product exceed 2^256Affected if Calling sell with a large amount value results in zero tokens received due to integer overflow, indicating the vulnerability is present and exploitable
If you have deployed the Ico Dollar token contract and its sell function uses raw arithmetic multiplication without SafeMath or Solidity 0.8+, your environment is vulnerable to CVE-2018-13218.
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 dataReplace unsafe arithmetic operations with SafeMath library functions or upgrade to Solidity 0.8+ which includes built-in overflow checking, and perform thorough testing to verify the fix.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-13218 — 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-13218 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