CVE-2018-13617
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 CAPTOZ, 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 confidenceInteger overflow vulnerability in the mintToken function of the CAPTOZ Ethereum token smart contract allows the contract owner to arbitrarily set any user's token balance to any value due to lack of proper integer overflow/underflow checks when minting 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 CAPTOZ token presenceSearch your wallets, exchanges, or blockchain explorers for CAPTOZ token holdings or interactions. Check if the token contract address matches the Captoz Project Captoz contract.Affected if You hold or interact with CAPTOZ tokens on any platform or in any wallet
-
Locate mintToken function in source codeObtain the contract source code from Etherscan via 'Contract' > 'Code' tab, or from your own files. Search for a function named 'mintToken' and examine its implementation.Affected if A function named mintToken exists that accepts target and amount parameters without proper overflow guards
-
Check for SafeMath usage in mintTokenWithin the mintToken function code, verify whether arithmetic operations use SafeMath library functions (.add, .sub, .mul) or native Solidity operators (+, -, *).Affected if The mintToken function uses native arithmetic operators instead of SafeMath functions
-
Verify Solidity compiler versionLocate the 'pragma solidity' declaration at the top of the contract source code. Note the compiler version specified.Affected if The contract is compiled with Solidity versions below 0.8.0 and does not use SafeMath
You are affected if you hold CAPTOZ tokens from a contract where the mintToken function exists and lacks SafeMath protections or Solidity 0.8+ built-in overflow checks, allowing the owner to arbitrarily manipulate balances.
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 arithmetic operations with SafeMath library functions or upgrade to Solidity 0.8+ which includes built-in overflow checks; also implement additional access controls to prevent owner abuse of balance manipulation.
- Consultation4.0 h
- Implementation8.0 h
- Testing8.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,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-13617 — 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-13617 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