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

CVE-2017-0145

HIGH · 8.8 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 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-0146, and CVE-2017-0148.

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 affecting multiple Windows versions (Vista SP2 through Windows 10/Server 2016). Attackers exploit this by sending crafted SMB packets to vulnerable systems, achieving arbitrary code execution without authentication.

MitigationDisable SMBv1 protocol on all affected systems; apply Microsoft security update MS17-010; if SMBv1 is business-critical, implement network segmentation and monitoring until replacement with SMBv2/v3 is possible.

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

CVSS:3.1/AV:N/AC:L/PR:L/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. Identify Windows version
    Run 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to determine the installed Windows version and build number.
    Affected if The version falls between Windows Vista SP2 and Windows Server 2016 inclusive (including Windows 7, 8, 8.1, 10, Server 2008 R2, Server 2012, Server 2012 R2).
  2. Confirm SMBv1 is enabled
    Run 'Get-WindowsOptionalFeature -Online -FeatureName SMB1Protocol' in PowerShell, or check registry key 'HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters' for 'SMB1' value (0 = disabled, 1 = enabled).
    Affected if SMBv1 protocol is installed and enabled (value is 1 or feature state is Enabled).
  3. Verify SMBv1 server role is active
    Run 'Get-SmbServerConfiguration | Select-Object EnableSMB1Protocol' to check if the SMBv1 server component is actively listening.
    Affected if EnableSMB1Protocol returns True, indicating the SMBv1 server is actively accepting connections.
  4. For Siemens Acuson P300 devices
    Access device management interface or run firmware version check command to identify installed firmware version.
    Affected if Firmware version equals 13.02, 13.03, 13.20, or 13.21.
  5. For Siemens Acuson P500, Sc2000, X700, or Syngo Sc2000 devices
    Access device management interface or run firmware version check command to identify installed firmware version.
    Affected if Firmware version is va10, vb10, falls between 4.0 and below 4.0e, equals 5.0a, or equals 1.0 or 1.1.

A system is affected if it runs a vulnerable Windows version (Vista SP2 through Server 2016) WITH SMBv1 protocol enabled, or if it is a Siemens device with one of the specific firmware versions listed.

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.

From vendor data
Upgrade available Upgrade to 4.0e or later
Fixed in 4.0e
Vendor patch portal.msrc.microsoft.com →
Interim mitigation

Disable SMBv1 protocol on all affected systems; apply Microsoft security update MS17-010; if SMBv1 is business-critical, implement network segmentation and monitoring until replacement with SMBv2/v3 is possible.

Fix this in Server Message Block Exploited in the wild — priority engagement
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,800
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,880.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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