Skip to content
Server Security Center
KEVhigh8.8 Used in ransomware campaigns

CVE-2017-0143: Microsoft Windows Server Message Block (SMBv1) Remote Code Execution

Microsoft Windows · listed in the CISA catalog of actively exploited vulnerabilities since 2021-11-03.

CVSS v3.1 (CISA ADP)
8.8
high
EPSS (exploit probability, 30 days)
93%
higher than 99.8% of all CVEs
Added to CISA KEV
2021-11-03
US federal due date 2022-05-03
Automatable (CISA SSVC)
no
technical impact: total

CVE-2017-0143 explained

CVE-2017-0143 is a remote code execution vulnerability in the SMBv1 server of Microsoft Windows. Remote attackers can execute arbitrary code by sending crafted packets. CISA lists it as known exploited, including in ransomware campaigns, so unpatched systems that run SMBv1 face serious risk.

Impact

An attacker with network access and low privileges can run arbitrary code on an affected system without any user interaction. CISA rates the technical impact as total, meaning full control of the affected component. CISA's assessment is that exploitation is not automatable. Confidentiality, integrity and availability are all highly affected. Attackers are known to exploit this vulnerability, and it has been used in ransomware campaigns.

Who is affected

The CVE record describes the affected versions in free text: 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. The description also names Windows Server 2016. The CVE record names no fixed version. Check the Microsoft advisory for the applicable updates.

Written with AI from the data on this page and checked against it automatically.

Official description

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.

CISA required action: Apply updates per vendor instructions.

CISA notes

Affected and fixed versions

From the CVE record published by the vendor or CVE numbering authority.

  • Microsoft Corporation Windows SMB
    Affected
    • 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
    Fixed in
    not stated

    Version statement as published by the CNA (free text).

How to fix it

  • The CVE record names no fixed version – check the vendor advisory and CISA's required action for updates and mitigations.
  • Vendor advisory: portal.msrc.microsoft.com/en-US/security-guidance/advisor…
  • CISA's deadline for US federal agencies: 2022-05-03 (passed) – a useful benchmark for everyone else, too.

What to do

  1. Apply Microsoft's security updates for this vulnerability on all affected Windows systems, following the vendor advisory.
  2. Prioritize internet-facing and critical servers, since attackers actively exploit this flaw, including in ransomware campaigns.
  3. Block SMB traffic at the network perimeter and restrict SMB access to trusted hosts only.
  4. Disable SMBv1 where it is not required, following Microsoft's guidance.
  5. Check systems that were left unpatched for signs of compromise.

The CVE record names no fixed version, but CISA's required action is to apply updates per vendor instructions. Consult the Microsoft advisory for the correct update for each Windows version. Until updates are installed, restrict network access to SMB, disable SMBv1 where possible, and monitor exposed systems for signs of compromise.

Written with AI from the data on this page and checked against it automatically.

CISA's assessment (SSVC)

Exploitation
Exploited in the wild
Automatable
No – each attack needs manual steps
Technical impact
Total – full control of the component or total information disclosure

Weakness: CWE-20

Questions about CVE-2017-0143

Is CVE-2017-0143 being exploited?
Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2021-11-03 and notes known use in ransomware campaigns. The US federal due date for remediation was 2022-05-03.
Is this the same as CVE-2017-0144, CVE-2017-0145, CVE-2017-0146 or CVE-2017-0148?
No. The CVE description states that this vulnerability is different from those described in CVE-2017-0144, CVE-2017-0145, CVE-2017-0146, and CVE-2017-0148.
What does CISA require for remediation?
CISA's required action is to apply updates per vendor instructions. Follow the Microsoft advisory to find and install the correct update for each affected Windows version.

Written with AI from the data on this page and checked against it automatically.

References

Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-22. Always confirm with the vendor's or distribution's advisory before patching.