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

CVE-2017-0143

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-0144, CVE-2017-0145, 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

CVE-2017-0143 is a remote code execution vulnerability in the SMBv1 server implementation across Windows Vista through Windows Server 2016. Attackers exploit this flaw by sending specially crafted packets to vulnerable systems, potentially allowing complete system compromise without authentication. This vulnerability is part of the exploit chain that was widely used in the WannaCry ransomware attacks.

MitigationPrimary remediation involves disabling the SMBv1 protocol on affected systems (via Windows Features, Group Policy, or registry) and/or applying the relevant Microsoft security patches. Organizations should also consider blocking port 445 at network perimeters if SMB is not externally required.

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
Intellispace PortalApplication
Affected:= 7.0= 8.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

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. Verify SMBv1 is enabled on the system
    On Windows, run 'Get-WindowsOptionalFeature -Online -FeatureName SMB1Protocol' in PowerShell, or check the registry key at HKLM\SYSTEM\CurrentControlSet\Services\LanmanServer\Parameters for 'SMB1' value (1 = enabled). On affected medical devices, consult the device documentation or vendor utilities to confirm SMBv1 status.
    Affected if SMBv1 is currently enabled - this is the required condition for exploitation on all affected systems
  2. Identify the Windows version
    Run 'winver' or 'systeminfo' from command prompt, or 'Get-ComputerInfo | Select-Object WindowsProductName, WindowsVersion' in PowerShell.
    Affected if The system is running Windows Vista, Windows 7, Windows 8.1, Windows 10, Windows Server 2008, 2008 R2, 2012, 2012 R2, or Windows Server 2016 - all of which contain the vulnerable SMBv1 implementation
  3. Check Philips Intellispace Portal version
    Consult the device or installation documentation, or check the installed software version through the Windows Programs and Features control panel on the affected system.
    Affected if The installed version is exactly 7.0 or exactly 8.0
  4. Check Siemens Acuson P300 firmware version
    Access the device system information through the device console or consult Siemens service documentation for the firmware version.
    Affected if The firmware version is 13.02, 13.03, 13.20, or 13.21
  5. Check Siemens Acuson P500, Sc2000, X700 or Syngo Sc2000 firmware version
    Access the device system information through the device console or consult Siemens service documentation for the firmware version.
    Affected if For P500: version va10 or vb10; for Sc2000/X700/Syngo Sc2000: version 4.0 through 4.0d (less than 4.0e) or exactly 5.0a
  6. Check Siemens Tissue Preparation System firmware version
    Access the device system information through the device console or consult Siemens service documentation.
    Affected if Any firmware version is installed - all versions of this device are affected

The system is affected if SMBv1 is enabled AND the Windows version falls within Vista through Server 2016, OR the medical device firmware matches the specific versions listed in the affected products.

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

Primary remediation involves disabling the SMBv1 protocol on affected systems (via Windows Features, Group Policy, or registry) and/or applying the relevant Microsoft security patches. Organizations should also consider blocking port 445 at network perimeters if SMB is not externally required.

Recommended fix High confidence

Apply Microsoft MS17-010 security update (KB4012212 for March 2017 or subsequent monthly security rolls); For medical devices, upgrade to vendor-provided fixed firmware versions as specified by Siemens Healthineers/Philips

  1. For Windows systems: Apply the Microsoft MS17-010 security update (KB4012212 or later monthly rollup) to address the SMBv1 vulnerability
  2. For Intellispace Portal 7.0 and 8.0: Contact Philips for the specific firmware/software update addressing CVE-2017-0143
  3. For Acuson P300 (versions 13.02, 13.03, 13.20, 13.21): Contact Siemens Healthineers for firmware update
  4. For Acuson P500 (va10, vb10): Contact Siemens Healthineers for firmware update
  5. For Acuson Sc2000 (>=4.0, <4.0e and 5.0a): Contact Siemens Healthineers for firmware update to version 4.0e or later
  6. For Acuson X700 (1.0, 1.1): Contact Siemens Healthineers for firmware update
  7. For Syngo Sc2000 (>=4.0, <4.0e and 5.0a): Contact Siemens Healthineers for firmware update to version 4.0e or later
  8. For Tissue Preparation System (all versions): Contact Siemens Healthineers for firmware update
Caveat Ensure compatibility testing before applying updates to medical device firmware; Some legacy systems may require SMBv1 for backward compatibility with older devices

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

Fix this in Server Message Block Exploited in the wild — priority engagement
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get it fixed fast

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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