# CVE-2007-0646: Other in n/a

> Remote attackers can cause a denial of service in Mac OS X via format string specifiers in filenames, requiring user interaction.

- **Severity:** High 7.1 (`AV:N/AC:M/Au:N/C:N/I:N/A:C`)
- **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:** 1 Feb 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-39c6-rp26-j8w8

## What is CVE-2007-0646?

CVE-2007-0646 is a high-severity vulnerability in Apple Mac Os X, published on 1 Feb 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

Format string vulnerability in iMovie HD 6.0.3, and Safari in Apple Mac OS X 10.4 through 10.4.10, allows remote user-assisted attackers to cause a denial of service (crash) via format string specifiers in a filename, which is not properly handled when calling the NSRunCriticalAlertPanel Apple AppKit function.

Weakness: CWE-134 (Use of Externally-Controlled Format String)

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

It affects 3 products.


Products: Apple Imovie, Apple Mac Os X, Apple Safari.

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

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

## Is CVE-2007-0646 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2007-0646 exists.

Public exploit code:

- Apple Mac OSX 10.4.x - iMovie HD '.imovieproj' Filename Format String (exploitdb)

## Other vulnerabilities in Apple Mac Os X

- [CVE-2021-30757](https://insights.sbomify.com/CVE-2021-30757/): Security feature bypass in iMovie (medium 5.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2007-0646 is a high-severity vulnerability in Apple Mac Os X, published on 1 Feb 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2007-0646 exists.

Affected product: Apple Mac Os X. 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-0646/ (Markdown: https://insights.sbomify.com/CVE-2007-0646/index.md)
```

## Sources

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

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