# CVE-2007-2406: Null dereference in n/a

> User-assisted remote attackers can execute arbitrary code via a crafted Quartz Composer file due to an uninitialized object pointer in Mac OS X.

- **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:** A user has to click or open something
- **Fix available:** No
- **Published:** 3 Aug 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-vwxq-hvr2-6m4q

## What is CVE-2007-2406?

CVE-2007-2406 is a medium-severity vulnerability in n/a, published on 3 Aug 2007. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Quartz Composer on Apple Mac OS X 10.4.10 does not initialize a certain object pointer, which might allow user-assisted remote attackers to execute arbitrary code via a crafted Quartz Composer file.

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

It affects 1 product.


Products: Apple Quartz Composer.

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

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

## Is CVE-2007-2406 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2007-2406 is a medium-severity vulnerability in n/a, published on 3 Aug 2007. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2007-2406 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-2406/ (Markdown: https://insights.sbomify.com/CVE-2007-2406/index.md)
```

## Sources

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

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