CVE-2018-13587
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 DECToken, 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 DECToken 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 lack of proper overflow checking in arithmetic operations when minting new tokens.
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 DECToken contract deploymentSearch your contract deployment records or blockchain explorers for any deployed instance of the DECToken contract (contract address starting around 0x...). Look for contracts named 'Dectoken' or 'DEC Token' in your Ethereum addresses/wallets.Affected if You have deployed the DECToken smart contract to any blockchain network (mainnet, testnet, or private).
-
Locate contract source codeSearch for the DECToken.sol or Dectoken.sol source file in your project repositories. If not available, obtain the contract bytecode from the blockchain and attempt to decompile it using tools like etherscan decompiler or PanopticLex.Affected if The source code or decompiled bytecode shows a function named 'mintToken' that performs arithmetic operations on token balances.
-
Verify mintToken function existsIn the source code, locate the mintToken function definition. Check if it accepts parameters such as (address to, uint256 amount) and performs balance modifications like balances[to] += amount.Affected if The mintToken function exists and modifies user balances through direct arithmetic operations without using SafeMath.
-
Confirm lack of overflow protectionSearch the entire contract file for 'SafeMath' library usage or 'require' statements that check for overflow/underflow in arithmetic operations. Look specifically around the mintToken function and any balance addition operations.Affected if The contract does not import or use SafeMath library, and no overflow checks exist on balance addition operations in mintToken.
-
Check owner权限Locate the contract owner variable (often named 'owner') and identify which address deploys or controls the contract. Verify if the mintToken function has an onlyOwner or require(msg.sender == owner) modifier.Affected if You are the contract owner or possess the owner private key, meaning you can call the vulnerable mintToken function.
You are affected if you have deployed the DECToken smart contract and it contains a mintToken function that performs balance arithmetic without SafeMath overflow protection, allowing the owner to manipulate any user 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 dataReplace vulnerable arithmetic operations with SafeMath library functions or migrate to a secure, audited token implementation (such as OpenZeppelin) that includes overflow protection. Consider contract migration if upgradeability is not built in.
- 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-13587 — 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-13587 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