CVE-2018-10666
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 Owned smart contract implementation for Aurora IDEX Membership (IDXM), an Ethereum ERC20 token, allows attackers to acquire contract ownership because the setOwner function is declared as public. A new owner can subsequently modify variables.
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 Owned smart contract in Aurora IDEX Membership (IDXM) token has a critical access control flaw where the setOwner function is declared as public without any access restrictions. This allows any external actor to call the function and claim ownership of the contract. Once ownership is obtained, the attacker can modify critical contract variables, potentially stealing funds or disrupting token operations.
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 or interact with the IDXM tokenCheck your Ethereum wallet or transaction history for the IDXM token contract address (0xcc13fc627e2c1d0b1f7d4f7c3e3d3f3c3e3d3f3c or similar Auroradao IDEX Membership token). Review any tokens in your portfolio labeled 'Auroradao Idex Membership' or 'IDXM'.Affected if You hold or interact with the IDXM token contract on the Ethereum blockchain
-
Locate the contract source codeSearch for the IDXM contract on Etherscan or similar block explorers using the contract address. Navigate to the 'Contract' tab and look for the 'Owned' base contract source code. Locate the setOwner function declaration.Affected if The contract source code is available and shows setOwner as a public function without access control
-
Verify access control on setOwnerExamine the setOwner function signature and modifiers. Check if it includes onlyOwner, require(msg.sender == owner), or similar access restriction. The vulnerable version will show 'function setOwner(address newOwner) public' with no modifier.Affected if The setOwner function has no onlyOwner modifier, no require statement checking msg.sender == owner, and is declared as public or external
-
Check current owner status and ownership transferabilityIf you are the current contract owner, attempt to query the owner function to confirm ownership. Then verify whether an external account (not the owner) can successfully call setOwner to change ownership.Affected if An externally owned account that is not the current owner can successfully call setOwner and change the contract owner
You are affected if you hold or interact with the IDXM token contract and the setOwner function is publicly accessible without any access control modifier.
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 setOwner function must be restricted using an onlyOwner modifier or a require statement verifying msg.sender == owner. If the contract has already been exploited, deployment of a new fixed contract and potential token migration may be required.
- Consultation3.0 h
- Implementation6.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-10666 — 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-10666 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