# CVE-2010-3970: Memory corruption in n/a

> Remote attackers can execute arbitrary code by tricking users into opening crafted documents with malicious thumbnail bitmaps in Windows Shell.

- **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:** 22 Dec 2010
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-p68f-wx5m-43gg

## What is CVE-2010-3970?

CVE-2010-3970 is a critical memory corruption vulnerability in Microsoft Windows Server 2003, published on 22 Dec 2010. 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

Stack-based buffer overflow in the CreateSizedDIBSECTION function in shimgvw.dll in the Windows Shell graphics processor (aka graphics rendering engine) in Microsoft Windows XP SP2 and SP3, Server 2003 SP2, Vista SP1 and SP2, and Server 2008 Gold and SP2 allows remote attackers to execute arbitrary code via a crafted .MIC or unspecified Office document containing a thumbnail bitmap with a negative biClrUsed value, as reported by Moti and Xu Hao, aka "Windows Shell Graphics Processing Overrun Vulnerability."

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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

It affects 4 products.


Products: Microsoft Windows Server 2003, Microsoft Windows Server 2008, Microsoft Windows Vista, Microsoft Windows Xp.

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

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

## Is CVE-2010-3970 being exploited?

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

Public exploit code:

- MS11-006 Microsoft Windows CreateSizedDIBSECTION Stack Buffer Overflow (metasploit)
- Microsoft Windows - CreateSizedDIBSECTION Stack Buffer Overflow (MS11-006) (Metasploit) (exploitdb)

## Other vulnerabilities in Microsoft Windows Server 2003

- [CVE-2011-2005](https://insights.sbomify.com/CVE-2011-2005/): Microsoft Ancillary Function Driver (afd.sys) Improper Input Validation (high 7.8, exploited in the wild)
- [CVE-2013-3863](https://insights.sbomify.com/CVE-2013-3863/): Memory corruption in n/a (critical 9.3)
- [CVE-2013-3181](https://insights.sbomify.com/CVE-2013-3181/): Memory corruption in n/a (critical 9.3)
- [CVE-2013-0077](https://insights.sbomify.com/CVE-2013-0077/): Code injection in n/a (critical 9.3)
- [CVE-2012-0009](https://insights.sbomify.com/CVE-2012-0009/): Path traversal in n/a (critical 9.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2010-3970 and fix it if it is affected.

What it is: CVE-2010-3970 is a critical memory corruption vulnerability in Microsoft Windows Server 2003, published on 22 Dec 2010. 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-2010-3970 exists.

Affected product: Microsoft Windows Server 2003. 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-3970/ (Markdown: https://insights.sbomify.com/CVE-2010-3970/index.md)
```

## Sources

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

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