Microsoft Windows SMBv1 Remote Information Disclosure Vulnerability (CVE-2017-0147) Security Advisory
Executive & SecOps Summary
SECOPS ASSESSMENTLegacy Windows operating systems including Windows Vista, 7, 8.1, 10, and Windows Server 2008, 2012, 2016 with SMBv1 enabled
Unauthenticated remote attackers can extract sensitive information from kernel process memory via crafted SMBv1 packets, which can be chained with tools like DOUBLEPULSAR for further compromise
Apply the MS17-010 security update immediately and completely disable the legacy SMBv1 protocol across the enterprise
Affected Products & Version Scope
Remediation & Live Workaround Commands
PATCH & WORKAROUND1. Official Patch & Version Upgrade Commands
Apply the MS17-010 cumulative security update. For legacy systems where automatic updates are disabled, verify and install the appropriate KB package.
# Check if MS17-010 related hotfixes are installed
Get-HotFix -Id KB4012212, KB4012215, KB4012598 -ErrorAction SilentlyContinue2. Temporary Workaround & Hardening Configuration
If patching cannot be immediately scheduled, disable the SMBv1 protocol entirely and block SMB traffic at the network boundary.
# Disable SMBv1 protocol via PowerShell (requires reboot)
Disable-WindowsOptionalFeature -Online -FeatureName SMB1Protocol -NoRestart
Set-ItemProperty -Path 'HKLM:\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters' -Name SMB1 -Value 0 -Force3. Log Audit & IoC Verification Commands
Audit the system to verify if SMBv1 is active and inspect network configurations to ensure port 445 is not exposed to untrusted networks.
# Audit script to check SMBv1 status
$smb1Status = Get-SmbServerConfiguration | Select-Object -ExpandProperty EnableSMB1Protocol
if ($smb1Status -eq $true) {
Write-Warning 'SMBv1 is currently ENABLED. This system is vulnerable to CVE-2017-0147.'
} else {
Write-Output 'SMBv1 is DISABLED. System is protected against SMBv1-specific exploits.'
}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.
Technical Root Cause & Exploitation Mechanics
1. Vulnerability Overview & Root Cause
This vulnerability exists in the Microsoft Windows SMBv1 (Server Message Block v1) server engine (srv.sys). The root cause is a failure of the SMBv1 server to properly validate the length and boundaries of transaction requests sent by a client. This lack of validation allows an attacker to request more data than the buffer actually contains, leading to an out-of-bounds read that leaks kernel memory space back to the requester.
2. Exploitation Mechanics & Attack Scenario
An attacker initiates the exploit by establishing an anonymous SMB connection over TCP port 445 and sending a specially crafted SMBv1 transaction request. Because the server does not validate the requested buffer size against the actual transaction data size, it copies adjacent kernel memory into the response packet. This leaked memory can contain sensitive data such as session tokens, cryptographic keys, or internal memory addresses. This specific information disclosure mechanism was heavily utilized by the 'DOUBLEPULSAR' implant to verify successful installation and bypass exploit mitigations like ASLR.
3. Infrastructure & Business Impact
Classified under CISA's Known Exploited Vulnerabilities (KEV) catalog with an EPSS score of 0.9969, this vulnerability represents an active and severe threat. If exploited, it allows attackers to perform reconnaissance within the internal network, harvest credentials from memory, and facilitate lateral movement. This can lead to full domain compromise, ransomware deployment, and catastrophic business disruption.
Official Vendor Advisories & References
The SMBv1 server in Microsoft Windows Vista SP2; Windows Server 2008 SP2 and R2 SP1; Windows 7 SP1; Windows 8.1; Windows Server 2012 Gold and R2; Windows RT 8.1; and Windows 10 Gold, 1511, and 1607; and Windows Server 2016 allows remote attackers to obtain sensitive information from process memory via a crafted packets, aka "Windows SMB Information Disclosure Vulnerability."
Frequently Asked SecOps Questions (CVE-2017-0147)
FAQQ1. How critical is CVE-2017-0147 and is it actively exploited in the wild?
CVE-2017-0147 is rated CVSS 7.5 (HIGH) with a 30-day EPSS exploitation probability of 99.7%. 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-0147?
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-0147 before patching?
[Mitigation] Apply the MS17-010 security update immediately and completely disable the legacy SMBv1 protocol across the enterprise Follow the CLI remediation commands and interactive SecOps checklist on this page to restrict exposure prior to your maintenance window.
Generate an Internal Engineering Notice or CISO Report for CVE-2017-0147
Instantly format this advisory into an executive CISO summary or engineering patch ticket.
🔗 Related Advisories in Similar Stack (microsoft)
View Category →Windows IKE Extension Double Free Remote Code Execution Vulnerability (CVE-2026-33824)
[Affected Scope] Internet Key Exchange (IKE) Extension service running on Microsoft Windows and Windows Server operating systems
Windows Remote Access Connection Manager (RasMan) Null Pointer Dereference Local DoS Vulnerability (CVE-2026-21525) Technical Advisory
[Affected Scope] Windows and Windows Server operating systems utilizing the Windows Remote Access Connection Manager (RasMan) service.
Windows ALPC Heap-Based Buffer Overflow Privilege Escalation Vulnerability (CVE-2026-85880) Security Advisory
[Affected Scope] Locally authenticated users across Microsoft Windows operating systems
Windows Update Stack Privilege Escalation Vulnerability via Link Following (CVE-2026-81963) Technical Advisory
[Affected Scope] Microsoft Windows operating systems utilizing the Windows Update Stack
Subscribe to Daily Vulnerability Briefings & KEV Alerts
Concise morning briefings for SecOps, DevSecOps, and SRE teams covering newly exploited CVEs and mitigation priorities.