# CVE-2005-3065: Denial of service in n/a

> Remote attackers can crash the Multi Theft Auto server by sending a crafted command that triggers an out-of-bounds read.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:N/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Sep 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-2fj8-grv4-35fw

## What is CVE-2005-3065?

CVE-2005-3065 is a medium-severity denial of service vulnerability in n/a, published on 27 Sep 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

MultiTheftAuto 0.5 patch 1 and earlier allows remote attackers to cause a denial of service (application crash) via a crafted command 40 that causes a -1 length to be used and triggers an out-of-bounds read.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2005-3065?

It affects 1 product.


Products: Multitheftauto Multitheftauto.

## How do I fix CVE-2005-3065?

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

## Is CVE-2005-3065 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2005-3064](https://insights.sbomify.com/CVE-2005-3064/): Missing authorization in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2005-3065 and fix it if it is affected.

What it is: CVE-2005-3065 is a medium-severity denial of service vulnerability in n/a, published on 27 Sep 2005. 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-2005-3065 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-2005-3065/ (Markdown: https://insights.sbomify.com/CVE-2005-3065/index.md)
```

## Sources

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

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