dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 14 Jun 2022. Known ransomware use
Windows 10 1507Operating system · Microsoft

CVE-2017-0147

HIGH · 7.5 CVSS v3.1 Published 2017-03-17
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
100/100
Remediation priority · Urgent
In the wild Ransomware High EPSS Public exploit Remotely reachable No privileges Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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."

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

This is an information disclosure vulnerability in the SMBv1 server implementation across Windows Vista through Windows 10 and Server 2016. Remote attackers can send specially crafted packets to obtain sensitive information from process memory. It shares the same root cause (SMBv1 processing) as the famous EternalBlue vulnerabilities from the Shadow Brokers leak.

MitigationDisable SMBv1 on all affected systems via PowerShell (Set-SmbServerConfiguration -RequireSecuritySignature 1) or Group Policy, and apply the relevant Microsoft security patches. This eliminates the attack vector entirely.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Windows 10 1507Operating system
Affected:all versions
Windows 10 1511Operating system
Affected:all versions
Windows 10 1607Operating system
Affected:all versions
Windows 7Operating system
Affected:all versions
Windows 8.1Operating system
Affected:all versions
Windows Rt 8.1Operating system
Affected:all versions
Windows Server 2008Operating system
Affected:all versions= r2
Windows Server 2012Operating system
Affected:all versions= r2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify Windows version is within affected range
    Run 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to determine the installed Windows version. Check if it matches Windows 10 1507/1511/1607, Windows 7, Windows 8.1, Windows Rt 8.1, Windows Server 2008/R2, Windows Server 2012/R2, or Windows Server 2016.
    Affected if The installed Windows version matches any of the versions listed in the CVE affected products list.
  2. Confirm SMBv1 server is enabled
    Run 'Get-WindowsOptionalFeature -Online -FeatureName SMB1Protocol' in PowerShell with admin privileges, or check the registry key at 'HKLM:\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters' for 'SMB1' value (0 = disabled, 1 = enabled).
    Affected if SMBv1 protocol server support is enabled (value is 1 or feature state is Enabled).
  3. Verify SMBv1 server role is installed and running
    Run 'Get-Service -Name LanmanServer | Select-Object Status' or check if the 'Server' service (LanmanServer) is running. Also verify the SMBv1 driver is loaded via 'sc query mrxsmb10'.
    Affected if The SMBv1 server service is installed, running, or the mrxsmb10 driver is present and enabled.
  4. Check if SMB port 445 is listening
    Run 'netstat -an | findstr ":445"' or use 'Test-NetConnection -ComputerName localhost -Port 445' to verify the SMB listener is active.
    Affected if The system is listening on TCP port 445, indicating SMB server is exposed to network traffic.

The system is affected if it runs any affected Windows version AND has SMBv1 server enabled and accessible on the network.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Patch available Apply the vendor patch
Vendor patch portal.msrc.microsoft.com →
Interim mitigation

Disable SMBv1 on all affected systems via PowerShell (Set-SmbServerConfiguration -RequireSecuritySignature 1) or Group Policy, and apply the relevant Microsoft security patches. This eliminates the attack vector entirely.

Recommended fix High confidence

Microsoft security bulletin MS17-010 (KB4012212 and related patches for respective Windows versions)

  1. Apply Microsoft security update MS17-010, which addresses this vulnerability across all affected Windows versions.
  2. Alternatively, if patching is not immediately feasible, disable SMBv1 on affected systems using: Run 'OptionalFeatures.exe', uncheck 'SMB 1.0/CIFS File Sharing Support', or run 'sc.exe config lanmanworkstation depend= bowser/mrxsmb20' and restart.
  3. After disabling SMBv1, verify SMBv1 is not running by running 'Get-SmbServerConfiguration' PowerShell cmdlet and checking for 'EnableSMB1Protocol' set to false.
  4. Ensure Windows Firewall allows SMB traffic only on needed networks if SMB is still required.
Caveat Disabling SMBv1 may break compatibility with legacy systems or applications that require SMBv1; verify all dependent systems support SMBv2 or later before disabling.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Windows 10 1507 Exploited in the wild — priority engagement
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get it fixed fast

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-0147 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2017-0147 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data