# CVE-2008-0039: Code injection in n/a

> Remote attackers can execute arbitrary commands in Apple Mac OS X Mail via a crafted file:// URL, requiring user interaction.

- **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:** 12 Feb 2008
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-vrcf-r5fx-pg4p

## What is CVE-2008-0039?

CVE-2008-0039 is a medium-severity code injection vulnerability in n/a, published on 12 Feb 2008. 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

Unspecified vulnerability in Mail in Apple Mac OS X 10.4.11 allows remote attackers to execute arbitrary commands via a crafted file:// URL.

Weakness: CWE-94 (Improper Control of Generation of Code)

## Which versions are affected by CVE-2008-0039?

It affects 1 product.


Products: Apple Mail.

## How do I fix CVE-2008-0039?

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

## Is CVE-2008-0039 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2017-17688](https://insights.sbomify.com/CVE-2017-17688/): Information disclosure in n/a (medium 5.9)
- [CVE-2008-4491](https://insights.sbomify.com/CVE-2008-4491/): Information disclosure in n/a (medium 5.0)
- [CVE-2010-3887](https://insights.sbomify.com/CVE-2010-3887/): Security feature bypass in n/a (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2008-0039 and fix it if it is affected.

What it is: CVE-2008-0039 is a medium-severity code injection vulnerability in n/a, published on 12 Feb 2008. 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-2008-0039 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-2008-0039/ (Markdown: https://insights.sbomify.com/CVE-2008-0039/index.md)
```

## Sources

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

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