dbcve.org
UbiouApplication

CVE-2018-13513

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 Ubiou, 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 mintToken function in the Ubiou Ethereum token contract contains an integer overflow vulnerability that allows the contract owner to set any user's balance to an arbitrary value. This occurs due to missing overflow validation in arithmetic operations during token minting, enabling manipulation of the token supply and user balances.

MitigationImplement SafeMath library or upgrade to Solidity 0.8+ for built-in overflow protection, and remove or properly restrict the owner's ability to arbitrarily set user balances with appropriate access 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 data
UbiouApplication
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. Locate the mintToken function in the contract source or deployed bytecode
    Search the contract code for 'function mintToken' or its disassembly in the deployed contract. For deployed contracts, use a blockchain explorer (Etherscan) to view the contract source or decompile the bytecode.
    Affected if The mintToken function exists and contains arithmetic operations on token balances or totalSupply without SafeMath or overflow checks.
  2. Verify SafeMath library usage
    Search the contract for 'import "./SafeMath.sol"' or 'using SafeMath for' statements. Check if arithmetic operations (+, -, *, /) in mintToken use SafeMath methods (add, sub, mul, div).
    Affected if SafeMath is not imported or not used for arithmetic operations in the mintToken function, leaving overflow/underflow checks missing.
  3. Check the Solidity compiler version
    Look for 'pragma solidity ^X.X.X' or 'pragma solidity >=X.X.X' at the top of the source code. Confirm the compiler version used during deployment.
    Affected if The contract is compiled with Solidity versions below 0.8.0, which do not have built-in overflow protection.
  4. Inspect the mintToken function for unchecked arithmetic
    Review the mintToken function body for statements like 'balances[target] += mintAmount' or 'totalSupply += mintAmount' without using SafeMath methods or explicit overflow checks (require statements validating the result).
    Affected if The function contains direct arithmetic operators (+, -, *, /) on balances or totalSupply without overflow validation.
  5. Examine owner access control on balance manipulation
    Review mintToken to see if it allows the owner to directly set an arbitrary balance (e.g., 'balances[target] = amount' or similar) without constraints or minting logic.
    Affected if The owner can set any user's balance to an arbitrary value through mintToken without proper constraints or validation.

If the contract uses Solidity below 0.8 without SafeMath and the mintToken function contains unchecked arithmetic operations that allow the owner to manipulate balances arbitrarily, the environment is affected by this vulnerability.

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 upgrade to Solidity 0.8+ for built-in overflow protection, and remove or properly restrict the owner's ability to arbitrarily set user balances with appropriate access controls.

Fix this in Ubiou Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-13513 — 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-13513 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