dbcve.org
Super Cool Awesome MoneyApplication · Supercoolawesomemoney

CVE-2018-13516

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 Super Cool Awesome Money (SCAM), 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 SCAM Ethereum token smart contract contains an integer overflow vulnerability. This allows the contract owner to manipulate token balances arbitrarily by exploiting the overflow condition when minting tokens.

MitigationReplace arithmetic operations with SafeMath library functions (e.g., OpenZeppelin SafeMath) or migrate to Solidity 0.8+ which includes built-in overflow checks. For deployed contracts, migrate tokens to a new fixed contract address.

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
Super Cool Awesome MoneyApplication
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 the Super Cool Awesome Money token
    Check your Ethereum wallet or use a blockchain explorer (such as Etherscan) to search for token holdings associated with the token name 'Supercoolawesomemoney' or its contract address
    Affected if You hold or interact with a token contract named 'Super Cool Awesome Money' or 'Supercoolawesomemoney' on Ethereum
  2. Locate the contract source code
    On Etherscan or similar explorer, go to the Contract tab and look for the source code of the Super Cool Awesome Money token contract
    Affected if No source code is verified or available for public review on the blockchain explorer
  3. Identify the mintToken function in the contract
    Search the contract source code for the function named 'mintToken' - look for functions that handle token minting operations
    Affected if A mintToken function exists in the contract and performs arithmetic operations on token balances without using SafeMath library or Solidity 0.8+
  4. Check for integer overflow protection
    Examine the mintToken function and surrounding code to determine if arithmetic operations (addition, multiplication) use OpenZeppelin SafeMath functions or Solidity version 0.8+ which has built-in overflow checks
    Affected if The mintToken function uses direct arithmetic operators (+, *, etc.) without SafeMath wrappers and the contract is compiled with Solidity below 0.8.0
  5. Verify if you are a holder or have interacted with this specific contract address
    Review your transaction history and token balances for the specific contract address of Super Cool Awesome Money token
    Affected if You have received, held, or executed transactions with this particular token contract address

You are affected if you hold, have held, or have interacted with the Super Cool Awesome Money (Supercoolawesomemoney) token contract and that contract contains an unprotected mintToken function vulnerable to integer overflow.

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 arithmetic operations with SafeMath library functions (e.g., OpenZeppelin SafeMath) or migrate to Solidity 0.8+ which includes built-in overflow checks. For deployed contracts, migrate tokens to a new fixed contract address.

Fix this in Super Cool Awesome Money 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-13516 — 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-13516 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