CVE-2018-13511
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 CorelliCoin, 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 · moderate confidenceThe CorelliCoin smart contract contains an integer overflow vulnerability in its mintToken function. This allows the contract owner to manipulate token balances arbitrarily by exploiting the overflow condition when minting new tokens, effectively granting themselves unlimited token creation capability.
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.
-
Locate Corellicoin contract deploymentSearch your smart contract inventory, deployment records, or blockchain explorers for any deployed instances of the Corellicoin contract (search by contract address or transaction history involving Corellicoin)Affected if You have deployed the Corellicoin contract to any Ethereum network
-
Obtain contract source codeIf the contract is verified on Etherscan or similar explorers, retrieve the source code. If unverified, decompile using tools like Panoptic or etherscan's decompiler to examine the mintToken functionAffected if The source code or decompiled bytecode reveals a mintToken function without SafeMath library or explicit overflow checks
-
Inspect mintToken function for overflow protectionExamine the mintToken function in the source code: look for 'SafeMath' library usage on arithmetic operations (add, mul, sub), or explicit require statements checking for overflow conditions before arithmetic operationsAffected if The mintToken function performs balance updates using direct arithmetic operators (+, *, -) without SafeMath or overflow validation require statements
-
Check mintToken access controlVerify that the mintToken function exists and is callable by the contract owner (check the function modifier - typically 'onlyOwner' or ownership verification in the function body)Affected if The mintToken function is present and accessible to the owner without additional safeguards beyond access control
-
Analyze token balance stateIf you have read access to the contract, query token balances of the owner address using the balanceOf function and compare against expected mint amounts; look for unusually high balance values that could indicate overflow manipulationAffected if The owner's balance shows unexpectedly high values or the totalSupply variable exceeds reasonable token issuance limits
If you have deployed the Corellicoin smart contract and its mintToken function lacks SafeMath or explicit overflow/underflow checks, your environment is affected by this vulnerability.
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 dataRemediate by implementing safe math libraries (e.g., OpenZeppelin's SafeMath) or explicit overflow/underflow checks in the mintToken function. Since Ethereum smart contracts are immutable post-deployment, this requires deploying a fixed version of the contract and migrating user balances.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-13511 — 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-13511 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