dbcve.org
BgamecoinApplication · Bgamecoin Project

CVE-2018-13551

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 Bgamecoin, 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 Bgamecoin Ethereum smart contract contains an integer overflow vulnerability that allows the contract owner to arbitrarily set any user's token balance to any value. This flaw combines a logic/authorization weakness with integer overflow, enabling unauthorized balance manipulation that could result in unauthorized token creation, theft, or complete compromise of the token's integrity.

MitigationReplace the vulnerable mintToken function with a secure implementation using SafeMath library or Solidity 0.8+ built-in overflow checks, and implement proper access controls limiting minting to appropriate roles. The contract will likely require redeployment with the corrected code and migration of token balances.

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
BgamecoinApplication
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 if you hold Bgamecoin tokens
    Check your Ethereum wallet (e.g., MetaMask, MyEtherWallet) for a Bgamecoin token balance, or query the Bgamecoin contract balanceOf your address using a blockchain explorer or web3 call
    Affected if Your address holds a non-zero BGB token balance and the contract address matches the vulnerable Bgamecoin contract
  2. Locate the Bgamecoin contract address
    Obtain the official Bgamecoin token contract address from the project documentation, etherscan, or token listing sites. Verify this is the Bgamecoin (BGB) token
    Affected if You have interacted with or hold tokens from this specific contract address
  3. Inspect the mintToken function source code
    On Etherscan or similar block explorer, view the contract source code and locate the mintToken function. Look for arithmetic operations (addition, multiplication) on token balances or totalSupply without SafeMath or Solidity 0.8+ overflow protection
    Affected if The mintToken function contains unchecked arithmetic operations on _amount, _value, or similar variables that can overflow (e.g., balances[to] += _value without overflow check)
  4. Check function accessibility and access control
    Examine whether mintToken has a require statement or modifier restricting who can call it (e.g., onlyOwner), and whether the vulnerability allows bypassing this control
    Affected if The mintToken function either lacks access control or the integer overflow flaw allows circumvention of existing access controls

You are affected if you hold Bgamecoin tokens from a contract whose mintToken function contains unchecked arithmetic operations enabling arbitrary balance manipulation.

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

Replace the vulnerable mintToken function with a secure implementation using SafeMath library or Solidity 0.8+ built-in overflow checks, and implement proper access controls limiting minting to appropriate roles. The contract will likely require redeployment with the corrected code and migration of token balances.

Fix this in Bgamecoin Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA3.0 h
13.0 hours of engineering $2,310
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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