CVE-2018-13512
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 mintToken function of a smart contract implementation for SmartHomeCoin, an Ethereum token, has an integer overflow that allows the owner of the contract to set the balance of an arbitrary user to any value.
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 mintToken function in the SmartHomeCoin Ethereum smart contract contains an integer overflow vulnerability that allows the contract owner to manipulate arbitrary user balances to any value. This occurs due to missing overflow checks when updating token balances, combined with privileged owner access.
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.1/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 SmartHomeCoin contract deploymentSearch your deployment records, blockchain explorers, or wallet configurations for any contract address labeled SmartHomeCoin (SMC) or related to the Smarthomecoin project.Affected if You have deployed or actively use a contract named SmartHomeCoin or Smarthomecoin.
-
Locate the mintToken function in contract sourceObtain the contract source code from Etherscan (if verified), your repository, or by decompiling the deployed contract bytecode. Search for a function named 'mintToken' or similar minting function.Affected if A function named mintToken exists in the contract without proper access controls on balance modifications.
-
Check for missing overflow protection in balance updatesExamine the mintToken function code. Look for token balance assignment statements (e.g., balances[account] = ...) that do not use SafeMath library methods (add, sub, mul) or do not include explicit overflow/underflow checks.Affected if The function updates balances without SafeMath or explicit overflow validation before arithmetic operations.
-
Verify owner privileges on arbitrary balance manipulationReview the mintToken function for require statements, onlyOwner modifiers, or other access controls that restrict who can call it. Check if the function accepts an arbitrary address and value parameter.Affected if The function can be called by the contract owner to set any user's balance to any value without restrictions.
You are affected if you have deployed or interact with a SmartHomeCoin contract containing a mintToken function that allows the owner to modify user balances without overflow protection.
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 dataRedeploy the contract with proper integer overflow protection (e.g., SafeMath library) and remove or properly constrain owner minting capabilities. If tokens are already in circulation, coordinate a token migration plan.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.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,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-13512 — 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-13512 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