# CVE-2007-3150: Code injection in n/a

> Man-in-the-middle attackers can execute arbitrary programs by injecting JavaScript and redirects into Google Desktop search results, requiring user interaction.

- **Severity:** Critical 9.3 (`AV:N/AC:M/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:** 11 Jun 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-g79j-r2mj-4w72

## What is CVE-2007-3150?

CVE-2007-3150 is a critical code injection vulnerability in n/a, published on 11 Jun 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

Google Desktop allows user-assisted remote attackers to execute arbitrary programs via a man-in-the-middle attack that injects JavaScript, a www.google.com search IFRAME, and a META HTTP-EQUIV="refresh" that targets a www.google.com search for a local .exe file, which is displayed in the "results stored on your computer" portion of the search results, and when clicked invokes Google Desktop to execute this file.

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

It affects 1 product.


Products: Google Desktop.

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

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

## Is CVE-2007-3150 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2007-1085](https://insights.sbomify.com/CVE-2007-1085/): Cross-site scripting in n/a (high 7.6)

## Fix prompt for AI coding agents

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

What it is: CVE-2007-3150 is a critical code injection vulnerability in n/a, published on 11 Jun 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-3150 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-3150/ (Markdown: https://insights.sbomify.com/CVE-2007-3150/index.md)
```

## Sources

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

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