CVE-2018-13485
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 BitcoinAgileToken, 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 BitcoinAgileToken Ethereum smart contract contains an integer overflow vulnerability that allows the contract owner to manipulate any user's token balance to arbitrary values due to unchecked arithmetic operations on the balance variable.
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 if the contract is BitcoinAgileTokenLocate the deployed contract source code on Etherscan or similar block explorer, or obtain the source code from the Bitcoinagile project repository. Verify the contract name is BitcoinAgileToken and it contains a mintToken function.Affected if The deployed contract is BitcoinAgileToken from the Bitcoinagile project and contains a mintToken function
-
Examine the mintToken function implementationReview the source code of the mintToken function. Look for the arithmetic operation that updates the balance variable (typically: balance[to] += mintedAmount or similar).Affected if The mintToken function performs direct arithmetic on balance variables without using a SafeMath library
-
Check for SafeMath usage in balance updatesSearch the contract code for uses of SafeMath operations (add, sub, mul, div) when updating token balances in mintToken. Verify if SafeMath is imported and used for the balance modification.Affected if The balance update in mintToken uses direct arithmetic operators (+, -, *, /) instead of SafeMath library functions
-
Verify owner-only access to mintTokenConfirm that the mintToken function is callable only by the contract owner (typically via a require statement checking msg.sender == owner or using a onlyOwner modifier).Affected if The mintToken function can be invoked by the contract owner and performs unchecked arithmetic on balances
The environment is affected if the BitcoinAgileToken contract uses direct arithmetic operations (without SafeMath) in the mintToken function to update token balances, allowing the owner to overflow the balance variable and manipulate any user's balance to arbitrary values.
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 direct arithmetic operations in mintToken with SafeMath library functions or implement explicit bounds checking to prevent integer overflow when updating token balances.
- Consultation3.0 h
- Implementation6.0 h
- Testing8.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,472.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-13485 — 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-13485 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