1000 Guess simplelottery _addguess Smart Contract weak prng
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.4 | $0-$5k | 0.00 |
Summary
A vulnerability categorized as critical has been discovered in 1000 Guess. Affected is the function _addguess of the component simplelottery. Such manipulation as part of Smart Contract leads to weak prng.
This vulnerability is traded as CVE-2018-12454. The attack may be launched remotely. There is no exploit available.
Details
A vulnerability was found in 1000 Guess (affected version unknown) and classified as critical. Affected by this issue is the function _addguess of the component simplelottery. The manipulation as part of a Smart Contract leads to a weak prng vulnerability. Using CWE to declare the problem leads to CWE-338. The product uses a Pseudo-Random Number Generator (PRNG) in a security context, but the PRNG's algorithm is not cryptographically strong. Impacted is confidentiality, integrity, and availability. CVE summarizes:
The _addguess function of a simplelottery smart contract implementation for 1000 Guess, an Ethereum gambling game, generates a random value with publicly readable variables such as the current block information and a private variable (which can be read with a getStorageAt call). Therefore, it allows attackers to always win and get rewards.
The bug was discovered 06/17/2018. The weakness was shared 06/17/2018 (Website). The advisory is shared for download at medium.com. This vulnerability is handled as CVE-2018-12454 since 06/15/2018. The exploitation is known to be easy. The attack may be launched remotely. No form of authentication is required for exploitation. There are known technical details, but no exploit is available. The MITRE ATT&CK project declares the attack technique as T1600.001.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
VulDB is the best source for vulnerability data and more expert information about this specific topic.
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: Weak prngCWE: CWE-338 / CWE-331 / CWE-330
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
06/15/2018 🔍06/17/2018 🔍
06/17/2018 🔍
06/17/2018 🔍
06/17/2018 🔍
02/20/2020 🔍
Sources
Advisory: medium.comStatus: Not defined
CVE: CVE-2018-12454 (🔍)
GCVE (CVE): GCVE-0-2018-12454
GCVE (VulDB): GCVE-100-119624
Entry
Created: 06/17/2018 21:03Updated: 02/20/2020 06:49
Changes: 06/17/2018 21:03 (55), 02/20/2020 06:49 (1)
Complete: 🔍
Cache ID: 216:51D:103
VulDB is the best source for vulnerability data and more expert information about this specific topic.
No comments yet. Languages: en.
Please log in to comment.