# CVE-2002-2311: File upload in n/a

> Remote attackers can upload arbitrary files via specific key presses in Internet Explorer, requiring user interaction to trigger the vulnerability.

- **Severity:** Medium 6.4 (`AV:N/AC:L/Au:N/C:P/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:** No
- **Published:** 26 Oct 2007
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-5f3j-w3f6-9g93

## What is CVE-2002-2311?

CVE-2002-2311 is a medium-severity vulnerability in Microsoft Internet Explorer, published on 26 Oct 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

Microsoft Internet Explorer 6.0 and possibly others allows remote attackers to upload arbitrary file contents when users press a key corresponding to the JavaScript (1) event.ctrlKey or (2) event.shiftKey onkeydown event contained in a webpage.  NOTE: it was reported that the vendor has disputed the severity of this issue.

Weakness: CWE-264

## Which versions are affected by CVE-2002-2311?

It affects 2 products.


Products: Microsoft Internet Explorer, Opera Software Opera Web Browser.

## How do I fix CVE-2002-2311?

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

## Is CVE-2002-2311 being exploited?

There is no known exploitation of CVE-2002-2311 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-2002-2311 and fix it if it is affected.

What it is: CVE-2002-2311 is a medium-severity vulnerability in Microsoft Internet Explorer, published on 26 Oct 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-2002-2311 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-2002-2311/ (Markdown: https://insights.sbomify.com/CVE-2002-2311/index.md)
```

## Sources

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

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