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

> An attacker can manipulate prize distribution in HashHeroes Tiles by exploiting predictable randomness in the smart contract's winner determination logic.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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:** 26 Dec 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-23fj-gx6v-3x6c

## What is CVE-2018-17987?

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

### Official description

The determineWinner function of a smart contract implementation for HashHeroes Tiles, an Ethereum game, uses a certain blockhash value in an attempt to generate a random number for the case where NUM_TILES equals the number of people who purchased a tile, which allows an attacker to control the awarding of the prize by being the last person to purchase a tile.

Weakness: CWE-330 (Use of Insufficiently Random Values)

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

It affects 1 product.


Products: Hashheroes Hashheroes.

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

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

## Is CVE-2018-17987 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2018-17987 is a high-severity vulnerability in n/a, published on 26 Dec 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-17987 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-17987/ (Markdown: https://insights.sbomify.com/CVE-2018-17987/index.md)
```

## Sources

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

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