# CVE-2010-0402: Code injection in n/a

> Remote authenticated users can execute arbitrary code or cause denial of service in OpenTTD via crafted in-game commands due to improper index validation.

- **Severity:** Medium 6.5 (`AV:N/AC:L/Au:S/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 4 May 2010
- **Updated:** 16 Sep 2024
- **Also known as:** DEBIAN-CVE-2010-0402, GHSA-m5pw-gjvh-jgrh

## What is CVE-2010-0402?

CVE-2010-0402 is a medium-severity code injection vulnerability in n/a, published on 4 May 2010. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

OpenTTD before 1.0.1 does not properly validate index values of certain items, which allows remote authenticated users to cause a denial of service (daemon crash) or possibly execute arbitrary code via a crafted in-game command.

Weakness: CWE-94 (Improper Control of Generation of Code)

## Which versions are affected by CVE-2010-0402?

It affects 1 product.


Products: Openttd Openttd.

## How do I fix CVE-2010-0402?

Upgrade to a fixed version.

## Is CVE-2010-0402 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2008-3576](https://insights.sbomify.com/CVE-2008-3576/): Memory corruption in n/a (critical 10.0)
- [CVE-2008-3547](https://insights.sbomify.com/CVE-2008-3547/): Memory corruption in n/a (critical 9.0)
- [CVE-2011-3341](https://insights.sbomify.com/CVE-2011-3341/): Integer overflow in n/a (high 7.5)
- [CVE-2011-3342](https://insights.sbomify.com/CVE-2011-3342/): Memory corruption in n/a (high 7.5)
- [CVE-2005-2764](https://insights.sbomify.com/CVE-2005-2764/): Memory corruption in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2010-0402 and fix it if it is affected.

What it is: CVE-2010-0402 is a medium-severity code injection vulnerability in n/a, published on 4 May 2010. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2010-0402 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-2010-0402/ (Markdown: https://insights.sbomify.com/CVE-2010-0402/index.md)
```

## Sources

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

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