dbcve.org
Stex Exchange IcoApplication · Stex Exchange Ico Project

CVE-2018-13198

HIGH · 7.5 CVSS v3.0 Published 2018-07-05
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 sell function of a smart contract implementation for STeX Exchange ICO (STE), an Ethereum token, has an integer overflow in which "amount * sellPrice" can be zero, consequently reducing a seller's assets.

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

In the STeX Exchange ICO (STE) Ethereum token smart contract, the sell function contains an integer overflow vulnerability in the calculation 'amount * sellPrice'. When specific values cause integer overflow, the result wraps to zero, causing sellers to receive zero proceeds while their tokens are deducted, effectively losing their assets.

MitigationReplace the vulnerable multiplication with SafeMath library functions (or migrate to Solidity 0.8+) to prevent integer overflow, and add explicit zero-value validation on the calculation result before proceeding with the token transfer.

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
Stex Exchange IcoApplication
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 deployed STE token contract
    Identify the contract address used for STeX Exchange ICO (STE) in your system or blockchain explorer. This is typically found in your token holdings, exchange records, or by searching for 'STeX Exchange ICO STE token contract address'.
    Affected if You are interacting with or holding the STE token contract at any address.
  2. Obtain the contract source code
    If the contract is verified on Etherscan or similar block explorers, locate and retrieve the source code. If you have direct access, compile the contract from your own deployment artifacts. Look for a function named 'sell' or 'sellTokens'.
    Affected if The source code is unavailable and cannot be audited for the vulnerability pattern.
  3. Inspect the sell function for vulnerable multiplication
    In the sell function, search for the calculation pattern 'amount * sellPrice' or similar multiplication of sell amount and price. Check if this multiplication is performed without using SafeMath library functions (such as mul) or without Solidity version 0.8+ which has built-in overflow checks.
    Affected if The multiplication 'amount * sellPrice' is performed directly without SafeMath or Solidity 0.8+ overflow protection.
  4. Check for zero-value validation
    Examine the code immediately after the multiplication calculation. Look for any explicit check that ensures the calculated amount is greater than zero before proceeding with the token transfer (for example, 'require(amount > 0)' or 'if (amount == 0) revert').
    Affected if There is no validation that the multiplication result is non-zero before transferring tokens.
  5. Test for overflow condition (if feasible)
    If you hold STE tokens and the contract is still operational, a cautious test could involve calling the sell function with carefully chosen values that could trigger overflow. However, this carries risk of actual token loss, so only attempt with a small test amount if other verification methods are unavailable.
    Affected if Calling sell with large values for amount and sellPrice results in zero proceeds while tokens are deducted, confirming the overflow vulnerability.

You are affected if your environment involves the STeX Exchange ICO (STE) token contract and the sell function contains unprotected 'amount * sellPrice' multiplication without SafeMath or Solidity 0.8+ overflow checks and lacks zero-value validation on the result.

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 multiplication with SafeMath library functions (or migrate to Solidity 0.8+) to prevent integer overflow, and add explicit zero-value validation on the calculation result before proceeding with the token transfer.

Fix this in Stex Exchange Ico 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-13198 — 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-13198 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