CVE-2018-13600
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 AMToken, 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 · moderate confidenceThe mintToken function in the AMToken Ethereum smart contract contains an integer overflow vulnerability. This allows the contract owner to arbitrarily set any user's token balance to any value by exploiting the overflow condition when calculating token supply or balances.
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.
-
Locate your deployed Amtoken contractIdentify the contract address where Amtoken is deployed. Check your deployment records, blockchain explorers, or project documentation for the contract address.Affected if You have deployed the Amtoken smart contract at any address.
-
Retrieve the contract source codeIf the contract is verified on Etherscan or similar block explorers, view the source code. If you maintain your project files, locate the AmToken.sol or equivalent source file.Affected if The source code contains a function named mintToken.
-
Examine the mintToken function for overflow protectionSearch the source code for the mintToken function definition. Inspect whether it uses SafeMath library methods (such as add, mul, sub, div) for arithmetic operations on token balances and totalSupply, or whether it uses Solidity compiler version 0.8 or higher which includes built-in checked arithmetic.Affected if The mintToken function performs arithmetic operations (addition, multiplication) on balances or totalSupply without SafeMath or Solidity 0.8+ checked arithmetic.
-
Verify the contract owner privilegesReview the mintToken function to confirm it grants the contract owner the ability to call it and modify any user's token balance directly.Affected if The mintToken function accepts a target address and an amount parameter and allows the owner to increase balances without external constraints.
Your environment is affected if you have deployed the Amtoken contract and its mintToken function performs arithmetic on token balances without SafeMath library or Solidity 0.8+ built-in overflow protection, allowing the owner to set arbitrary 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 dataThe vulnerable mintToken function must be rewritten to include proper integer overflow checks using SafeMath library or Solidity 0.8+ built-in checked arithmetic. If the contract is already deployed, a migration to a patched contract version or contract upgrade mechanism should be executed.
- Consultation4.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,544.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-13600 — 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-13600 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