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

> Remote attackers can execute arbitrary commands via argument injection in Internet Explorer when invoking Netscape, requiring specific system configurations.

- **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:** 21 Jul 2007
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-mx2j-qfcf-xcrp

## What is CVE-2007-3924?

CVE-2007-3924 is a critical command injection vulnerability in Microsoft Internet Explorer, published on 21 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 Netscape installed and certain URIs registered, allows remote attackers to conduct cross-browser scripting attacks and execute arbitrary commands via shell metacharacters in a -chrome argument to the navigatorurl URI, which are inserted into the command line that is created when invoking netscape.exe, a related issue to CVE-2007-3670.  NOTE: there has been debate about whether the issue is in Internet Explorer or Netscape. As of 20070713, it is CVE's opinion that IE appears to not properly delimit the URL argument when invoking Netscape; this issue could arise with other protocol handlers in IE.

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

It affects 2 products.


Products: Microsoft Internet Explorer, Netscape Navigator.

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

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

## Is CVE-2007-3924 being exploited?

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

## 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-3924 and fix it if it is affected.

What it is: CVE-2007-3924 is a critical command injection vulnerability in Microsoft Internet Explorer, published on 21 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: There is no known exploitation of CVE-2007-3924 in the wild and no public exploit code.

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

## Sources

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

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