CVE-2018-13132
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 · uneditedSpadeico is a smart contract running on Ethereum. The mint function has an integer overflow that allows minted tokens to be arbitrarily retrieved by the contract owner.
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 Spadeico Ethereum smart contract contains an integer overflow vulnerability in its mint function that allows the contract owner to retrieve arbitrarily large amounts of minted tokens. This is a classic Solidity arithmetic vulnerability where lack of overflow checking enables the owner to manipulate token counts beyond intended limits.
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 Spadeico contract presenceSearch your contract deployments, token registries, or blockchain explorers for contracts named 'Spadeico' or 'SPADE' and note the contract addressAffected if A Spadeico contract is deployed in your environment or held in your wallet/portfolio
-
Locate the mint function source codeObtain the contract source code from Etherscan 'Contract' tab (if verified) or your codebase, then locate the 'mint' function definitionAffected if The mint function exists and uses standard arithmetic operators (+, -, *, /) without SafeMath library wrappers
-
Check for SafeMath usage in arithmetic operationsWithin the mint function, examine any line that increments token supply or balances - verify it uses SafeMath methods (add, sub, mul, div) rather than native Solidity operatorsAffected if Integer arithmetic operations lack SafeMath overflow checks (e.g., 'totalSupply += amount' instead of 'totalSupply.add(amount)');
-
Inspect owner-privileged minting functionsReview contract for functions with 'onlyOwner' or 'owner' modifiers that allow minting or transferring tokens beyond normal user constraintsAffected if An onlyOwner function exists that permits the owner to mint or retrieve arbitrary token amounts without proportional constraints or external validation
-
Verify contract on blockchain for anomaliesQuery the contract's totalSupply, owner balance, and transfer events using a blockchain explorer or web3 call - compare against expected token economicsAffected if totalSupply or owner balance shows values exceeding normal mint schedules, or transfers lack corresponding user deposits
Your environment is affected if you have the Spadeico contract deployed and its mint function lacks SafeMath overflow checks, allowing the owner to mint unlimited tokens.
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 standard arithmetic operations in the mint function with SafeMath library functions that perform overflow checks, and review/remove any owner-privileged functions that allow arbitrary token retrieval to enforce proper token economics.
- Consultation2.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,096.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-13132 — 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-13132 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