CVE DatabaseCVE-2017-0146
한국어 권고문 →
CVE-2017-01468.8/HIGHCISA KEV

Microsoft Windows SMBv1 Remote Code Execution Vulnerability (CVE-2017-0146)

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

Executive & SecOps Summary

SECOPS ASSESSMENT
Affected Scope

Legacy Microsoft 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 official Microsoft security update (MS17-010) 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

Apply the MS17-010 security update provided by Microsoft. For modern Windows environments, ensure the latest cumulative updates are installed. You can verify the installation of the patch using the following PowerShell command:

powershell
# Verify if the MS17-010 patch (e.g., KB4012212 or KB4012215) is installed
Get-HotFix | Where-Object { $_.HotFixID -eq 'KB4012212' -or $_.HotFixID -eq 'KB4012215' }

2. Temporary Workaround & Hardening Configuration

If patching cannot be immediately performed, disable the legacy SMBv1 protocol and restrict network access to SMB services.

powershell
# Disable SMBv1 protocol via PowerShell (requires reboot)
Disable-WindowsOptionalFeature -Online -FeatureName SMB1Protocol -NoRestart

# Disable SMBv1 Server via Registry
Set-ItemProperty -Path 'HKLM:\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters' -Name 'SMB1' -Value 0 -Force

3. Log Audit & IoC Verification Commands

To detect vulnerable hosts or active SMBv1 usage within your network, utilize network scanning tools to audit the protocol status.

bash
# Scan target IP to check for SMBv1 protocol status and MS17-010 vulnerability exposure
nmap -p 445 --script smb-protocols,smb-vuln-ms17-010 <Target-IP>
Interactive SecOps Remediation Checklist
0/4 (0%)
Recommended Security Control & Mitigation Partner
SentinelOne Singularity AI EDR
To secure your infrastructure, completely disable SMBv1 and block inbound TCP port 445 at the network perimeter.

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 exists in the Microsoft Windows Server Message Block 1.0 (SMBv1) server implementation. The root cause is a logical flaw in how the SMBv1 server handles specific transaction requests, failing to properly validate buffer allocations and packet sizes. This validation failure leads to memory corruption in the kernel pool, allowing an attacker to trigger an out-of-bounds write or invalid pointer dereference.

2. Exploitation Mechanics & Attack Scenario

An attacker initiates the exploit by scanning for open TCP port 445 on target systems. Once identified, the attacker transmits a sequence of malformed SMBv1 transaction packets designed to groom the kernel pool memory (heap spraying). By corrupting the kernel memory structures, the attacker achieves arbitrary code execution in kernel mode, which is typically leveraged to inject in-memory payloads such as the 'DOUBLEPULSAR' backdoor without touching the disk.

3. Infrastructure & Business Impact

As a highly critical vulnerability listed in the CISA KEV catalog, CVE-2017-0146 poses an extreme risk. Successful exploitation allows lateral movement within the internal network, enabling attackers to compromise Active Directory Domain Controllers and critical servers. This vulnerability has been heavily utilized in worm-like ransomware campaigns, resulting in massive operational downtime, data exfiltration, and severe financial losses.

Official Vendor Advisories & References

Frequently Asked SecOps Questions (CVE-2017-0146)

FAQ

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

CVE-2017-0146 is rated CVSS 8.8 (HIGH) with a 30-day EPSS exploitation probability of 89.9%. 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-0146?

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-0146 before patching?

[Mitigation] Immediately apply the official Microsoft security update (MS17-010) 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-0146

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-0146 Microsoft Windows SMBv1 Remote Code Execution Vulnerability (CVE-2017-0146) (CVSS 8.8) - Patch & Workaround | CVE Pulse