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 27 Apr 2022. Known ransomware use
Server Message BlockApplication · Microsoft

CVE-2017-0148

HIGH · 8.1 CVSS v3.1 Published 2017-03-17
Fix available
A fix is available. Upgrade to 4.0e or later.
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 execute arbitrary code via crafted packets, aka "Windows SMB Remote Code Execution Vulnerability." This vulnerability is different from those described in CVE-2017-0143, CVE-2017-0144, CVE-2017-0145, and CVE-2017-0146.

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 a remote code execution vulnerability in the SMBv1 server implementation affecting multiple Windows versions. Attackers exploit this by sending specially crafted packets to vulnerable SMBv1 servers, allowing arbitrary code execution. This was one of the vulnerabilities in the EternalBlue exploit chain famously used by WannaCry ransomware.

MitigationApply the relevant Microsoft security patches (MS17-010) to all affected systems. As a defense-in-depth measure, disable SMBv1 protocol via Group Policy or registry if not required for business operations.

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
Server Message BlockApplication
Affected:= 1.0
Acuson P300 FirmwareOperating system
Affected:= 13.02= 13.03= 13.20= 13.21
Acuson P500 FirmwareOperating system
Affected:= va10= vb10
Acuson Sc2000 FirmwareOperating system
Affected:>= 4.0, < 4.0e= 5.0a
Acuson X700 FirmwareOperating system
Affected:= 1.0= 1.1
Syngo Sc2000 FirmwareOperating system
Affected:>= 4.0, <= 4.0e= 5.0a
Tissue Preparation System FirmwareOperating system
Affected:all versions
Versant Kpcr Molecular System FirmwareOperating system
Affected:all versions

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
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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 SMBv1 protocol status on Windows
    Run 'Get-SmbServerConfiguration | Select-Object EnableSMB1Protocol' in PowerShell, or check registry key 'HKLM\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters\SMB1' (value 0 means disabled, 1 means enabled)
    Affected if SMBv1 is enabled (value is 1 or cmdlet returns True)
  2. Confirm Windows version falls within affected range
    Run 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to identify the Windows version. Check against: Vista, Server 2008, 7/Server 2008 R2, 8.1/Server 2012 R2, 10, or Server 2016
    Affected if Windows version is Vista through Windows 10 or Server 2008 through Server 2016 AND SMBv1 is enabled
  3. Detect if SMBv1 client is installed on Windows 10/Server 2016+
    Run 'Get-WindowsOptionalFeature -Online -FeatureName SMB1Protocol' to check if the SMB1 client feature is present
    Affected if Feature state shows as Enabled or Present
  4. Identify Siemens Acuson P300 firmware version
    Access the device management interface or check system documentation for firmware version information
    Affected if Firmware version is exactly 13.02, 13.03, 13.20, or 13.21
  5. Identify Siemens medical device firmware for other affected models
    Check device system information or firmware inventory for Acuson P500, Acuson Sc2000, Acuson X700, Syngo Sc2000, Tissue Preparation System, or Versant Kpcr Molecular System
    Affected if Acuson P500: va10 or vb10; Acuson Sc2000/X700 or Syngo Sc2000: 4.0 through 4.0e or 5.0a; Tissue Preparation or Versant Kpcr: any version

A system is affected if it runs a vulnerable Windows version (Vista through 10/Server 2016) with SMBv1 protocol enabled, or if it is one of the listed Siemens medical devices with the specified firmware versions.

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
Upgrade available Upgrade to 4.0e or later
Fixed in 4.0e
Vendor patch portal.msrc.microsoft.com →
Interim mitigation

Apply the relevant Microsoft security patches (MS17-010) to all affected systems. As a defense-in-depth measure, disable SMBv1 protocol via Group Policy or registry if not required for business operations.

Recommended fix High confidence

For Windows systems: Apply MS17-010 security update (released March 2017). For medical devices: Contact vendor for specific firmware updates

  1. Apply Microsoft security update MS17-010 to patch the SMBv1 vulnerability in affected Windows systems (Vista SP2, Windows Server 2008 SP2/R2 SP1, Windows 7 SP1, Windows 8.1, Windows Server 2012 Gold/R2, Windows RT 8.1, Windows 10 Gold/1511/1607, Windows Server 2016)
  2. If patching is not immediately possible, disable SMBv1 on affected systems via: Run 'OptionalFeatures.exe', uncheck 'SMB 1.0/CIFS File Sharing Support', or via PowerShell: 'Set-SmbServerConfiguration -EnableSMB1Protocol $false'
  3. For Siemens medical devices (Acuson P300, P500, Sc2000, X700, Syngo Sc2000, Tissue Preparation System, Versant Kpcr Molecular System), contact Siemens Healthineers for device-specific firmware updates and follow their remediation guidance
  4. Implement network segmentation to isolate vulnerable medical devices from broader network until patches/updates are applied
  5. Verify SMBv1 is disabled using: 'Get-WindowsOptionalFeature -Online -FeatureName SMB1Protocol'
Caveat Disabling SMBv1 may break legacy applications or devices that require SMBv1 protocol; verify compatibility before disabling

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

Fix this in Server Message Block Exploited in the wild — priority engagement
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get it fixed fast

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-0148 — 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-0148 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