Loading vulnerability…
CVE-2015-0096 is an untrusted search path vulnerability in multiple Microsoft Windows versions involving Windows Explorer’s handling of crafted shortcut files. When Windows Explorer accesses the icon of a maliciously crafted LNK file, it can trigger DLL loading from the current working directory. If an attacker places a Trojanized DLL in that directory and causes the shortcut to be viewed, the operating system may load the attacker-controlled library because of unsafe DLL search path behavior. Microsoft referred to this issue as the DLL Planting Remote Code Execution Vulnerability. Although the vulnerable condition is rooted in shortcut/icon processing, exploitation requires local placement of attacker-controlled content and results in execution in the context of the affected system component, enabling privilege gain by a local user.
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 (1 hidden).
This repository contains a single Metasploit module (Ruby file) that exploits CVE-2015-0096 (MS15-020), a vulnerability in the handling of Windows shortcut (.LNK) files. The exploit abuses the way Windows loads icon resources from LNK files, allowing an attacker to execute arbitrary code by tricking the target into opening a malicious LNK file that references a DLL hosted on an attacker-controlled SMB share. The module sets up an SMB server, generates a malicious DLL containing the selected payload, and crafts a LNK file that points to the DLL via a UNC path. The attacker must deliver the LNK file to the victim, who must then open or browse to it, triggering the exploit. The code is operational and leverages Metasploit's payload generation and SMB server capabilities. The only file in the repository is the exploit module itself, written in Ruby and designed for use within the Metasploit Framework.
This repository contains a single Metasploit module (Ruby file) that exploits CVE-2015-0096 (MS15-020), a vulnerability in the handling of Windows shortcut (.LNK) files. The exploit abuses the way Windows loads icon resources from .LNK files, allowing an attacker to execute arbitrary code by tricking the target into viewing a malicious shortcut file that references a DLL on a remote (UNC) network share. The module generates both the malicious .LNK file and the corresponding DLL payload, which must be hosted on a network share accessible to the victim. When the victim browses to the location containing the .LNK file, Windows loads the DLL from the specified UNC path, resulting in code execution. The exploit targets Windows Server 2003 SP2 (with MS10-046 installed) and Windows Server 2008 SP2 (32-bit, with MS14-027 installed). The module is weaponized, allowing for customizable payloads via 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.
2 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A Microsoft Windows Shell Link vulnerability referenced as an example of malformed LNK exploit payload generation by Meterpreter.
A Windows LNK/DLL planting remote code execution vulnerability reportedly used by Brutal Kangaroo against air-gapped targets.
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.