CVE-2018-13220
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 MAVCash, 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 MAVCash Ethereum token smart contract contains an integer overflow vulnerability in its sell function where the calculation 'amount * sellPrice' can result in zero due to arithmetic overflow. When the product exceeds the maximum value for the integer type, it wraps to zero, causing sellers to receive zero compensation despite transferring their tokens.
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 MAVCash token contract addressSearch blockchain explorers (Etherscan, Ethernal) for the MAVCash token contract address using the token name or symbolAffected if You hold the MAVCash token and have identified the specific contract address used for the token
-
Retrieve the contract source codeCheck if the source code is verified on Etherscan or other block explorers under the contract address. If not verified, use a decompiler to obtain readable bytecodeAffected if Source code or decompiled bytecode is available for inspection
-
Locate the sell function in the source codeSearch the source code for a function named 'sell' or 'sellTokens' that handles the token selling logicAffected if A sell function exists in the contract
-
Inspect the amount calculation for overflow vulnerabilityFind the line where 'amount * sellPrice' or equivalent multiplication is performed. Check whether this multiplication uses SafeMath library functions (such as mul) or native Solidity arithmeticAffected if The multiplication is performed using native Solidity operators (*) without SafeMath protection, allowing the result to wrap to zero when the product exceeds the maximum uint256 value
-
Verify the vulnerability is exploitableConfirm that there are no other checks in the sell function that would prevent the overflow from occurring or detect a zero result before transferring tokensAffected if No additional validation exists to catch a zero payout before the token transfer occurs
You are affected if you hold MAVCash tokens from a contract where the sell function performs multiplication without SafeMath and lacks validation to prevent zero payouts from 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 dataThe integer overflow must be fixed using SafeMath library functions for arithmetic operations, and the contract should be redeployed with a token migration mechanism to transfer holders from the vulnerable contract to the new fixed version.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.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 $12,352.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-13220 — 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-13220 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