CVE-2010-2568 is a remote code execution vulnerability in the Windows Shell shortcut handling logic on Microsoft Windows XP SP3, Windows Server 2003 SP2, Windows Vista SP1 and SP2, Windows Server 2008 SP2 and R2, and Windows 7. The flaw is triggered when Windows Explorer improperly handles crafted .LNK or .PIF shortcut files during icon display. Because the vulnerable code path is reached while rendering the shortcut’s icon, code execution can occur without the victim explicitly opening the shortcut target. The issue became widely known as the Stuxnet LNK exploit and was observed exploited in the wild in 2010, including in malware operations targeting Siemens WinCC-related environments.
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.
2 valid exploits after Mallory filtered fakes, detection scripts, and README-only repos (2 hidden).
This repository contains a single Metasploit module: 'ms10_046_shortcut_icon_dllloader.rb', which exploits the Microsoft Windows Shell LNK code execution vulnerability (CVE-2010-2568, also known as MS10-046). The module acts as an HTTP/WebDAV server, generating and serving malicious LNK (shortcut) files and DLL payloads. When a vulnerable Windows system accesses the LNK file (typically via a network share or WebDAV), the LNK's icon resource points to a remote DLL, which is then loaded and executed by the Windows Shell, resulting in arbitrary code execution. The module is highly weaponized, allowing the attacker to select any Metasploit payload to be delivered as a DLL. The main attack vector is network-based, requiring the victim to access a malicious LNK file hosted by the attacker. The module exposes fingerprintable endpoints such as HTTP URLs for the LNK and DLL files, and UNC paths used in the LNK file. The code is written in Ruby and is structured as a standard Metasploit exploit module.
This repository contains a single Metasploit module: 'ms10_046_shortcut_icon_dllloader.rb', which exploits the Windows Shell LNK code execution vulnerability (CVE-2010-2568, MS10-046). The exploit works by generating a malicious .LNK (shortcut) file that references an icon resource pointing to a DLL file hosted on an SMB share controlled by the attacker. When the victim browses to or opens the LNK file, Windows loads the icon from the SMB share, causing the malicious DLL to be executed. The module sets up an SMB server to host the payload DLL and creates the LNK file, which must be delivered to the target (e.g., via USB, network share, or email). The exploit is weaponized, allowing for arbitrary code execution on vulnerable Windows systems. The only file in the repository is a Ruby script designed for use within the Metasploit framework.
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.
18 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A Windows LNK shortcut handling vulnerability used by Stuxnet to trigger execution from a USB device via a malicious .lnk file.
A critical Windows LNK handling vulnerability abused by Stuxnet, allowing specially crafted shortcut files to trigger arbitrary DLL loading without the user opening the file.
A Windows Shell remote code execution vulnerability in the handling of crafted .LNK and .PIF shortcut files during icon display in Windows Explorer. It is significant because it was exploited in the wild and associated with attacks involving Siemens WinCC SCADA environments.
A Windows LNK handling vulnerability abused by exploit-based malicious shortcut files; the content describes it as the most common vulnerability targeted by corrupted LNK binaries designed to exploit Windows when a folder containing the LNK is opened.
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.