dbcve.org
Trabet CoinApplication · Trabet Coin Project

CVE-2018-13557

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 Trabet_Coin, 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 Trabet_Coin Ethereum smart contract contains an integer overflow vulnerability that allows the contract owner to manipulate arbitrary user balances to any value. This occurs because the function does not properly validate arithmetic operations when minting new tokens, potentially causing the balance to wrap around or be set to unexpected values.

MitigationThe vulnerable contract should be updated to use SafeMath library functions for all arithmetic operations or implement explicit overflow/underflow checks in the mintToken function. Consider redeploying the contract with corrected logic and migrating token balances if any manipulation occurred.

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
Trabet CoinApplication
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 Trabet Coin contract in your environment
    Identify the contract address you are using for Trabet Coin. Query the blockchain explorer or your local node for the deployed contract at that address.
    Affected if A Trabet Coin contract is deployed and you are using it for token operations
  2. Obtain the contract source code or bytecode
    Retrieve the contract's source code from a blockchain explorer (Etherscan), your source code repository, or by decompiling the bytecode if source is unavailable.
    Affected if You cannot verify the source code and must rely on the deployed contract behavior
  3. Inspect the mintToken function for SafeMath usage
    Locate the mintToken function in the source code. Check if the arithmetic operations (balance additions, totalSupply updates) use SafeMath library functions (add, sub, mul) instead of plain Solidity operators (+, -, *).
    Affected if The mintToken function uses plain arithmetic operators (+, -, *) without SafeMath library calls, indicating vulnerability to integer overflow
  4. Verify explicit overflow checks exist
    If SafeMath is not used, check if the function contains manual checks such as require(balance + amount > balance) or require(newBalance >= oldBalance) before updating balances.
    Affected if No SafeMath is used and no explicit overflow/underflow validation checks are present before arithmetic operations in mintToken
  5. Confirm you are the contract owner or a token holder
    Check your role: if you are the contract owner, you can call mintToken; if you are a holder, check your balance history for unexpected changes.
    Affected if You interact with this contract as owner (can exploit) or as holder (balance can be manipulated)

If a Trabet Coin contract is deployed in your environment and the mintToken function lacks SafeMath or explicit overflow checks, your environment is affected by CVE-2018-13557.

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

The vulnerable contract should be updated to use SafeMath library functions for all arithmetic operations or implement explicit overflow/underflow checks in the mintToken function. Consider redeploying the contract with corrected logic and migrating token balances if any manipulation occurred.

Fix this in Trabet Coin Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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