Skip to main content
Mallory
HighExploited in the wildCISA KEVPublic exploitVulnerability

CVE-2018-8174: Double Kill

Published May 9, 2018 · Updated 11 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days2 mentions · peak 2 in a dayToday
CVSS7.5High · v3.1
EPSS88.2%100th percentile
CISA KEVYesAdded Feb 15, 2022
In the wildActivePer CISA KEV
Vendor
Microsoft Corporation
IdentifiersCVE-2018-8174CWE-416

CVE-2018-8174, also known as Double Kill, is a use-after-free vulnerability in the Windows VBScript engine that enables remote code execution through Internet Explorer and applications hosting its engine. During array cleanup, a VBScript object's Class_Terminate callback can preserve a reference to an object whose memory is subsequently freed. Incorrect object-lifetime and reference-count handling leaves a dangling reference that attackers can exploit through object reuse and type confusion to obtain arbitrary memory access and execute shellcode. The vulnerable cleanup path involves VbsErase and the OLE Automation VariantClear function. Affected platforms include multiple Windows client and server releases, including Windows 7, Windows 8.1, Windows RT 8.1, Windows 10, and Windows Server versions from 2008 through 2016. The vulnerability was exploited as a zero-day in April 2018 and subsequently incorporated into multiple exploit kits.

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 allows arbitrary code execution with the permissions of the compromised user, enabling malware installation, data theft, and modification or destruction of accessible data. Administrative users expose the system to broader compromise; exploitation does not inherently grant elevated privileges. Observed campaigns used the vulnerability to deliver ransomware, downloaders, and espionage backdoors, including Magniber, Buran, Purple Fox, CobInt, and SLUB.

Mitigation

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

Disable VBScript execution in exposed Internet Explorer contexts and discontinue Internet Explorer use where feasible. Account for applications that embed the Internet Explorer engine: restricting direct browser execution alone may leave document-based attack paths available. Use intrusion prevention or virtual patching to block exploit delivery where immediate patching is not possible. Enforce least privilege and layered web, email, and endpoint protections to reduce exposure and constrain post-exploitation activity.

Remediation

Patch, then assume compromise.

Apply the Microsoft security updates addressing CVE-2018-8174, released on May 8, 2018, or applicable superseding updates for each affected Windows release. The fix modifies the OLE Automation VariantClear cleanup behavior to set the Variant type to VT_EMPTY during deallocation, preventing the demonstrated dangling-reference and object-reuse sequence.

Public exploits

Exploits

4 exploits validated by Mallory's analysis. Hidden: 1 rejected by Mallory's analysis as not a working exploit; 3 not yet analyzed, such as Exploit-DB entries.

