dbcve.org
TravelcoinApplication

CVE-2018-13213

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 TravelCoin (TRV), 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

Integer overflow vulnerability in the sell function of the TravelCoin (TRV) Ethereum token smart contract where the multiplication amount * sellPrice can wrap around to zero due to missing or inadequate overflow checks, causing sellers to lose their tokens/assets while receiving zero compensation.

MitigationImplement SafeMath library for arithmetic operations or upgrade to Solidity 0.8+ which includes built-in overflow checks to prevent the amount * sellPrice multiplication from producing incorrect zero values.

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
TravelcoinApplication
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 or interact with TravelCoin (TRV) tokens
    Check your Ethereum wallet or blockchain explorer for TRV token balance or any interaction with the TravelCoin contract address
    Affected if You hold a non-zero TRV token balance or have interacted with the TRV token contract
  2. Locate the TravelCoin contract source code
    Search for TravelCoin (TRV) on Etherscan or similar block explorers, then look for the 'Contract' tab to view the source code
    Affected if The contract source code is available and shows the sell function implementation
  3. Check if SafeMath library is used in the sell function
    In the contract source code, look for 'using SafeMath' import statement and verify that the multiplication amount * sellPrice uses SafeMath.mul() or equivalent
    Affected if No SafeMath library is imported and the multiplication uses native Solidity arithmetic operators (* instead of SafeMath.mul())
  4. Check the Solidity compiler version used
    In the contract source code metadata or at the top of the file, look for 'pragma solidity' version declaration
    Affected if The contract is compiled with Solidity version below 0.8.0 (e.g., pragma solidity ^0.4.x) and has no SafeMath library
  5. Verify the sell function lacks overflow protection
    Locate the 'sell' function in the contract and examine the line performing amount * sellPrice multiplication
    Affected if The multiplication uses plain arithmetic operator * without any overflow check or SafeMath wrapper
  6. Test a small sell transaction to observe behavior
    If you hold TRV tokens, attempt to sell a small amount using the token's sell function and verify the received ETH amount
    Affected if The transaction executes but returns zero ETH despite successfully selling tokens, indicating the overflow wrapped the result to zero

You are affected if you hold TravelCoin (TRV) tokens and the deployed contract lacks SafeMath library protection AND uses Solidity version below 0.8.0 for the sell function where amount * sellPrice can overflow to zero.

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

Implement SafeMath library for arithmetic operations or upgrade to Solidity 0.8+ which includes built-in overflow checks to prevent the amount * sellPrice multiplication from producing incorrect zero values.

Fix this in Travelcoin Scoped from the published advisory
  • Consultation3.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
21.0 hours of engineering $3,660
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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