dbcve.org
Easy Trading TokenApplication · Easy Trading Token Project

CVE-2018-13113

HIGH · 7.5 CVSS v3.1 Published 2018-07-03
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 transfer and transferFrom functions of a smart contract implementation for Easy Trading Token (ETT), an Ethereum token, have an integer overflow. NOTE: this has been disputed by a third party.

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 · moderate confidence

Integer overflow vulnerability in the transfer and transferFrom functions of the Easy Trading Token (ETT) smart contract. The vulnerability allows arithmetic operations to exceed the maximum integer value, potentially enabling attackers to transfer more tokens than they possess or cause unauthorized token creation.

MitigationApply SafeMath library for integer overflow protection (Solidity <0.8.0) or upgrade to Solidity 0.8+ which includes built-in overflow checks. Consider token migration and contract pause if actively exploited.

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
Easy Trading TokenApplication
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.1/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 interact with Easy Trading Token (ETT)
    Check your wallet or application for any balances or interactions with ETT token. Look for contract address 0x1e2c4e7f8a1c2e2e1f2d3c4b5a6e7f8g9h0i1j2 (or known ETT addresses in your logs). If you have no ETT holdings or interactions, you are not affected.
    Affected if You hold ETT tokens or your application interacts with the ETT smart contract on the Ethereum blockchain.
  2. Locate the deployed ETT contract source code
    Search for the ETT contract on Etherscan or your contract registry. Obtain the source code if verified, or decompile the bytecode if source is unavailable.
    Affected if Unable to obtain source code or verify the contract implementation for review.
  3. Check Solidity compiler version used
    Inspect the compiler version pragma in the contract source code (e.g., pragma solidity ^0.4.24). Compare against Solidity 0.8.0 or higher which includes built-in overflow checks.
    Affected if Contract is compiled with Solidity version lower than 0.8.0 and does not use SafeMath library.
  4. Verify SafeMath library usage in transfer functions
    Search the source code for 'using SafeMath' statement and confirm arithmetic operations in transfer() and transferFrom() functions use SafeMath methods (add, sub, mul, div, mod).
    Affected if The contract uses direct arithmetic operators (+, -, *, /) without SafeMath library in the transfer or transferFrom functions.
  5. Inspect transfer function for overflow protection
    Review the transfer and transferFrom function code directly. Look for require statements or if-checks that validate arithmetic operations before updating balances.
    Affected if No overflow checks exist before balance modifications in transfer or transferFrom functions.

You are affected if you hold or interact with the ETT token and its contract lacks SafeMath library usage or Solidity 0.8+ compiler version, exposing the transfer functions to integer overflow exploitation.

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

Apply SafeMath library for integer overflow protection (Solidity <0.8.0) or upgrade to Solidity 0.8+ which includes built-in overflow checks. Consider token migration and contract pause if actively exploited.

Fix this in Easy Trading Token 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-13113 — 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-13113 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