ROC Ethereum ERC20 Token request_dividend Smart Contract access control
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.7 | $5k-$25k | 0.00 |
Summary
A vulnerability labeled as critical has been found in ROC. Affected is the function request_dividend of the component Ethereum ERC20 Token Handler. The manipulation as part of Smart Contract results in access control.
This vulnerability is identified as CVE-2018-10944. The attack can be executed remotely. There is not any exploit available.
Details
A vulnerability classified as critical has been found in ROC (the affected version unknown). Affected is the function request_dividend of the component Ethereum ERC20 Token Handler. The manipulation as part of a Smart Contract leads to a access control vulnerability. CWE is classifying the issue as CWE-284. The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor. This is going to have an impact on confidentiality, integrity, and availability. CVE summarizes:
The request_dividend function of a smart contract implementation for ROC (aka Rasputin Online Coin), an Ethereum ERC20 token, allows attackers to steal all of the contract's Ether.
The bug was discovered 05/14/2018. The weakness was released 05/14/2018 (Website). The advisory is available at medium.com. This vulnerability is traded as CVE-2018-10944 since 05/09/2018. It is possible to launch the attack remotely. The exploitation doesn't require any form of authentication. Technical details are known, but there is no available exploit. The structure of the vulnerability defines a possible price range of USD $5k-$25k at the moment (estimation calculated on 02/04/2020). This vulnerability is assigned to T1068 by the MITRE ATT&CK project.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Name
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.7VulDB Meta Temp Score: 5.7
VulDB Base Score: 5.6
VulDB Temp Score: 5.6
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 5.9
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: 🔍
Timeline
05/09/2018 🔍05/13/2018 🔍
05/14/2018 🔍
05/14/2018 🔍
05/14/2018 🔍
02/04/2020 🔍
Sources
Advisory: medium.comStatus: Not defined
CVE: CVE-2018-10944 (🔍)
GCVE (CVE): GCVE-0-2018-10944
GCVE (VulDB): GCVE-100-117666
Entry
Created: 05/14/2018 12:30Updated: 02/04/2020 20:09
Changes: 05/14/2018 12:30 (56), 02/04/2020 20:09 (1)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.