Skip to main content
Mallory
HighExploited in the wildCISA KEVPublic exploitVulnerability

CVE-2014-4114: Sandworm

Published Oct 15, 2014 · Updated 13 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS7.8High · v3.1
EPSS81.6%100th percentile
CISA KEVYesAdded Mar 3, 2022
In the wildActivePer CISA KEV
Vendor
Microsoft Corporation
IdentifiersCVE-2014-4114CWE-20

CVE-2014-4114, commonly known as Sandworm, is a remote code execution vulnerability in Microsoft Windows Object Linking and Embedding (OLE). A specially crafted OLE object in an Office document can cause Windows Object Packager to retrieve attacker-controlled files and invoke malicious INF installation directives. The documented execution path involves CPackage::OLE2MPlayerReadFromStream retrieving remotely referenced files and CPackage::DoVerb selecting the INF installation handler. Crafted PowerPoint presentations and slideshows can trigger this behavior when opened, executing arbitrary code with the logged-on user's privileges. Affected platforms include Windows Vista SP2, Windows 7 SP1, Windows 8 and 8.1, Windows Server 2008 SP2 and R2 SP1, Windows Server 2012 and 2012 R2, and Windows RT and RT 8.1. The vulnerability was exploited in targeted attacks during 2014, including Sandworm Team campaigns distributing BlackEnergy.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation compromises the affected system within the current user's security context. Attackers can execute malware and access, modify, or delete data available to that user. If the user has administrative privileges, exploitation can additionally permit program installation and creation of accounts with full user rights. Malicious PowerPoint Show files can initiate code installation without User Account Control prompts; this does not independently confer privileges beyond those available to the user.

Mitigation

If you can’t patch tonight, do this now.

Keep untrusted Office documents in Protected View and avoid opening unsolicited attachments or downloaded presentations. Use non-administrative accounts to limit exploitation impact. Documented workarounds include disabling the WebClient service to prevent WebDAV retrieval, blocking TCP ports 139 and 445 in both directions at the enterprise firewall to restrict SMB retrieval, and removing the INF install-verb command registration to prevent executable launches through INF installation. These workarounds can disrupt file sharing, WebDAV-dependent services, and legitimate installers; assess operational effects before deployment.

Remediation

Patch, then assume compromise.

Install the applicable Microsoft security update identified by MS14-060 / KB3000869, or a superseding update containing the fix. The update changes OLE object activation behavior. Windows RT and RT 8.1 receive the update through Windows Update and require a restart; other affected editions may require a restart. Also address CVE-2014-6352, a separately tracked bypass of the original fix, rather than treating MS14-060 alone as complete protection against related OLE exploitation.

Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Microsoft CorporationWindows 7operating_system
Microsoft CorporationWindows 8operating_system
Microsoft CorporationWindows 8.1operating_system
Microsoft CorporationWindows Rtoperating_system
Microsoft CorporationWindows Rt 8.1operating_system
Microsoft CorporationWindows Server 2008operating_system
Microsoft CorporationWindows Server 2012operating_system
Microsoft CorporationWindows Vistaoperating_system
FAQ

Frequently asked questions

Is CVE-2014-4114 exploited in the wild?
Yes. As of Nov 4, 2026, Mallory has reports of exploitation in the wild, and CISA added it to KEV on Mar 3, 2022.
Is there a public exploit for CVE-2014-4114?
Yes. Mallory tracks 1 public exploit or proof of concept for CVE-2014-4114, the earliest disclosed Oct 14, 2014.
Is there a patch for CVE-2014-4114?
Install the applicable Microsoft security update identified by MS14-060 / KB3000869, or a superseding update containing the fix. The update changes OLE object activation behavior.
What products are affected by CVE-2014-4114?
Microsoft Corporation Windows 7, Microsoft Corporation Windows 8, Microsoft Corporation Windows Rt, Microsoft Corporation Windows Server 2008, Microsoft Corporation Windows Server 2012, and 3 more.
How severe is CVE-2014-4114?
CVE-2014-4114 has a CVSS v3.1 score of 7.8 (High) and an EPSS score of 81.6% (100th percentile) as of Nov 4, 2026.
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidence20Every report linking this CVE to a named adversary.
Associated malware14Malware families linked to this CVE, with evidence and IOCs.
Detection signatures2YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity1Community discussion across Reddit, Mastodon, and other social sources.