View more in app →
CVE-2018-8174-msfThis repository contains a Metasploit module (CVE-2018-8174.rb) and a malicious RTF template (CVE-2018-8174.rtf) for exploiting CVE-2018-8174, a VBScript memory corruption vulnerability in Microsoft Office Word (32-bit). The exploit works by generating a specially crafted RTF file that, when opened in a vulnerable version of Word, causes the application to fetch and execute a malicious HTML payload containing VBScript from an attacker-controlled HTTP server. The Metasploit module allows the operator to specify the filename and URI path for the exploit delivery, and embeds a customizable payload (such as a reverse shell) into the exploit. The README provides installation instructions and notes that the exploit is most reliable with non-staged reverse shell payloads. The main attack vector is via malicious file delivery (RTF), with a secondary network component (HTTP server hosting the payload). The exploit is operational and can be used to achieve code execution on unpatched systems.0x09AL · Disclosed May 22, 2018 · Framework: metasploit · ruby · rtf · fileformat · networkOperationalCVE-2018-8174_EXPThis repository contains a Python exploit script (CVE-2018-8174.py) targeting the Microsoft Internet Explorer VBScript Engine remote code execution vulnerability (CVE-2018-8174, also known as Double Kill). The script generates a malicious RTF file and an HTML file containing shellcode that exploits the vulnerability. The attacker can specify a URL (where the HTML exploit will be hosted), an output RTF filename, and optionally an IP and port for a reverse shell payload. The README provides usage instructions, including how to host the exploit and set up a netcat listener to receive the reverse shell. The exploit is operational, allowing for customizable payload delivery and remote code execution on vulnerable Windows systems. The repository structure is simple, with one main Python exploit script and a README for instructions.Yt1g3r · Disclosed May 30, 2018 · python · networkOperationalCVE-2018-8174This repository is a proof-of-concept exploit for CVE-2018-8174, a remote code execution vulnerability in the VBScript engine as used by Internet Explorer, which can be triggered via Microsoft Word or WordPad. The repository contains four files: a LICENSE, a README.md with usage instructions, an index.html file containing obfuscated VBScript exploit code, and a Python script (msvbs.py) that generates a malicious RTF file embedding a link to the attacker's web server. The exploit works by having a victim open the crafted RTF file, which causes Word/WordPad to load the attacker's HTML (index.html) via an embedded OLE object. The VBScript in index.html exploits the vulnerability to execute shellcode, which downloads and runs Putty.exe from a remote site. The main fingerprintable endpoints are the attacker's web server URL (e.g., http://192.168.1.2:8080) and the reference to Putty.exe. The exploit is a POC and uses a static payload, but demonstrates full remote code execution capability.SyFi · Disclosed Jun 1, 2018 · python · vbscript · network · filePoCcve-2018-8174_analysisThis repository contains a detailed analysis and a proof-of-concept (POC) exploit for CVE-2018-8174, a use-after-free vulnerability in the VBScript engine of Microsoft Internet Explorer. The repository consists of a README.md with an in-depth technical write-up and a single exploit script, analysis.vbs, written in VBScript. The exploit demonstrates how to trigger the vulnerability by manipulating VBScript class objects and memory, leading to type confusion and ultimately arbitrary code execution. The script includes routines to leak memory addresses, resolve function pointers for VirtualProtect and NtContinue, and construct the necessary structures to bypass DEP and execute shellcode. The payload is a placeholder shellcode, but the exploit structure allows for arbitrary shellcode execution. The attack vector is via the browser (Internet Explorer) or any environment that executes VBScript. No network endpoints or external IPs/domains are present; the exploit is self-contained and targets the local system via browser scripting. The repository is a valuable resource for understanding the exploitation process of this vulnerability and serves as a POC for researchers and defenders.piotrflorczyk · Disclosed Jul 10, 2018 · vbscript · browserPoC
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 10 1607operating_system
Microsoft CorporationWindows 10 1703operating_system
Microsoft CorporationWindows 10 1709operating_system
Microsoft CorporationWindows 10 1803operating_system
Microsoft CorporationWindows 7operating_system
Microsoft CorporationWindows 8.1operating_system
Microsoft CorporationWindows Rt 8.1operating_system
Microsoft CorporationWindows Server 2008operating_system
Microsoft CorporationWindows Server 2012operating_system
Microsoft CorporationWindows Server 2016operating_system
FAQ

Frequently asked questions

Is CVE-2018-8174 exploited in the wild?
Yes. As of Nov 7, 2026, Mallory has reports of exploitation in the wild, and CISA added it to KEV on Feb 15, 2022.
Is there a public exploit for CVE-2018-8174?
Yes. Mallory tracks 4 public exploits or proofs of concept for CVE-2018-8174, the earliest disclosed May 22, 2018.
Is there a patch for CVE-2018-8174?
Apply the Microsoft security updates addressing CVE-2018-8174, released on May 8, 2018, or applicable superseding updates for each affected Windows release. The fix modifies the OLE Automation VariantClear cleanup behavior to set the Variant type to VT_EMPTY during deallocation, preventing the demonstrated dangling-reference and object-reuse sequence.
What products are affected by CVE-2018-8174?
Microsoft Corporation Windows 7, Microsoft Corporation Windows 8.1, Microsoft Corporation Windows Rt 8.1, Microsoft Corporation Windows 10 1607, Microsoft Corporation Windows 10 1703, and 5 more.
How severe is CVE-2018-8174?
CVE-2018-8174 has a CVSS v3.1 score of 7.5 (High) and an EPSS score of 88.2% (100th percentile) as of Nov 7, 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 evidence12Every report linking this CVE to a named adversary.
Associated malware33Malware families linked to this CVE, with evidence and IOCs.
Detection signatures5YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity3Community discussion across Reddit, Mastodon, and other social sources.