LiveActive security incident?Get immediate response
CVE Record

CVE-2018-10666: The Owned smart contract implementation for Aurora IDEX Membership (IDXM), an Ethereum ERC20 token, allows...

The 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.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2018-10666 concerns the Aurora IDEX Membership (IDXM) ERC20 token smart contract. A public ownership-change function could let an attacker make themselves contract owner, then change contract variables. The bundle does not provide CVSS, affected versions, patch details, or confirmed exploitation.

Executive priority

Treat as high priority only if the organization holds, integrates, or depends on IDXM. Otherwise, track as niche blockchain exposure with incomplete remediation evidence.

Technical view

The vulnerable Owned implementation exposes setOwner as public, allowing unauthorized ownership reassignment. Once ownership is obtained, the new owner can modify variables controlled by that role. The available record identifies IDXM specifically but does not include contract address, affected versioning, exploit telemetry, or remediation status.

Likely exposure

Exposure appears limited to the Aurora IDEX Membership (IDXM) ERC20 token implementation and any systems relying on that contract’s ownership-controlled behavior. The source bundle does not identify broader products, CPEs, or affected versions.

Exploitation context

The CVE is not listed as CISA KEV, and the provided sources do not confirm active exploitation. The issue is conceptually serious because public blockchain contracts are externally callable, but exploit status and real-world impact are not established in the bundle.

Researcher notes

Evidence is sparse: one CVE description and one public write-up are listed. No CVSS, CWE, CPE, patch, contract address, or exploitation confirmation is included. Validate against the actual deployed contract before drawing operational conclusions.

Mitigation direction

  • Check Aurora or IDEX guidance for migration, deprecation, or fixed contract information.
  • Avoid new reliance on the vulnerable IDXM contract until ownership state is verified.
  • Review integrations that depend on IDXM ownership-controlled variables or token behavior.
  • For reused code, restrict ownership changes to authorized owners or governance.
  • Document any business dependency on IDXM for risk acceptance decisions.

Validation and detection

  • Confirm whether your organization holds, integrates, or monitors IDXM.
  • Review the deployed contract source for a public setOwner function.
  • Check current contract owner and recent ownership-change history on-chain.
  • Identify downstream systems trusting owner-controlled variables from this contract.
  • Record absence or presence of vendor migration guidance.
Prepared
Confidence
medium
Sources
3

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

description · low confidence lookup

Credential and access behavior lookup

The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2018-10666 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.