CVE-2018-13599
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 ResidualValue, 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 · moderate confidenceThe ResidualValue Ethereum token smart contract contains an integer overflow vulnerability in its mintToken function. This flaw allows the contract owner to manipulate the balance of any user to an arbitrary value by exploiting the overflow condition, effectively bypassing proper authorization and token supply controls.
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 Residualvalue contract addressQuery the blockchain or check the project documentation for the deployed contract address. If you hold tokens, check your wallet for the contract address used.Affected if You have interacted with or hold tokens from a contract at the documented Residualvalue address.
-
Retrieve contract source code or bytecodeUse a blockchain explorer (Etherscan, Blockscout) or web3 library to fetch the deployed contract code at the identified address.Affected if No source code is available or the contract code cannot be verified.
-
Check for SafeMath library usageSearch the contract code for 'SafeMath' library imports or usage in arithmetic operations, particularly in the mintToken function.Affected if SafeMath is not used in the mintToken function or not imported at all.
-
Inspect mintToken function for overflow protectionExamine the mintToken function implementation for explicit overflow checks (require statements) or SafeMath operations for balance and totalSupply variables.Affected if The function uses standard arithmetic operators (+, -, *, /) without overflow validation.
-
Verify owner privileges for balance manipulationReview the contract code to determine if the mintToken function can be called by the owner to set any user's balance to an arbitrary value without constraints.Affected if The owner can call mintToken to arbitrarily increase any user's balance without user consent or external validation.
You are affected if the deployed Residualvalue token contract lacks SafeMath or explicit overflow checks in its mintToken function, allowing the owner to manipulate balances arbitrarily.
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 an updated contract version that implements SafeMath library for arithmetic operations or explicit overflow checks in the mintToken function; if already deployed, migrate balances to a fixed contract and consider community notification for affected users.
- Consultation3.0 h
- Implementation6.0 h
- Testing5.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 $4,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-13599 — 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-13599 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