CVE-2018-13494
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 SusanTokenERC20, 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 SusanTokenERC20 Ethereum token contract contains an integer overflow vulnerability that allows the contract owner to manipulate any user's token balance to an arbitrary value. This represents both an integer overflow flaw and a critical authorization bypass where owner privileges are misused to set arbitrary 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 Susantoken contract deploymentSearch your contract deployment records, blockchain explorers, or configuration files for any deployed instances of 'SusanToken' or 'Susantoken' ERC20 token contracts. Check contract addresses against known deployments of this token.Affected if A Susantoken ERC20 contract is deployed in your environment
-
Verify mintToken function existsIf you have access to the contract source code or can interact with the contract via a blockchain explorer/tool, check if a function named 'mintToken', 'mint', or similar owner-only token creation function exists in the contract.Affected if The contract contains a function that allows the owner to directly modify token balances
-
Check for SafeMath usageExamine the contract source code for 'using SafeMath' statements or library imports. Also check arithmetic operations (+, -, *, /) to see if they wrap around without overflow protection.Affected if The contract does not use SafeMath library for arithmetic operations and relies on raw integer math
-
Inspect owner privilege escalationReview the contract code for functions that allow the owner to set arbitrary balances for any address without requiring cryptographic proof or multi-sig approval. Look for functions with 'onlyOwner' modifiers that write directly to balance mappings.Affected if The contract grants the owner unrestricted ability to set any address balance to any value
You are affected if you have deployed any version of the Susantoken ERC20 token contract and it contains a mintToken function that permits the owner to arbitrarily manipulate user balances without SafeMath overflow protection.
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 or upgrade the contract with a secure implementation using SafeMath library for arithmetic operations and remove or properly audit owner-only balance manipulation functions. If already deployed, migrate users to a fixed contract implementation.
- Consultation4.0 h
- Implementation6.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-13494 — 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-13494 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