# CVE-2007-3745: Use after free in n/a

> Remote attackers can execute arbitrary code on Mac OS X via an unsafe CoreAudio Java interface allowing arbitrary memory freeing.

- **Severity:** Medium 6.8 (`AV:N/AC:M/Au:N/C:P/I:P/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:** 3 Aug 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-p36c-8r99-rg84

## What is CVE-2007-3745?

CVE-2007-3745 is a medium-severity use after free vulnerability in n/a, published on 3 Aug 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Java interface to CoreAudio on Apple Mac OS X 10.3.9 and 10.4.10 contains an unsafe interface that is exposed by JDirect, which allows remote attackers to free arbitrary memory and thereby execute arbitrary code.

## Which versions are affected by CVE-2007-3745?

It affects 1 product.


Products: Apple Core Audio Technologies.

## How do I fix CVE-2007-3745?

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

## Is CVE-2007-3745 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2007-3745 and fix it if it is affected.

What it is: CVE-2007-3745 is a medium-severity use after free vulnerability in n/a, published on 3 Aug 2007. 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-2007-3745 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-2007-3745/ (Markdown: https://insights.sbomify.com/CVE-2007-3745/index.md)
```

## Sources

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

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