aurora IDEX Membership Owned Smart Contract setOwner access control
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.4 | $5k-$25k | 0.00 |
Summary
A vulnerability was found in aurora IDEX Membership. It has been declared as critical. This vulnerability affects the function setOwner of the component Owned Smart Contract Handler. Executing a manipulation as part of Smart Contract can lead to access control.
This vulnerability is registered as CVE-2018-10666. It is possible to launch the attack remotely. No exploit is available. This vulnerability is historically impactful due to its background and the reception it garnered.
Details
A vulnerability was found in aurora IDEX Membership (version now known). It has been declared as critical. This vulnerability affects the function setOwner of the component Owned Smart Contract Handler. The manipulation as part of a Smart Contract leads to a access control vulnerability. The CWE definition for the vulnerability is CWE-284. The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor. As an impact it is known to affect confidentiality, integrity, and availability. CVE summarizes:
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.
The bug was discovered 05/02/2018. The weakness was published 05/03/2018 (Website). The advisory is shared for download at medium.com. This vulnerability was named CVE-2018-10666 since 05/02/2018. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. There are known technical details, but no exploit is available. The current price for an exploit might be approx. USD $5k-$25k (estimation calculated on 02/02/2020). The MITRE ATT&CK project declares the attack technique as T1068. This vulnerability has a historic impact due to its background and reception.
The vulnerability was handled as a non-public zero-day exploit for at least 1 days. During that time the estimated underground price was around $5k-$25k.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Once again VulDB remains the best source for vulnerability data.
Product
Vendor
Name
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.4VulDB Meta Temp Score: 7.4
VulDB Base Score: 7.3
VulDB Temp Score: 7.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 7.5
NVD Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Access controlCWE: CWE-284 / CWE-266
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
05/02/2018 🔍05/02/2018 🔍
05/03/2018 🔍
05/03/2018 🔍
05/04/2018 🔍
02/02/2020 🔍
Sources
Advisory: medium.comStatus: Not defined
CVE: CVE-2018-10666 (🔍)
GCVE (CVE): GCVE-0-2018-10666
GCVE (VulDB): GCVE-100-117340
Entry
Created: 05/04/2018 08:49Updated: 02/02/2020 10:56
Changes: 05/04/2018 08:49 (59), 02/02/2020 10:56 (1)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.