CVE-2018-13586
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 Nectar (NCTR), 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 Nectar (NCTR) Ethereum token contract contains an integer overflow vulnerability that permits the contract owner to arbitrarily set any user's token balance to any value, enabling unauthorized manipulation of token supplies.
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 you hold NCTR tokensCheck your Ethereum wallet or blockchain explorer for Nectar (NCTR) token balance. Confirm the token contract address matches the Nectar token.Affected if You hold any NCTR tokens in a wallet connected to the vulnerable contract address.
-
Confirm you are the contract ownerIf you deployed or manage the NCTR contract, check the owner address using the owner() function or by querying the contract on a blockchain explorer.Affected if You are the contract owner and the contract contains the vulnerable mintToken function.
-
Locate the mintToken function in contract sourceObtain the NCTR contract source code (from Etherscan or your deployment files) and search for the mintToken function definition.Affected if The contract source contains a mintToken function without proper integer overflow checks.
-
Verify absence of overflow protectionExamine the mintToken function for use of SafeMath library for arithmetic operations, or confirm the contract uses Solidity version 0.8 or higher with built-in overflow checks.Affected if The mintToken function uses raw arithmetic (like + or -) without SafeMath and the contract is compiled with Solidity below 0.8.
You are affected if you hold NCTR tokens or are the owner of a deployed NCTR contract where the mintToken function lacks SafeMath or Solidity 0.8+ overflow protection.
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 vulnerable mintToken function must be rewritten with proper integer overflow protection (using SafeMath library or Solidity 0.8+ built-in checks), and the fixed contract should be redeployed with a migration strategy to transfer balances and maintain continuity.
- Consultation6.0 h
- Implementation12.0 h
- Testing10.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,504.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-13586 — 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-13586 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