CVE-2018-13487
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 PlatoToken, 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 PlatoToken Ethereum smart contract contains an integer overflow vulnerability that allows the contract owner to set any user's token balance to an arbitrary value, effectively enabling unauthorized manipulation of token supplies.
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 deployed PlatoToken contractQuery your blockchain explorer or node for contracts at addresses associated with the Plato Project token. Identify if the contract is named PlatoToken or similar.Affected if A PlatoToken contract is deployed and accessible in your environment
-
Retrieve contract source codeVerify if the source code is available on Etherscan (via Sourcify) or your local verification system. If not verified, decompile the bytecode using a tool like Panoramix or Hevm.Affected if Source code cannot be retrieved and the contract bytecode shows no SafeMath library patterns
-
Inspect mintToken function for unsafe arithmeticLocate the mintToken function in the source code. Check if arithmetic operations on balances use direct addition/subtraction operators (+, -, +=, -=) instead of SafeMath methods (add, sub).Affected if The mintToken function uses direct arithmetic operators without SafeMath overflow checks
-
Check for owner-only balance manipulationExamine if the mintToken function permits the contract owner (or any caller with minter role) to directly assign an arbitrary value to any user's balance, bypassing normal minting logic.Affected if The function allows setting balance to any value without proper validation or onlyOwner modifiers are missing
-
Verify SafeMath library usageSearch the contract for 'using SafeMath' statements and confirm all balance-modifying operations use SafeMath methods (add, sub, mul, div).Affected if No SafeMath library is imported or used for token balance operations
Your environment is affected if you have deployed the PlatoToken contract and its mintToken function uses direct arithmetic without SafeMath overflow protection, allowing owner-level 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 in the mintToken function with a SafeMath library or equivalent overflow-checked operations to prevent integer overflows during token minting.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-13487 — 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-13487 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