CVE-2018-13620
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 TripCash, 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 confidenceThe TripCash Ethereum token smart contract contains an integer overflow vulnerability in the mintToken function. This allows the contract owner to manipulate arbitrary user balances to any value due to unchecked integer arithmetic.
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.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 checksWork through these to decide whether this CVE applies to you.
-
Identify TripCash token holdingsSearch your Ethereum wallets (Metamask, MyEtherWallet, hardware wallets) for TRIP token balance, or query the blockchain for your address balances using Etherscan or web3 APIAffected if You hold any amount of TRIP tokens or interact with the TripCash contract address on mainnet
-
Locate the deployed TripCash contractQuery the Ethereum blockchain for contract address 0x1961b3331969ed52770751fc718ef1105d3612a or search for 'TripCash' token on Etherscan/blockscoutAffected if You have deployed, own, or interact with this specific contract address on any Ethereum network
-
Inspect mintToken function source codeView the contract source code on Etherscan (Contract tab > Code) or decompile the contract using a tool like decompiler.ethereum.org. Search for function mintToken and examine the arithmetic operationsAffected if The mintToken function contains arithmetic operations (+, -, *, /) on balances without using SafeMath library or explicit overflow checks
-
Verify owner privilegesCheck the contract owner address by calling owner() or checking the contract deployment account. Look for functions that allow the owner to modify user balances (mintToken, transfer, etc.)Affected if The contract has an owner account that can call mintToken and the function does not validate overflow on the 'amount' parameter or balance variables
-
Monitor for unauthorized balance changesQuery current token balance of your address using balanceOf() function, then compare against historical transactions on Etherscan or via past balance snapshotsAffected if Your token balance has changed without your signed transactions, or you see mintToken calls in transaction history that you did not authorize
You are affected if you hold TripCash (TRIP) tokens from the vulnerable contract and the deployed mintToken function lacks SafeMath or overflow checks, allowing the contract owner to arbitrarily inflate your balance.
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 dataReplace standard integer arithmetic with SafeMath library or implement explicit overflow/underflow checks in the mintToken function; consider upgrading to a newer, audited token standard if the contract cannot be safely modified.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.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 $3,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-13620 — 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-13620 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