CVE-2018-13517
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 C3 Token (C3), 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 C3 Token smart contract contains an integer overflow vulnerability that allows the contract owner to set any user's token balance to an arbitrary value, potentially enabling unauthorized token creation or balance manipulation.
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 C3 Token contract addressCheck your records or blockchain explorer for any contract address associated with C3 Token that you have interacted with, hold tokens from, or manageAffected if You hold, manage, or have interacted with a contract labeled as C3 Token on the blockchain
-
Verify mintToken function existsUse a blockchain explorer or decompile the contract bytecode to search for a function named 'mintToken' in the C3 Token contractAffected if The deployed contract contains a function called mintToken that accepts user address and amount parameters
-
Check for SafeMath or overflow protectionReview the contract source code or bytecode for use of SafeMath library or inline overflow checks within the mintToken functionAffected if The mintToken function lacks SafeMath library usage or explicit overflow validation on arithmetic operations
-
Verify contract owner privilegesExamine the contract for an owner variable and check if mintToken can only be called by the contract owner (via onlyOwner modifier or similar access control)Affected if The mintToken function is callable by the contract owner without additional safeguards or timelocks
-
Check balance assignment capabilityReview the mintToken function logic to determine if it can directly set any address balance to an arbitrary value without constraintsAffected if The function allows setting balances to arbitrary values without requiring the address to have previously received tokens or without collateral backing
-
Confirm all versions affectedCompare the deployed contract version against the C3 Token Project version historyAffected if The deployed contract is any version of C3 Token (all versions are affected per CVE)
You are affected if you interact with or hold C3 Token and the deployed contract contains a vulnerable mintToken function without overflow protection that permits the owner to arbitrarily set 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 contract owner should update the mintToken function with proper overflow protection (e.g., SafeMath library) and review/adjust owner privileges to follow least-privilege principles. The fixed contract must be redeployed and token holders notified of the new contract address.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-13517 — 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-13517 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