CVE-2018-13581
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 · uneditedThe mintToken function of a smart contract implementation for TravelCoin (TRV), 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 confidenceInteger overflow vulnerability in the mintToken function of the TravelCoin (TRV) Ethereum smart contract allows the contract owner to set arbitrary user balances to any value due to improper arithmetic bounds checking.
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 dataall versionsCVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check if you hold TravelCoin (TRV) tokensReview your cryptocurrency wallets (hardware, software, or exchange accounts) for any TRV token balances. Search for transactions involving the TravelCoin token contract address in your transaction history.Affected if You hold any amount of TRV tokens and the contract has not been migrated to a fixed version.
-
Identify the deployed TRV contract addressLook up the official TravelCoin token listing on blockchain explorers (Etherscan) or cryptocurrency tracking platforms to find the currently deployed contract address. Cross-reference with any token addition records in your wallet.Affected if The contract address resolves to the vulnerable Travelcointoken contract that has not been upgraded.
-
Verify the mintToken function in the contract source codeOn Etherscan or similar block explorer, locate the TRV token contract and view the verified source code. Search for the mintToken function and examine whether it uses SafeMath or similar overflow protection for arithmetic operations on the balance variable.Affected if The mintToken function performs arithmetic on balances without SafeMath or equivalent overflow checks.
-
Check total supply and owner minting activityCompare the current total supply of TRV tokens against the initial supply or expected supply. Review the contract transaction history for any mintToken calls initiated by the contract owner address that created unexpected balances.Affected if The total supply exceeds expected limits or the owner has executed mintToken transactions that created arbitrary balances.
You are affected if you hold TRV tokens from a contract whose mintToken function lacks proper integer overflow protection and whose owner has minted or can mint arbitrary balances.
Generated from the published advisory. Verify against your own configuration.
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 dataDeploy a fixed contract version with proper integer overflow/underflow checks (e.g., using SafeMath library) and migrate all balances; verify no other arithmetic vulnerabilities exist in the contract.
- Consultation4.0 h
- Implementation2.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,160.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-13581 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2018-13581 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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