CVE-2017-0145: Microsoft SMBv1 Remote Code Execution
Microsoft SMBv1 · listed in the CISA catalog of actively exploited vulnerabilities since 2022-02-10.
- CVSS v3.1 (CISA ADP)
- 8.8
- high
- EPSS (exploit probability, 30 days)
- 90%
- higher than 99.7% of all CVEs
- Added to CISA KEV
- 2022-02-10
- US federal due date 2022-08-10
- Automatable (CISA SSVC)
- no
- technical impact: total
CVE-2017-0145 explained
CVE-2017-0145 is a remote code execution vulnerability in the SMBv1 server of Microsoft Windows. Crafted packets sent to the SMBv1 server allow remote attackers to execute arbitrary code. CISA lists it as known exploited, with known use in ransomware campaigns, which makes patching a priority for any system still running SMBv1.
Impact
An attacker who can reach the SMBv1 server over the network can execute arbitrary code by sending crafted packets. The CVSS vector indicates low attack complexity, low privileges required and no user interaction. Confidentiality, integrity and availability impact are all high. CISA rates the technical impact as total, meaning full control of the affected component, but not automatable. Attackers are known to exploit it, including in ransomware campaigns.
Who is affected
The CVE record describes 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; Windows 10 Gold, 1511 and 1607. The description also names Windows Server 2016. The CVE record names no fixed version; consult the Microsoft advisory for the applicable security 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-0143, CVE-2017-0144, 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 SMBAffectedFixed in
- 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
not statedVersion statement as published by the CNA (free text).
| Product | Affected | Fixed in |
|---|---|---|
| Microsoft Corporation Windows SMBVersion statement as published by the CNA (free text). |
| not stated |
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-08-10 (passed) – a useful benchmark for everyone else, too.
What to do
- Apply the Microsoft security updates for this vulnerability on all affected Windows systems, following the vendor advisory.
- Identify systems with the SMBv1 server enabled and disable SMBv1 where it is not required.
- Block SMB traffic at network perimeters and keep SMB services off the internet.
- Check exposed and unpatched systems for signs of compromise, including ransomware activity.
- Replace Windows versions that can no longer receive security updates.
The CVE record names no fixed version. Follow the Microsoft advisory to identify the correct security update for each Windows version, as CISA's required action is to apply updates per vendor instructions. Until updates are applied, disable SMBv1 where possible and block SMB access from untrusted networks.
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-0145
- Is CVE-2017-0145 being exploited?
- Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2022-02-10 and notes known ransomware use. US federal agencies had to remediate it by 2022-08-10.
- Is this the same as CVE-2017-0143, CVE-2017-0144, CVE-2017-0146 or CVE-2017-0148?
- No. The description states that this vulnerability is different from those described in CVE-2017-0143, CVE-2017-0144, CVE-2017-0146 and CVE-2017-0148.
- What does CISA require?
- CISA's required action is to apply updates per vendor instructions. Use the Microsoft advisory to find the update for each affected Windows version.
Written with AI from the data on this page and checked against it automatically.
References
Government
Other advisories
Trackers and catalogs
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.