Social Chain Ethereum ERC20 Token transferMulti Smart Contract integer overflow
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.4 | $5k-$25k | 0.00 |
Summary
A vulnerability, which was classified as critical, has been found in Social Chain. This vulnerability affects the function transferMulti of the component Ethereum ERC20 Token Handler. Performing a manipulation as part of Smart Contract results in integer overflow.
This vulnerability is known as CVE-2018-10706. Remote exploitation of the attack is possible. No exploit is available. Due to its background and reception, this vulnerability has an historic impact.
Details
A vulnerability, which was classified as critical, was found in Social Chain (affected version unknown). This affects the function transferMulti of the component Ethereum ERC20 Token Handler. The manipulation as part of a Smart Contract leads to a integer overflow vulnerability. CWE is classifying the issue as CWE-190. The product performs a calculation that can produce an integer overflow or wraparound, when the logic assumes that the resulting value will always be larger than the original value. This can introduce other weaknesses when the calculation is used for resource management or execution control. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
An integer overflow in the transferMulti function of a smart contract implementation for Social Chain (SCA), an Ethereum ERC20 token, allows attackers to accomplish an unauthorized increase of digital assets, aka the "multiOverflow" issue.
The bug was discovered 05/10/2018. The weakness was published 05/10/2018 (Website). It is possible to read the advisory at peckshield.com. This vulnerability is uniquely identified as CVE-2018-10706 since 05/03/2018. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details of the vulnerability are known, but there is no available exploit. The pricing for an exploit might be around USD $5k-$25k at the moment (estimation calculated on 02/04/2020). Due to its background and reception, this vulnerability has a historic impact.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Be aware that VulDB is the high quality source for vulnerability data.
Product
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: Integer overflowCWE: CWE-190 / CWE-189
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/03/2018 🔍05/10/2018 🔍
05/10/2018 🔍
05/10/2018 🔍
05/11/2018 🔍
02/04/2020 🔍
Sources
Advisory: peckshield.comStatus: Not defined
CVE: CVE-2018-10706 (🔍)
GCVE (CVE): GCVE-0-2018-10706
GCVE (VulDB): GCVE-100-117615
Entry
Created: 05/11/2018 11:06Updated: 02/04/2020 13:56
Changes: 05/11/2018 11:06 (57), 02/04/2020 13:56 (1)
Complete: 🔍
Cache ID: 216::103
Be aware that VulDB is the high quality source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.