CVE-2018-12068
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 Target Coin (TGT), a tradable Ethereum ERC20 token, allows a potential trap that could be used to cause financial damage to the seller, because of overflow of the multiplication of its argument amount and a manipulable variable sellPrice, aka the "tradeTrap" issue.
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 Target Coin (TGT) ERC20 smart contract contains an integer overflow vulnerability in its sell function. The multiplication of the user-provided amount and the sellPrice variable can overflow due to lack of proper bounds checking, and since sellPrice is manipulable, an attacker can trigger the overflow to cause financial loss to sellers.
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 TGT token presenceCheck if your system or Ethereum wallet holds the Target Coin (TGT) token, or if your application integrates with the TGT ERC20 contract at address 0x2fAb8c2Ed092dd15E2D7252968d5188A9D3C1B8 (verify against official sources)Affected if You hold TGT tokens or interact with the TGT contract
-
Locate the sell function sourceObtain the TGT contract source code from Etherscan via the 'Contract' tab or your own codebase if you deployed a modified versionAffected if You have access to the contract code showing the vulnerable sell function
-
Check for SafeMath usage in sell functionSearch the sell function for 'SafeMath' or '.mul()' - the vulnerable pattern is 'amount * sellPrice' without overflow protectionAffected if The multiplication uses plain arithmetic operators (*) without SafeMath or Solidity 0.8+ overflow checks
-
Verify sellPrice is mutableLook for a function that allows setting sellPrice (commonly named 'setSellPrice' or similar), and confirm it lacks access controls or requires no special privilegesAffected if Any user can modify the sellPrice value through a public setter function
-
Confirm no bounds checking existsInspect the sell function for require statements or if statements that validate amount * sellPrice stays within uint256 range before the multiplication executesAffected if There are no validation checks preventing the multiplication from overflowing
You are affected if your system interacts with a TGT contract where the sell function performs amount * sellPrice without SafeMath, and sellPrice can be modified by an attacker to cause 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 dataImplement safe math libraries (e.g., OpenZeppelin SafeMath) or migrate to Solidity 0.8+ which includes built-in overflow checks to prevent integer overflow in arithmetic operations.
- Consultation4.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-12068 — 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-12068 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