CVE-2018-13555
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 JaxBox, 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 JaxBox Ethereum token smart contract contains an integer overflow vulnerability that permits the contract owner to manipulate user balances to arbitrary values. This is a classic ERC-20 token vulnerability where arithmetic operations lack proper overflow/underflow protection.
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 the deployed JaxBox token contractQuery your blockchain explorer or deployment records for the JaxBox token contract address. In your project repository, search for the deployed contract address in configuration files, deployment scripts, or environment variables.Affected if You have a deployed JaxBox token contract and can access its address
-
Retrieve the contract source code or bytecodeSearch for the JaxBox token source code in your project repositories under contracts/, or use a blockchain explorer (Etherscan) to decompile the bytecode if source code is not available. Look for files named JaxBox.sol, JaxToken.sol, or similar.Affected if The contract source code or decompiled bytecode can be obtained for analysis
-
Identify the mintToken functionIn the source code or decompiled output, locate the mintToken function definition. Look for function signatures containing 'mint' and check if it accepts parameters for target address and token amount.Affected if A mintToken function exists in the contract and can be called by the owner
-
Verify overflow protection in mintTokenExamine the mintToken function implementation. Check if it uses SafeMath library for arithmetic (look for 'using SafeMath for' or '.add()', '.mul()' calls) or contains explicit require statements validating that totalSupply + amount does not overflow.Affected if The mintToken function lacks SafeMath usage or explicit overflow checks before arithmetic operations
-
Check for arbitrary balance manipulation riskReview the function logic to determine if the owner can set any user's balance to any value without restrictions. Look for direct assignment to balances[user] = value patterns without validation.Affected if The function allows the contract owner to set user balances to arbitrary values without proper validation
Your environment is affected if you have deployed the JaxBox token contract and its mintToken function lacks SafeMath or explicit overflow checks, allowing the owner to manipulate balances 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 dataDeploy a fixed contract version using SafeMath library for arithmetic operations or implement explicit overflow checks in the mintToken function, then migrate all token balances to the new contract.
- Consultation8.0 h
- Implementation12.0 h
- Testing10.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 $10,144.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-13555 — 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-13555 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