CVE-2018-13197
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 Welfare Token Fund (WTF), 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 vulnerability in the WTF token smart contract's sell function where the calculation 'amount * sellPrice' can result in zero due to integer overflow, causing sellers to lose their assets without receiving proper compensation.
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 if Welfare Token Fund contract is deployedSearch blockchain explorers or your transaction records for deployments of the Welfare Token Fund token contract addressAffected if The contract is currently deployed on any blockchain network you use
-
Locate the contract source codeIf you have local copies of deployed contracts, search for files containing 'WelfareTokenFund' or WTF token contracts; or verify if source code is published on Etherscan/Blockscout with the 'sell' functionAffected if Source code is available and lacks SafeMath library usage in the sell function
-
Examine the sell function multiplicationReview the sell function in the contract source code and locate the line performing 'amount * sellPrice' calculationAffected if The multiplication uses Solidity version below 0.8.0 without SafeMath library or overflow checks
-
Check if token trading is activeReview recent blockchain events or your logs for transactions interacting with the sell function (sell tokens, withdraw, etc.)Affected if Any recent sell function calls exist in the environment
-
Verify sellPrice value rangeCheck if sellPrice is a value that when multiplied with typical sell amounts could trigger overflow (typically very small values or edge cases)Affected if sellPrice is set such that amount * sellPrice can equal zero for common sell amounts
You are affected if the Welfare Token Fund contract is deployed in your environment and lacks SafeMath or Solidity 0.8+ overflow protections in the sell function, especially if sell transactions have occurred.
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 library or migrate to Solidity 0.8+ which has built-in overflow checks, and add explicit validation for the multiplication result before executing the transfer.
- Consultation2.0 h
- Implementation4.0 h
- Testing6.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,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-13197 — 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-13197 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