CVE-2018-13483
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 mkethToken, 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 mkethToken Ethereum smart contract contains an integer overflow vulnerability that allows the contract owner to arbitrarily set any user's token balance to any value. This is a critical integrity issue as it enables the owner to manipulate token supplies beyond normal bounds through improper arithmetic in the 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.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 mkethToken contract deploymentSearch your contract deployments for the mkethToken or Mkethtoken contract. Check your deployed contracts for the token name string in the contract source or the contract creation transaction data.Affected if You have deployed the mkethToken smart contract from the Mkethtoken project.
-
Verify mintToken function existsExamine the deployed contract ABI or source code. Look for a function named 'mintToken' that accepts an address and a uint256 amount parameter.Affected if The deployed contract contains a function named 'mintToken' that allows setting token balances.
-
Check for SafeMath library usageReview the mintToken function source code. Search for 'using SafeMath' at the top of the file or SafeMath method calls (add, sub, mul) within the function. Also check for manual overflow checks before arithmetic operations.Affected if The mintToken function performs arithmetic operations (such as balance[target] = balance[target] + mintedAmount) without using SafeMath library or explicit overflow checks.
-
Verify owner-only access without additional restrictionsExamine the mintToken function to confirm it is callable only by the contract owner (requires msg.sender == owner or similar), and check if there are any caps, limits, or additional validation on the amount parameter that would prevent arbitrary large values.Affected if The function can be called by the owner with any uint256 amount value without additional constraints.
If you have deployed the mkethToken contract and its mintToken function lacks SafeMath or overflow checks while allowing the owner to set arbitrary balances, your environment is affected by CVE-2018-13483.
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 dataImplement SafeMath library or manual overflow checks in the mintToken function to prevent integer overflows, and redeploy the corrected contract. Additionally, consider removing or restricting the owner privilege to set arbitrary balances if not intended functionality.
- Consultation4.0 h
- Implementation2.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 $3,440.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-13483 — 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-13483 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