CVE-2018-12067
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 Substratum (SUB), 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 · moderate confidenceThe Substratum (SUB) ERC20 token smart contract contains an integer overflow vulnerability in its sell function. The multiplication of the user-provided amount parameter and the sellPrice variable can overflow due to inadequate bounds checking. Since sellPrice is manipulable, an attacker could exploit this 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 Substratum SUB token presenceSearch your blockchain wallet, token tracking systems, or smart contract registry for the Substratum (SUB) token contract address. The official SUB token is associated with the Substratum project.Affected if The Substratum SUB token contract is deployed or integrated in your environment.
-
Locate the deployed sell functionQuery the blockchain for the SUB token contract and retrieve its source code. Look for the sell() function definition that accepts an amount parameter.Affected if A sell() function exists that accepts a user-provided amount parameter.
-
Inspect the multiplication arithmeticExamine the sell function code for the line performing amount * sellPrice. Look for whether SafeMath library is used for this multiplication (e.g., mul() method) or if native multiplication operator (*) is used without overflow protection.Affected if The code uses native multiplication operator (*) for amount * sellPrice without SafeMath or bounds checking.
-
Verify sellPrice manipulabilityCheck if there exists a function that allows external modification of the sellPrice variable (e.g., a setter function, or if sellPrice can be set by anyone). Look for functions that update the sellPrice state variable.Affected if sellPrice can be changed by external actors without sufficient access controls.
Your environment is affected if the Substratum SUB token contract is present and its sell function performs amount * sellPrice using native arithmetic without SafeMath while allowing sellPrice to be modified externally.
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 vulnerable arithmetic operations with SafeMath library functions that explicitly check for overflows, or implement proper bounds validation before the multiplication operation.
- Consultation4.0 h
- Implementation6.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 $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-12067 — 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-12067 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