CVE-2015-6128 is a DLL side loading vulnerability in multiple Windows components, including the Shutdown UX DLL (Authentication UI Shutdown Choices object) and the Event Viewer Snapin. The vulnerability arises from improper handling of library loading when instantiating certain OLE/COM objects via their CLSIDs. Specifically, Windows attempts to load specific DLLs (e.g., wuaext.dll, elsext.dll) from the current working directory, allowing an attacker to execute arbitrary code by placing a malicious DLL alongside a specially crafted Office document. When the document is opened, the malicious DLL is loaded and executed with the privileges of the user. The vulnerability affects Windows Vista SP2, Windows Server 2008 SP2/R2 SP1, Windows 7 SP1, and was also verified on Windows 10 with Office 2016 64-bit. The issue is central to the way OLE technology handles embedded objects and their associated DLLs.
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 (1 hidden).
This repository contains a single Metasploit module: 'office_ole_multiple_dll_hijack.rb', which exploits multiple DLL side-loading vulnerabilities in Microsoft Office OLE objects on Windows systems. The exploit works by generating a specially crafted Office document (such as a PowerPoint .ppsx file) that embeds a vulnerable OLE object. When the victim opens this document from a directory containing a malicious DLL (named according to the targeted component, e.g., mqrt.dll, spframe.dll, wuaext.dll, phoneinfo.dll), Windows will load the attacker's DLL, resulting in arbitrary code execution with the user's privileges. The module supports multiple targets, including various Office and Windows versions, and references several CVEs and Microsoft security bulletins. The default payload launches calc.exe, but any Metasploit payload can be used. The structure is typical for a Metasploit exploit: it defines targets, payload options, and methods for generating the malicious document and embedding the OLE object. The attack vector is local, requiring the victim to open the document from a directory containing the attacker's DLL. No network endpoints are involved; the main fingerprintable elements are the DLL filenames and the crafted Office document.
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.