CVE DatabaseCVE-2017-0148
한국어 권고문 →
CVE-2017-01488.1/HIGHCISA KEVCWE-20CWE-20

Microsoft Windows SMBv1 Remote Code Execution Vulnerability (CVE-2017-0148) - MS17-010

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

Executive & SecOps Summary

SECOPS ASSESSMENT
Affected Scope

Legacy 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 crafted packets, leading to complete system compromise

Mitigation

Apply the MS17-010 security patch immediately 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. Verify patch installation using PowerShell:

powershell
# Check if MS17-010 related hotfixes are installed
Get-HotFix | Where-Object { $_.HotFixID -match 'KB4012212|KB4012215|KB4012598|KB4013429' }

2. Temporary Workaround & Hardening Configuration

If patching cannot be immediately applied, disable the legacy SMBv1 protocol and block external SMB traffic at the network boundary.

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

3. Log Audit & IoC Verification Commands

Scan the network to identify systems running the vulnerable SMBv1 protocol or showing signs of MS17-010 exposure.

bash
# Scan target subnet for SMBv1 protocol and MS17-010 vulnerability using Nmap
nmap -p 445 --script smb-protocols,smb-vuln-ms17-010 <Target-IP-Subnet>
Interactive SecOps Remediation Checklist
0/4 (0%)
Recommended Security Control & Mitigation Partner
SentinelOne Singularity AI EDR
Immediately disable SMBv1 globally and restrict inbound TCP port 445 traffic at the perimeter firewall to prevent remote exploitation.

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 is an input validation flaw (CWE-20) within the SMBv1 (Server Message Block v1) protocol handling engine in Microsoft Windows. The SMBv1 server fails to properly validate the size and structure of specific transaction request packets sent by a client, leading to memory corruption and buffer overflow conditions in the non-paged pool. This flaw is heavily associated with the leaked NSA exploit suite and the DOUBLEPULSAR backdoor payload.

2. Exploitation Mechanics & Attack Scenario

An attacker scans for target systems with TCP port 445 (SMB) exposed. Upon establishing a connection, the attacker forces SMBv1 negotiation and transmits specially crafted transaction packets (such as SMB_COM_TRANSACTION2). These packets manipulate parameter values to trigger a buffer overflow in the kernel's non-paged pool. This corruption allows the attacker to execute arbitrary shellcode with SYSTEM privileges, typically resulting in the injection of the memory-resident DOUBLEPULSAR backdoor.

3. Infrastructure & Business Impact

As a CISA KEV-listed vulnerability with an EPSS score exceeding 0.99, this flaw is actively exploited in the wild. Successful exploitation enables rapid lateral movement across internal networks via worm-like propagation. This poses catastrophic risks to business continuity, including widespread ransomware deployment, sensitive data exfiltration, and complete infrastructure compromise.

Official Vendor Advisories & References

Frequently Asked SecOps Questions (CVE-2017-0148)

FAQ

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

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

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

[Mitigation] Apply the MS17-010 security patch immediately 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-0148

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