CVE-2018-13219
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 YourCoin (ICO) (Contract Name: ETH033), 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 sell() function of the ETH033 Ethereum token smart contract where the calculation 'amount * sellPrice' can overflow to zero, causing sellers to lose their assets while receiving no compensation.
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 hold or interact with Yourcoin tokenCheck your Ethereum wallet, exchange accounts, or blockchain explorer for any balances or transactions involving the Yourcoin token contractAffected if You have a non-zero Yourcoin balance or have interacted with the Yourcoin contract
-
Locate the deployed Yourcoin contract source codeIf you know the Yourcoin contract address, search on Etherscan or similar block explorers for the verified source codeAffected if You have deployed or are using a Yourcoin contract whose source code is publicly verifiable
-
Examine the sell() function for vulnerable multiplicationLocate the sell() function in the contract source and inspect the line performing 'amount * sellPrice' or similar multiplicationAffected if The sell() function performs multiplication without using SafeMath library or overflow checks
-
Verify if SafeMath is used for arithmetic operationsSearch the contract code for 'using SafeMath' statement and verify SafeMath is imported and used for the multiplication in sell()Affected if The contract does not import or use SafeMath for the sell() function arithmetic
-
Test the vulnerability with a small amountIf you have access to the contract, call sell() with an amount that would cause overflow (e.g., large amount with high sellPrice) on a test network firstAffected if The sell() transaction succeeds but transfers zero tokens to the seller despite deducting the sold amount
You are affected if you hold or interact with Yourcoin and the deployed contract's sell() function performs multiplication without SafeMath protection, allowing the amount * sellPrice calculation to overflow to zero.
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 that detect overflow conditions, or implement explicit bounds checking before multiplication.
- Consultation4.0 h
- Implementation3.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,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-13219 — 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-13219 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