CVE DatabaseCVE-2017-0144
한국어 권고문 →
CVE-2017-01448.8/HIGHCISA KEV

Microsoft Windows SMBv1 Remote Code Execution Vulnerability (CVE-2017-0144, EternalBlue)

⚡ Jump to Patch
Affected Vendors
microsoft
Affected Components
windows, windows_server
Published Date
2017-03-17
CVSS v3.1
8.8
HIGH
EPSS (30d)
99.2%
FIRST.org
CISA KEV
Exploited

Executive & SecOps Summary

SECOPS ASSESSMENT
Affected Scope

Legacy and modern Windows operating systems including Windows Vista, 7, 8.1, 10, and Windows Server 2008, 2012, 2016 with SMBv1 enabled.

Impact

Unauthenticated remote attackers can execute arbitrary code with SYSTEM privileges by sending specially crafted SMBv1 packets, leading to complete system compromise.

Mitigation

Immediately apply the Microsoft MS17-010 security patch and completely disable the legacy SMBv1 protocol across the enterprise network.

Affected Products & Version Scope

Windows Vista SP2, Windows 7 SP1, Windows 8.1, Windows 10 (Gold, 1511, 1607), Windows Server 2008 SP2/R2 SP1, Windows Server 2012 Gold/R2, Windows Server 2016

Remediation & Live Workaround Commands

PATCH & WORKAROUND

1. Official Patch & Version Upgrade Commands

The primary remediation is to apply the MS17-010 security update. On modern Windows systems, this is handled via Windows Update. For legacy environments, verify the patch status using the following PowerShell command:

powershell
# Check if MS17-010 related hotfixes are installed
Get-HotFix -Id KB4012212, KB4012215, KB4012598, KB4013429 -ErrorAction SilentlyContinue

2. Temporary Workaround & Hardening Configuration

If patching cannot be immediately scheduled, mitigate the risk by disabling the SMBv1 protocol entirely and blocking SMB traffic at the network boundary.

powershell
# Disable SMBv1 protocol and remove the feature via PowerShell
Disable-WindowsOptionalFeature -Online -FeatureName SMB1Protocol -NoRestart
Set-ItemProperty -Path 'HKLM:\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters' -Name SMB1 -Value 0 -Force

3. Log Audit & IoC Verification Commands

Monitor network traffic for active SMBv1 connections and audit listening ports on your servers to identify exposed SMB services.

bash
# Check for active established SMB connections (Port 445) on a gateway or host
netstat -antp | grep ':445' | grep 'ESTABLISHED'
Interactive SecOps Remediation Checklist
0/4 (0%)
Recommended Security Control & Mitigation Partner
SentinelOne Singularity AI EDR
To secure your infrastructure, immediately disable the legacy SMBv1 protocol and block inbound TCP port 445 at the perimeter firewall.

Block Kernel Privilege Escalation & Ransomware Payloads Before You Can Reboot

Protect unpatched Windows, Linux, and macOS workloads against in-memory exploitation and lateral movement with autonomous EDR.

100% MITRE ATT&CK Detection · 1-Click Rollback

Technical Root Cause & Exploitation Mechanics

1. Vulnerability Overview & Root Cause

This vulnerability (CVE-2017-0144) is a critical memory corruption (buffer overflow) vulnerability in the Microsoft Windows Server Message Block v1 (SMBv1) protocol implementation. An integer overflow occurs within the srv.sys kernel driver when processing transaction parameter sizes in incoming SMBv1 requests. This mathematical error leads to an out-of-bounds write, allowing data to overflow from a allocated non-paged pool buffer into adjacent memory regions.

2. Exploitation Mechanics & Attack Scenario

An attacker targets a system with TCP port 445 exposed. By sending a sequence of precisely crafted SMBv1 SMB_COM_TRANSACTION2 or SMB_COM_NT_TRANSACT packets, the attacker performs 'pool grooming' to arrange the kernel memory layout. Once the memory is aligned, the attacker triggers the buffer overflow to hijack the kernel execution flow, injecting and executing an in-memory payload such as the DOUBLEPULSAR backdoor. This entire process requires no authentication or user interaction.

3. Infrastructure & Business Impact

This vulnerability was famously leveraged by the 'WannaCry' and 'NotPetya' ransomware campaigns to achieve rapid self-propagation. A single compromised machine within an internal network allows attackers to automate lateral movement and privilege escalation across all vulnerable Windows hosts on the same subnet. This can result in catastrophic business disruption, widespread data encryption, and sensitive data exfiltration.

Official Vendor Advisories & References

Frequently Asked SecOps Questions (CVE-2017-0144)

FAQ

Q1. How critical is CVE-2017-0144 and is it actively exploited in the wild?

CVE-2017-0144 is rated CVSS 8.8 (HIGH) with a 30-day EPSS exploitation probability of 99.2%. It is listed in the CISA Known Exploited Vulnerabilities (KEV) catalog, requiring immediate emergency remediation.

Q2. Which vendors and products are affected by CVE-2017-0144?

Primary impacted vendors include microsoft across windows, windows_server. Scope summary: Windows Vista SP2, Windows 7 SP1, Windows 8.1, Windows 10 (Gold, 1511, 1607), Windows Server 2008 SP2/R2 SP1, Windows Server 2012 Gold/R2, Windows Server 2016

Q3. What temporary mitigations or workarounds exist for CVE-2017-0144 before patching?

[Mitigation] Immediately apply the Microsoft MS17-010 security patch and completely disable the legacy SMBv1 protocol across the enterprise network. Follow the CLI remediation commands and interactive SecOps checklist on this page to restrict exposure prior to your maintenance window.

SECOPS WORKBENCH INTEGRATION

Generate an Internal Engineering Notice or CISO Report for CVE-2017-0144

Instantly format this advisory into an executive CISO summary or engineering patch ticket.

Generate Report →

🔗 Related Advisories in Similar Stack (microsoft)

View Category →
SecOps Advisory Dispatch & RSS Feed

Subscribe to Daily Vulnerability Briefings & KEV Alerts

Concise morning briefings for SecOps, DevSecOps, and SRE teams covering newly exploited CVEs and mitigation priorities.

Slack / Teams / RSS Feed:
PatchKO
CVE-2017-0144 Microsoft Windows SMBv1 Remote Code Execution Vulnerability (CVE-2017-0144, EternalBlue) (CVSS 8.8) - Patch & Workaround | CVE Pulse