# CVE-2018-12454: Business logic in n/a

> Attackers can predict random values in the 1000 Guess lottery contract to always win rewards, exploiting weak randomness generation.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Jun 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-5vmw-r8q3-jr3r

## What is CVE-2018-12454?

CVE-2018-12454 is a high-severity vulnerability in n/a, published on 17 Jun 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-338 (Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG))

## Which versions are affected by CVE-2018-12454?

It affects 1 product.


Products: 1000guess 1000 Guess.

## How do I fix CVE-2018-12454?

No fix has been published for CVE-2018-12454 yet. Limit exposure of the affected software until one is available.

## Is CVE-2018-12454 being exploited?

There is no known exploitation of CVE-2018-12454 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-12454 and fix it if it is affected.

What it is: CVE-2018-12454 is a high-severity vulnerability in n/a, published on 17 Jun 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-12454 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2018-12454/ (Markdown: https://insights.sbomify.com/CVE-2018-12454/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2018-12454
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2018-12454
- OSV: https://osv.dev/vulnerability/CVE-2018-12454

---
From sbomify Insights: https://insights.sbomify.com/CVE-2018-12454/
Summaries are generated and may contain mistakes; the official description above is the record.