# CVE-2007-3670: Command injection in n/a

> Remote attackers can execute arbitrary commands via shell metacharacters in Firefox URIs when Internet Explorer invokes Firefox, requiring user interaction.

- **Severity:** Medium 4.3 (`AV:N/AC:M/Au:N/C:N/I:P/A:N`)
- **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:** Yes
- **Published:** 10 Jul 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-qwp7-hh47-5g3h

## What is CVE-2007-3670?

CVE-2007-3670 is a medium-severity command injection vulnerability in Microsoft Internet Explorer, published on 10 Jul 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

Argument injection vulnerability in Microsoft Internet Explorer, when running on systems with Firefox installed and certain URIs registered, allows remote attackers to conduct cross-browser scripting attacks and execute arbitrary commands via shell metacharacters in a (1) FirefoxURL or (2) FirefoxHTML URI, which are inserted into the command line that is created when invoking firefox.exe.  NOTE: it has been debated as to whether the issue is in Internet Explorer or Firefox. As of 20070711, it is CVE's opinion that IE appears to be failing to properly delimit the URL argument when invoking Firefox, and this issue could arise with other protocol handlers in IE as well. However, Mozilla has stated that it will address the issue with a "defense in depth" fix that will "prevent IE from sending Firefox malicious data."

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

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

It affects 2 products.


Products: Microsoft Internet Explorer, Mozilla Firefox.

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

Apply the vendor's patch.

## Is CVE-2007-3670 being exploited?

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

Public exploit code:

- Microsoft Internet Explorer and Mozilla Firefox - URI Handler Command Injection (exploitdb)

## Other vulnerabilities in Microsoft Internet Explorer

- [CVE-2014-1776](https://insights.sbomify.com/CVE-2014-1776/): Microsoft Internet Explorer Memory Corruption (critical 9.8, exploited in the wild)
- [CVE-2021-27085](https://insights.sbomify.com/CVE-2021-27085/): Microsoft Internet Explorer Remote Code Execution (high 8.8, exploited in the wild)
- [CVE-2017-0222](https://insights.sbomify.com/CVE-2017-0222/): Microsoft Internet Explorer Remote Code Execution (high 8.8, exploited in the wild)
- [CVE-2017-0210](https://insights.sbomify.com/CVE-2017-0210/): Microsoft Internet Explorer Privilege Escalation (high 8.8, exploited in the wild)
- [CVE-2017-0149](https://insights.sbomify.com/CVE-2017-0149/): Microsoft Internet Explorer Memory Corruption (high 8.8, exploited in the wild)

## Fix prompt for AI coding agents

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

What it is: CVE-2007-3670 is a medium-severity command injection vulnerability in Microsoft Internet Explorer, published on 10 Jul 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-3670 exists.

Affected product: Microsoft Internet Explorer. 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-3670/ (Markdown: https://insights.sbomify.com/CVE-2007-3670/index.md)
```

## Sources

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

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