CVE-2018-13463
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 T-Swap-Token (T-S-T), 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 mintToken function in the T-Swap-Token (T-S-T) Ethereum smart contract contains an integer overflow vulnerability that allows the contract owner to manipulate any user's token balance to arbitrary 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 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 if T-Swap Token contract is deployedSearch your smart contract deployment records or blockchain explorers for contracts named 'T Swap Token' or 'T-S-T'. Retrieve the contract address if found.Affected if You have deployed or are running an instance of the T-Swap Token contract in your environment.
-
Verify contract ownershipCall the 'owner()' function on the contract or check the contract's state to determine the owner address. Compare this to your deployment address.Affected if You are the contract owner, as only the owner can invoke the vulnerable mintToken function.
-
Locate the mintToken function in contract sourceObtain the contract source code (from Etherscan if verified, or your deployment files) and search for a function named 'mintToken' or similar.Affected if The mintToken function exists in the deployed contract.
-
Check for integer overflow protection in mintTokenExamine the mintToken function code for use of SafeMath library methods (mul, add, sub) or explicit overflow/underflow checks before arithmetic operations on balance variables.Affected if The function performs arithmetic on balance variables without SafeMath or explicit overflow checks.
-
Confirm function allows arbitrary balance modificationReview the mintToken function signature and logic to verify it accepts a target address and amount parameter, and directly assigns the amount to the user's balance without constraints.Affected if The function takes an address and amount as input and directly sets the balance, allowing unrestricted manipulation.
You are affected if you have deployed the T-Swap Token contract and the mintToken function lacks SafeMath or overflow checks, allowing the owner to manipulate any user's balance to arbitrary values.
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 dataThe mintToken function should be updated to use safe math libraries or include explicit overflow/underflow checks to prevent integer overflow conditions when setting user balances.
- Consultation2.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,512.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-13463 — 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-13463 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