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

> Attackers can take over contract ownership via flawed logic, allowing manipulation of digital assets in the Ether Cartel game.

- **Severity:** High 7.5 (`CVSS:3.1/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:** 22 May 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-5757-f848-8hh4

## What is CVE-2018-11329?

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

### Official description

The DrugDealer function of a smart contract implementation for Ether Cartel, an Ethereum game, allows attackers to take over the contract's ownership, aka ceoAnyone. After that, all the digital assets (including Ether balance and tokens) might be manipulated by the attackers, as exploited in the wild in May 2018.

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

It affects 1 product.


Products: Ethercartel Ether Cartel.

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

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

## Is CVE-2018-11329 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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