CVE-2018-17968: A gambling smart contract implementation for RuletkaIo, an Ethereum gambling game, generates a random value th
CVE-2018-17968 is a high-severity flaw (CVSS 7.5) affecting ruletkaio. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
A gambling smart contract implementation for RuletkaIo, an Ethereum gambling game, generates a random value that is predictable by an external contract call. The developer wrote a random() function that uses a block timestamp and block hash from the Ethereum blockchain. This can be predicted by writing the same random function code in an exploit contract to determine the deadSeat value.
Why this priority
- High severity
- Public exploit reference
- Remotely exploitable, no login, no user action
No fix is published yet: follow the downgrade or mitigation steps.
Risk facts
| CVSS score | 7.5 (High) |
| Attack vector | Network (remote) |
| Attack complexity | Low |
| Privileges needed | None |
| User interaction | None |
| EPSS exploit chance | 1.2% (top 32%) |
| CISA exploited list | No |
| Weakness | CWE-338 |
| Published | 2018-10-23 |
| Last modified | 2026-06-17 |
Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score
Am I affected?
Timeline
- Published CVE record published
- Updated Record last modified
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.
Quick answers
How do I fix CVE-2018-17968?
ruletkaio: mitigate or apply the listed mitigation. Exact commands for each OS are on this page.
Is CVE-2018-17968 being exploited?
CVE-2018-17968 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.
What does CVE-2018-17968 affect?
CVE-2018-17968 affects ruletkaio. Severity is high (CVSS 7.5). A gambling smart contract implementation for RuletkaIo, an Ethereum gambling game, generates a random value that is predictable by an external contract call. The developer wrote a random() function that uses a block timestamp and block hash
How urgent is CVE-2018-17968?
Priority 53/100. High severity; Public exploit reference; Remotely exploitable, no login, no user action