# CVE-2007-2175: Memory corruption in n/a

> Remote attackers can execute arbitrary code via memory corruption in QuickTime Java extensions when Java is enabled in browsers.

- **Severity:** High 7.6 (`AV:N/AC:H/Au:N/C:C/I:C/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:** 24 Apr 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-v58r-vg3c-hjmm

## What is CVE-2007-2175?

CVE-2007-2175 is a high-severity memory corruption vulnerability in Apple Safari, published on 24 Apr 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

Apple QuickTime Java extensions (QTJava.dll), as used in Safari and other browsers, and when Java is enabled, allows remote attackers to execute arbitrary code via parameters to the toQTPointer method in quicktime.util.QTHandleRef, which can be used to modify arbitrary memory when creating QTPointerRef objects, as demonstrated during the "PWN 2 0WN" contest at CanSecWest 2007.

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

It affects 1 product.


Products: Apple Safari.

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

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

## Is CVE-2007-2175 being exploited?

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

Public exploit code:

- Apple QuickTime 7.1.5 - QTJava toQTPointer() Java Handling Arbitrary Code Execution (exploitdb)
- Apple QuickTime for Java 7 - Memory Access (Metasploit) (exploitdb)
- Apple QTJava toQTPointer() Arbitrary Memory Access (metasploit)
- Apple QTJava - 'toQTPointer()' Arbitrary Memory Access (Metasploit) (exploitdb)

## Other vulnerabilities in Apple Safari

- [CVE-2015-5780](https://insights.sbomify.com/CVE-2015-5780/): Security feature bypass in n/a (critical 10.0)
- [CVE-2014-1300](https://insights.sbomify.com/CVE-2014-1300/): Code injection in n/a (critical 10.0)
- [CVE-2014-1303](https://insights.sbomify.com/CVE-2014-1303/): Memory corruption in n/a (critical 10.0)
- [CVE-2010-1120](https://insights.sbomify.com/CVE-2010-1120/): Code injection in n/a (critical 10.0)
- [CVE-2009-0137](https://insights.sbomify.com/CVE-2009-0137/): Cross-site scripting in n/a (critical 10.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2007-2175 is a high-severity memory corruption vulnerability in Apple Safari, published on 24 Apr 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-2175 exists.

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

## Sources

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

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