# CVE-2018-14715: The endCoinFlip function and throwSlammer function of the smart contract implementations for Cryptogs, an Ethereum game, generate random num


- **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
- **Fix available:** No
- **Published:** 3 Aug 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-p9f6-cwf6-ccqv

## What is CVE-2018-14715?

CVE-2018-14715 is a high-severity vulnerability in n/a, published on 3 Aug 2018. 

### Official description

The endCoinFlip function and throwSlammer function of the smart contract implementations for Cryptogs, an Ethereum game, generate random numbers with an old block's hash. Therefore, attackers can predict the random number and always win the game.

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

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

It affects 1 product.


Products: Cryptogs Cryptogs.

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

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

## Is CVE-2018-14715 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2018-14715 is a high-severity vulnerability in n/a, published on 3 Aug 2018. 
Exploitation: There is no known exploitation of CVE-2018-14715 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-14715/ (Markdown: https://insights.sbomify.com/CVE-2018-14715/index.md)
```

## Sources

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

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