# CVE-2008-2304: Memory corruption in n/a

> Buffer overflow in Apple Core Image Fun House allows attackers to execute arbitrary code or crash the application via a malicious .funhouse file.

- **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:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 14 Jul 2008
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-2wf7-rh9j-q4q3

## What is CVE-2008-2304?

CVE-2008-2304 is a medium-severity memory corruption vulnerability in n/a, published on 14 Jul 2008. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Buffer overflow in Apple Core Image Fun House 2.0 and earlier in CoreImage Examples in Xcode tools before 3.1 allows user-assisted attackers to execute arbitrary code or cause a denial of service (application crash) via a .funhouse file with a string XML element that contains many characters.

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

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

It affects 1 product.


Products: Apple Core Image Fun House.

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

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

## Is CVE-2008-2304 being exploited?

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

Public exploit code:

- Core Image Fun House 2.0 (OSX) - Arbitrary Code Execution (PoC) (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2008-2304 is a medium-severity memory corruption vulnerability in n/a, published on 14 Jul 2008. It can only be exploited from the same machine or local network, 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-2008-2304 exists.

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-2304/ (Markdown: https://insights.sbomify.com/CVE-2008-2304/index.md)
```

## Sources

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

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