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

CVE-2017-0148: Microsoft SMBv1 Server Remote Code Execution

Microsoft SMBv1 server · listed in the CISA catalog of actively exploited vulnerabilities since 2022-04-06.

CVSS v3.1 (CISA ADP)
8.1
high
EPSS (exploit probability, 30 days)
99.3%
among the highest 0.1% of all CVEs
Added to CISA KEV
2022-04-06
US federal due date 2022-04-27
Automatable (CISA SSVC)
no
technical impact: total

CVE-2017-0148 explained

CVE-2017-0148 is a remote code execution vulnerability in the SMBv1 server component of multiple Microsoft Windows client and server versions. Crafted packets sent to the SMBv1 server can let a remote, unauthenticated attacker run arbitrary code. CISA lists it as known exploited, including in ransomware campaigns, so unpatched systems are at serious risk.

Impact

A remote attacker with network access to the SMBv1 server can execute arbitrary code without credentials or user interaction. Successful exploitation compromises confidentiality, integrity and availability. CISA rates the technical impact as total, meaning full control of the affected component. Attack complexity is high and CISA does not consider it automatable. Attackers are nevertheless known to exploit it, and CISA reports known ransomware use.

Who is affected

The CVE record describes affected versions in free text. It names 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 lists Windows Server 2016. The CVE record names no fixed version; consult 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-0143, CVE-2017-0144, CVE-2017-0145, and CVE-2017-0146.

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-04-27 (passed) – a useful benchmark for everyone else, too.

What to do

  1. Apply the Microsoft security updates for this vulnerability on all affected Windows systems, following the vendor advisory.
  2. Prioritize internet-facing and critical servers, as CISA lists this CVE as known exploited with ransomware use.
  3. Block SMB traffic from the internet and restrict SMB access between network segments to systems that need it.
  4. Disable SMBv1 where it is not required, per vendor guidance.
  5. Check systems for signs of compromise, especially any that were unpatched and exposed to untrusted networks.

The CVE record names no fixed version. Follow the Microsoft advisory for the correct update for each Windows version, as CISA's required action is to apply updates per vendor instructions. Until updates are installed, block SMB from untrusted networks and limit SMBv1 exposure.

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 Improper Input Validation

Questions about CVE-2017-0148

Is CVE-2017-0148 being exploited?
Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2022-04-06 and reports known ransomware use. US federal agencies had a remediation due date of 2022-04-27.
Does an attacker need credentials or user interaction?
No. The attacker needs network access to the SMBv1 server but no privileges and no user interaction. Attack complexity is rated high.
Is this the same as CVE-2017-0143 to CVE-2017-0146?
No. The description states this vulnerability is different from those described in CVE-2017-0143, CVE-2017-0144, CVE-2017-0145, and CVE-2017-0146.

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.