CVE-2018-13621
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 SoundTribeToken, 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 SoundTribeToken Ethereum smart contract allows the contract owner to set arbitrary token balances for any user, effectively enabling unauthorized balance manipulation.
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 SoundTribeToken contract deploymentSearch your contract deployment records, blockchain explorers, or project repository for any deployed instance of the SoundTribeToken smart contract. Look for contracts with the name 'SoundTribeToken' or 'Soundtribetoken'.Affected if You have deployed or are using the SoundTribeToken contract in any environment.
-
Locate the mintToken function source codeObtain the source code of the deployed contract (from Etherscan verification, your repository, or contract discovery tools). Locate the mintToken function definition.Affected if The mintToken function exists in your deployed contract and allows the owner to set arbitrary balances.
-
Check for SafeMath usage in mintTokenInspect the mintToken function code for use of SafeMath library for arithmetic operations (look for SafeMath.add, SafeMath.sub, SafeMath.mul, or similar). Also check for any manual overflow checks.Affected if The mintToken function does not use SafeMath or any overflow protection for balance arithmetic operations.
-
Verify owner-only access to mintTokenCheck the function modifier on mintToken (such as 'onlyOwner' or similar access control) and determine if the function allows setting balances to any value without internal constraints.Affected if The mintToken function can be called by the contract owner to set arbitrary token balances for any user.
You are affected if you have deployed the SoundTribeToken contract and its mintToken function lacks SafeMath overflow protection while allowing the owner to manipulate balances arbitrarily.
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 dataFix the integer overflow in mintToken using SafeMath or appropriate arithmetic checks, and implement proper access controls or remove owner-only arbitrary balance-setting functionality; redeploy contract and migrate token holders if already deployed.
- Consultation4.0 h
- Implementation8.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-13621 — 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-13621 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