CVE-2018-13212
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 EthereumLegit, 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 EthereumLegit 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 multiplication overflows, the product wraps to zero, causing sellers to receive zero or minimal payment while losing 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 deployed EthereumLegit contract addressQuery your deployment records or blockchain explorers for contracts named 'Ethereumlegit' or 'EthereumLegit'Affected if You have deployed the EthereumLegit contract at any address on any network
-
Retrieve the contract source codeUse Etherscan or a similar block explorer to view the verified source code for the sell function, or decompile the bytecode if source is not verifiedAffected if The source code shows a sell function containing the multiplication 'amount * sellPrice' without overflow protection
-
Check for overflow protection in sell functionExamine whether the contract uses the SafeMath library for the multiplication, or is compiled with Solidity version 0.8.0 or higher which includes built-in overflow checksAffected if The contract uses Solidity versions below 0.8.0 AND does not use SafeMath for the amount * sellPrice calculation, making the overflow possible
-
Verify the vulnerability is exploitableTest the sell function with an amount and sellPrice combination where their product exceeds 2^256, or review transaction logs for instances where sellers received zero tokensAffected if Calling sell with values that cause multiplication overflow results in zero payment to the seller
Your environment is affected if you have deployed the EthereumLegit contract and the sell function lacks SafeMath or Solidity 0.8+ overflow protections.
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 dataDeploy a new fixed contract version using Solidity 0.8+ with built-in overflow checks or SafeMath library for multiplication, then migrate all token balances and notify affected users of the contract migration.
- 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-13212 — 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-13212 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