CVE-2018-13208
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 MoneyTree (TREE), 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 sell function in the MoneyTree (TREE) Ethereum token smart contract contains an integer overflow vulnerability where the calculation 'amount * sellPrice' can overflow to zero due to insufficient bounds checking. This causes the seller to receive zero or drastically reduced assets despite valid input.
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 deployed MoneyTree token contractSearch your blockchain explorer or contract deployment records for the TREE token contract address. Verify the contract is at the expected MoneyTree deployment address.Affected if The TREE token contract is deployed in your environment without a corresponding patched version.
-
Obtain the sell function source codeIf the contract is verified on a block explorer, retrieve the source code and locate the sell function. Look for the line performing 'amount * sellPrice' or equivalent multiplication.Affected if The source code shows unprotected arithmetic multiplication without SafeMath.
-
Verify SafeMath usage on the multiplicationInspect the sell function specifically for SafeMath.mul() or equivalent overflow-safe library usage around the amount * sellPrice calculation. Check for 'require' or 'assert' statements that validate the product won't overflow.Affected if The multiplication is performed with bare arithmetic operators (*, +, -) instead of SafeMath library functions and lacks explicit overflow guards.
-
Check the compiler version and librariesReview the Solidity compiler version used and confirm whether SafeMath is imported and used throughout the contract, not just in the sell function.Affected if The contract uses an older Solidity version (pre-0.8.0) without SafeMath for the critical multiplication.
-
Test the overflow condition on a test networkDeploy the contract on a test network and attempt to sell an amount where amount * sellPrice exceeds the maximum uint256 value, observing if the seller receives zero tokens.Affected if The sell function returns zero or a drastically reduced payout when given large sellPrice values that cause overflow to zero.
Your environment is affected if you are using a deployed MoneyTree token contract whose sell function performs the amount * sellPrice multiplication without SafeMath or equivalent overflow protection.
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 dataImplement SafeMath or equivalent overflow-safe arithmetic library for all arithmetic operations in the sell function, specifically replacing the unchecked multiplication with SafeMath.mul() to prevent overflow to zero.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,192.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-13208 — 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-13208 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