CVE-2010-3970 is a stack-based buffer overflow in the CreateSizedDIBSECTION function within shimgvw.dll, part of the Windows Shell graphics processor. The vulnerability is triggered when processing a crafted .MIC file or an Office document containing a thumbnail bitmap with a negative biClrUsed value. This flaw affects Microsoft Windows XP SP2/SP3, Server 2003 SP2, Vista SP1/SP2, and Server 2008 Gold/SP2. The vulnerability allows remote attackers to execute arbitrary code in the context of the user running the affected application.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository contains a single Metasploit module (ms11_006_createsizeddibsection.rb) that exploits a stack-based buffer overflow vulnerability (CVE-2010-3970, MS11-006) in the handling of thumbnail images within Microsoft Office documents and .MIC files on vulnerable Windows systems. The exploit works by generating a specially crafted file (default name: msf.doc) with a malformed bitmap header (specifically, a negative 'biClrUsed' value) embedded in the SummaryInformation stream of an OLE document. When a user views the folder containing this file in 'Thumbnails' view, the vulnerable code is triggered, leading to arbitrary code execution. The module supports multiple Windows targets (Windows 2000 SP0/SP4 English, Windows XP SP3 English) and includes logic for SEH and ROP-based exploitation. The payload is fully customizable using Metasploit's payload system, allowing for a variety of post-exploitation actions. The attack vector is local, as it requires the user to interact with the malicious file on their system. The only fingerprintable endpoint is the generated malicious file itself. The code is mature and weaponized, as it is part of the Metasploit framework and supports multiple payloads and targets.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
No public activity tracked yet. Mallory keeps watching.
No public activity observed for this vulnerability.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.