dbcve.org
Trabet Coin PreicoApplication · Trabet Coin Preico Project

CVE-2018-13552

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_PreICO, 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

Integer overflow vulnerability in the mintToken function of the Trabet_Coin_PreICO Ethereum smart contract allows the contract owner to set arbitrary token balances for any user due to missing or inadequate integer overflow/underflow checks when assigning balance values.

MitigationReplace the vulnerable mintToken function with a secure implementation using SafeMath library for arithmetic operations or explicit bounds checking, and consider deploying a new fixed contract with token migration if the original is already in production.

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 Coin PreicoApplication
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 Trabet Coin Preico contract is deployed
    Search your blockchain explorer or deployment records for contracts at addresses associated with the Trabet Coin Preico project. Check if a contract with the name 'Trabet_Coin_PreICO' or similar exists in your environment.
    Affected if A contract matching the Trabet Coin Preico project is found on any network you operate or monitor.
  2. Retrieve the contract source code
    If the contract is verified on block explorers like Etherscan, view the source code. Look for the mintToken function definition.
    Affected if The mintToken function is present and allows the owner to modify user balances without documented overflow protection.
  3. Check for SafeMath library usage in mintToken
    Inspect the mintToken function code. Look for 'using SafeMath' statements or SafeMath method calls (add, sub, mul) used for balance arithmetic.
    Affected if The function performs arithmetic operations (addition, multiplication) on balance variables without using SafeMath or explicit bounds checking.
  4. Verify caller role for mintToken execution
    Check the function modifier on mintToken - look for 'onlyOwner' or similar access control. Determine if your address holds the owner role in the contract.
    Affected if You are the contract owner and can call mintToken, or the current owner can arbitrarily set balances.
  5. Check for integer overflow protection mechanisms
    Review all arithmetic operations in mintToken that involve balance assignments. Look for explicit checks like 'require(newBalance >= oldBalance)' or use of SafeMath library functions.
    Affected if No overflow/underflow guards exist on the balance assignment operations within mintToken.

If the Trabet Coin Preico contract is deployed in your environment and the mintToken function lacks SafeMath or explicit bounds checking on balance arithmetic, you are 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

Replace the vulnerable mintToken function with a secure implementation using SafeMath library for arithmetic operations or explicit bounds checking, and consider deploying a new fixed contract with token migration if the original is already in production.

Fix this in Trabet Coin Preico Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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