CVE-2018-13583
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 Shmoo, 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 Shmoo Ethereum token smart contract contains an integer overflow vulnerability that allows the contract owner to arbitrarily set any user's token balance to any value, bypassing proper validation and breaking token ledger integrity.
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 Shmoo token contract in useCheck your wallet, transaction history, or blockchain explorer for any Shmoo token (ticker: SHOO) holdings or interactions. Search for the contract address on Etherscan or similar block explorers.Affected if You hold Shmoo tokens or have transacted with the Shmoo token contract.
-
Verify contract ownership statusQuery the contract to check if your address is the owner. On Etherscan, use the 'Read Contract' function to call the 'owner' method, or use web3/ethers.js to call owner().Affected if Your address is the contract owner and you have the ability to call administrative functions.
-
Inspect mintToken function source codeLocate the Shmoo token contract source code on Etherscan (Contract tab) or the official Shmoo repository. Search for the 'mintToken' function definition.Affected if The mintToken function exists and performs arithmetic operations (such as balance additions) without using SafeMath or Solidity 0.8+ overflow checks.
-
Check Solidity version and SafeMath usageExamine the contract source code at the top for the 'pragma solidity' declaration. Search the code for 'using SafeMath' imports or library declarations.Affected if The contract uses Solidity below version 0.8.0 AND does not import or use the SafeMath library for arithmetic operations.
You are affected if the Shmoo token contract is deployed in your environment and the mintToken function performs balance arithmetic without overflow protection (no SafeMath, no Solidity 0.8+), allowing the owner to manipulate any balance.
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 dataUpgrade the contract to use Solidity 0.8+ with built-in overflow checks or implement SafeMath library for arithmetic operations, and consider deploying a new fixed contract with potential token migration mechanisms.
- Consultation4.0 h
- Implementation8.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 $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-13583 — 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-13583 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