# CVE-2010-3962: Microsoft Internet Explorer Uninitialized Memory Corruption

> Remote attackers can execute arbitrary code via crafted CSS token sequences in Internet Explorer, requiring immediate patching.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Yes, since 6 Oct 2025 (CISA KEV)
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Nov 2010
- **Updated:** 22 Oct 2025
- **Also known as:** GHSA-cmh7-cfjq-p92g

## What is CVE-2010-3962?

CVE-2010-3962 is a high-severity use after free vulnerability in Microsoft Internet Explorer, published on 5 Nov 2010. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Use-after-free vulnerability in Microsoft Internet Explorer 6, 7, and 8 allows remote attackers to execute arbitrary code via vectors related to Cascading Style Sheets (CSS) token sequences and the clip attribute, aka an "invalid flag reference" issue or "Uninitialized Memory Corruption Vulnerability," as exploited in the wild in November 2010.

Weakness: CWE-416 (Use After Free)

## Which versions are affected by CVE-2010-3962?

It affects 1 product.


Products: Microsoft Internet Explorer.

## How do I fix CVE-2010-3962?

No fix has been published for CVE-2010-3962 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 27 Oct 2025.

## Is CVE-2010-3962 being exploited?

Yes. Attackers have exploited CVE-2010-3962 in the wild since at least 6 Oct 2025.

Public exploit code:

- MS10-090 Microsoft Internet Explorer CSS SetUserClip Memory Corruption (metasploit)
- Microsoft Internet Explorer - Memory Corruption (exploitdb)
- Microsoft Internet Explorer 6/7/8 - Memory Corruption (exploitdb)
- Microsoft Internet Explorer - CSS SetUserClip Memory Corruption (MS10-090) (Metasploit) (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-2010-3962 and fix it if it is affected.

What it is: CVE-2010-3962 is a high-severity use after free vulnerability in Microsoft Internet Explorer, published on 5 Nov 2010. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2010-3962 in the wild since at least 6 Oct 2025.

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

## Sources

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

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