dbcve.org
Cbr TokenApplication · Cbr Token Project

CVE-2018-13484

HIGH · 7.5 CVSS v3.0 Published 2018-07-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
The mintToken function of a smart contract implementation for CBRToken, 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 confidence

The CBRToken smart contract's mintToken function contains an integer overflow vulnerability that allows the contract owner to manipulate the balance of any user to arbitrary values. This occurs due to lack of proper overflow validation when updating token balances, enabling privilege escalation and token supply manipulation.

MitigationImplement SafeMath library or manual overflow/underflow checks in the mintToken function to validate arithmetic operations, and consider adding event logging and access control verification for balance modifications.

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 data
Cbr TokenApplication
Affected:all versions

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the deployed contract
    Query the blockchain for the contract at the CBRToken deployment address and verify the contract name/version metadata. For Ethereum, use tools like Etherscan or web3.js to call the contract's name() function or inspect the bytecode metadata.
    Affected if The contract is confirmed to be Cbr Token from the Cbr Token Project
  2. Verify mintToken function exists
    Inspect the contract's ABI or source code to confirm the mintToken function is present. Use a blockchain explorer or download the source code from Etherscan if verified, then check for function signature 'mintToken(address,uint256)'.
    Affected if The mintToken function is present in the deployed contract
  3. Check for SafeMath library usage
    Examine the contract source code for 'using SafeMath' statements or SafeMath library imports in the mintToken function scope. Search for library references in the contract file.
    Affected if SafeMath library is NOT imported or used within the mintToken function
  4. Inspect arithmetic overflow protection
    Review the mintToken function's body for explicit overflow/underflow checks before arithmetic operations on token balances. Look for require statements validating balance additions or uint256 overflow guards.
    Affected if No overflow validation exists before updating token balances in mintToken
  5. Confirm owner privilege for balance modification
    Verify the mintToken function has onlyOwner or similar access control modifier, or check if any address can call this function to modify balances.
    Affected if The function can be called by the contract owner to arbitrarily modify any user's balance

If the deployed contract is CBRToken with a mintToken function lacking SafeMath or explicit overflow checks, the integer overflow vulnerability is present and the owner can manipulate balances arbitrarily.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement SafeMath library or manual overflow/underflow checks in the mintToken function to validate arithmetic operations, and consider adding event logging and access control verification for balance modifications.

Fix this in Cbr Token Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-13484 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2018-13484 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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