CVE-2018-13201
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 TiTok - Ticket Token (Contract Name: MyAdvancedToken7), 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 in the sell function of the TiTok (MyAdvancedToken7) Ethereum smart contract allows the calculation amount * sellPrice to overflow to zero. When this occurs, sellers receive 0 ETH despite their tokens being deducted from their balance, resulting in complete loss of assets.
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 the contractObtain the contract source code or bytecode at the TiTok contract address and check if it matches the MyAdvancedToken7 contract named 'Titok' or 'Ticket Token'Affected if The contract is the TiTok/MyAdvancedToken7 token with no SafeMath library and the sell function exists
-
Check the sell function for vulnerable multiplicationInspect the sell function in the source code and locate the line performing 'amount * sellPrice' or equivalent token-to-ETH calculationAffected if The multiplication is performed without SafeMath library (e.g., using '*' operator directly instead of mul())
-
Verify Solidity versionCheck the compiler version pragma at the top of the contract source code (e.g., 'pragma solidity ^0.4.XX')Affected if The contract uses Solidity version below 0.8.0 which lacks built-in overflow protection
-
Check for return value validationLook for any require or if statement after the sell amount calculation that validates the resulting ETH amount is greater than zero before calling transferAffected if No validation exists to ensure the calculated ETH amount is non-zero before executing the transfer
-
Confirm token deduction occurs regardless of overflowVerify that the sell function deducts tokens from the seller balance (e.g., balanceOf[msg.sender] -= amount) before or independent of the ETH transfer resultAffected if Tokens are always deducted even when the overflow causes the transfer amount to be zero
If the contract is TiTok/MyAdvancedToken7, uses Solidity below 0.8, performs the amount*sellPrice multiplication without SafeMath, and lacks validation that the calculated ETH amount is non-zero before transfer, the environment is affected by CVE-2018-13201.
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 the vulnerable multiplication with SafeMath library functions or upgrade to Solidity 0.8+ for built-in overflow protection, and add validation to ensure the calculated return value is greater than zero before executing the transfer.
- 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-13201 — 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-13201 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