CVE-2018-13214
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 GMile, 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 GMile token smart contract's sell function allows amount * sellPrice to wrap around to zero due to Solidity's lack of overflow protection. This causes the seller to receive zero proceeds while their tokens are transferred, effectively draining their 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 token contractQuery the blockchain for the token at the GMile contract address and verify the token name is 'Globalmiles' and symbol is 'Gmile' using the name() and symbol() functionsAffected if The token name returns 'Globalmiles' and symbol returns 'Gmile' indicating it is the affected contract
-
Locate the sell function source codeObtain the contract source code from Etherscan (if verified) or decompile the bytecode to find the sell function implementationAffected if The sell function is found in the source code and contains the multiplication amount * sellPrice
-
Check for SafeMath usage in multiplicationInspect the sell function code to determine if the multiplication (amount * sellPrice) uses SafeMath library methods (.mul()) or standard Solidity arithmeticAffected if The multiplication uses direct arithmetic operators (*) without SafeMath protection, indicating vulnerability
-
Verify Solidity compiler versionCheck the contract metadata or source code pragma directive to identify the Solidity version used (e.g., pragma solidity ^0.4.25)Affected if The contract was compiled with Solidity version 0.7.x or lower without SafeMath, as versions before 0.8.0 lack built-in overflow checks
-
Confirm zero-return vulnerability pathAnalyze the sell function logic to confirm that an attacker-controlled amount and sellPrice could result in the product wrapping to zero (256-bit overflow)Affected if The code allows user-controlled amount and sellPrice values that could produce a product exceeding 2^256, causing it to wrap to zero
If the contract is the Globalmiles Gmile token, uses direct multiplication for amount * sellPrice, was compiled with Solidity below 0.8.0 without SafeMath library, and lacks overflow protection, the environment is affected by this vulnerability.
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 migrate to Solidity 0.8+ which includes built-in overflow checking to prevent the multiplication from wrapping to zero.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-13214 — 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-13214 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