CVE-2018-13602
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 mint function of a smart contract implementation for MiningToken, 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 MiningToken smart contract contains an integer overflow vulnerability in its mint function that allows the contract owner to set arbitrary user balances, effectively enabling unauthorized balance manipulation. This is a critical access control and integrity failure in the token's minting logic.
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.
-
Locate MiningToken contract in your environmentSearch the blockchain for deployments of the Marcelominingtoken contract, or check your contract inventory for any token contracts named Marcelominingtoken or MiningTokenAffected if The Marcelominingtoken contract is deployed in your blockchain environment
-
Identify the mint function implementationRetrieve the contract source code or decompile the deployed bytecode to locate the mint function definitionAffected if A mint function exists in the contract that accepts parameters to set user balances
-
Check for SafeMath usage in mint functionReview the mint function code to see if arithmetic operations (particularly addition for balance updates) use SafeMath library or equivalent overflow-safe functionsAffected if The mint function performs arithmetic without SafeMath or overflow protection
-
Verify access control on mint functionExamine the mint function to determine who can call it and whether there are restrictions on setting arbitrary balance valuesAffected if The mint function can be called by the owner without proper validation of the amounts being minted
-
Test for integer overflow in balance manipulationIf you have access, attempt to call the mint function with extremely large values (near max uint256) to see if the balance wraps aroundAffected if Calling mint with large values causes balance to wrap around due to integer overflow
Your environment is affected if the Marcelominingtoken contract is deployed and the mint function lacks SafeMath overflow protection or proper access controls on balance manipulation.
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 unsafe arithmetic operations with SafeMath library functions to prevent integer overflow, and implement proper access control checks on the mint function to restrict balance modifications to legitimate operations.
- Consultation4.0 h
- Implementation4.0 h
- Testing3.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,016.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-13602 — 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-13602 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