# CVE-2019-25157: Ethex Contracts Monthly Jackpot EthexJackpot.sol access control

> Attackers can bypass access controls in the EthexJackpot smart contract to perform unauthorized actions, requiring a code patch.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Dec 2023
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-cj9x-566g-2m4m

## What is CVE-2019-25157?

CVE-2019-25157 is a medium-severity missing authorization vulnerability in Ethex Contracts, published on 19 Dec 2023. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability was found in Ethex Contracts. It has been classified as critical. This affects an unknown part of the file EthexJackpot.sol of the component Monthly Jackpot Handler. The manipulation leads to improper access controls. It is possible to initiate the attack remotely. This product does not use versioning. This is why information about affected and unaffected releases are unavailable. The patch is named 6b8664b698d3d953e16c284fadc6caeb9e58e3db. It is recommended to apply a patch to fix this issue. The associated identifier of this vulnerability is VDB-248271.

Weakness: CWE-284 (Improper Access Control)

## Which versions are affected by CVE-2019-25157?

It affects 1 product.


Products: Ethex Ethex Contracts.

## How do I fix CVE-2019-25157?

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

## Is CVE-2019-25157 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-25157 and fix it if it is affected.

What it is: CVE-2019-25157 is a medium-severity missing authorization vulnerability in Ethex Contracts, published on 19 Dec 2023. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-25157 in the wild and no public exploit code.

Affected product: Ethex Contracts. 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-2019-25157/ (Markdown: https://insights.sbomify.com/CVE-2019-25157/index.md)
```

## Sources

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

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