CVE-2018-13209
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 sell function of a smart contract implementation for Nectar (NCTR), an Ethereum token, has an integer overflow in which "amount * sellPrice" can be zero, consequently reducing a seller's assets.
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 sell function in the Nectar (NCTR) Ethereum token smart contract suffers from an integer overflow vulnerability where the multiplication 'amount * sellPrice' can wrap around to zero due to missing overflow validation, causing sellers to lose their token value when converting to ETH.
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 Nectar token deploymentLocate the smart contract address for Nectar (NCTR) in your environment or check if you hold NCTR tokens. Verify the contract address matches the official Nectar token contract.Affected if You hold or have deployed the Nectar (NCTR) token contract at the official contract address.
-
Locate the sell function source codeObtain the source code of the Nectar token contract and locate the sell function. This is typically available on Etherscan or GitHub repositories for the project.Affected if The sell function exists in the deployed contract.
-
Check for SafeMath library usage in multiplicationSearch the sell function code for 'SafeMath' library calls or look for the multiplication operation 'amount * sellPrice'. Verify if SafeMath.mul or similar overflow-safe arithmetic is used.Affected if The multiplication 'amount * sellPrice' is performed without SafeMath or overflow validation.
-
Verify explicit overflow checks existInspect the code immediately before the multiplication to see if there is an explicit check such as 'require(amount > 0)' or 'require(amount * sellPrice > 0)' or similar validation that would prevent wrapping to zero.Affected if No explicit overflow check exists before the multiplication that would catch the wrap-around to zero condition.
You are affected if you interact with the Nectar token contract and its sell function performs the multiplication without SafeMath or explicit overflow validation, allowing the product to wrap to zero and causing token value loss.
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 dataImplement SafeMath library for arithmetic operations or add explicit overflow checks before the multiplication to prevent the product from wrapping to zero.
- 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-13209 — 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-13209 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