# CVE-2012-0065: Memory corruption in n/a

> A heap-based buffer overflow in usbmuxd allows physically proximate attackers to execute arbitrary code via a malicious USB device.

- **Severity:** Medium 4.6 (`AV:L/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 6 Oct 2012
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2012-0065, GHSA-vqcg-7gjc-556x

## What is CVE-2012-0065?

CVE-2012-0065 is a medium-severity memory corruption vulnerability in n/a, published on 6 Oct 2012. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Heap-based buffer overflow in the receive_packet function in libusbmuxd/libusbmuxd.c in usbmuxd 1.0.5 through 1.0.7 allows physically proximate attackers to execute arbitrary code via a long SerialNumber field in a property list.

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

## Which versions are affected by CVE-2012-0065?

It affects 1 product.


Products: Nikias Bassen Usbmuxd.

## How do I fix CVE-2012-0065?

Upgrade to a fixed version.

## Is CVE-2012-0065 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2012-0065 and fix it if it is affected.

What it is: CVE-2012-0065 is a medium-severity memory corruption vulnerability in n/a, published on 6 Oct 2012. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2012-0065 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-2012-0065/ (Markdown: https://insights.sbomify.com/CVE-2012-0065/index.md)
```

## Sources

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

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