← Back to KEV catalog

CVE-2017-0143

Exploitation: active CVSS 8.8 HIGH Ransomware: known use

CVSS base score: 8.8 (High) CISA · v3.1

Score assigned by CISA's Vulnrichment program; the vendor's CVE record did not include one. Vulnrichment source record →

Microsoft Windows Server Message Block (SMBv1) Remote Code Execution Vulnerability

Vendor: Microsoft   Product: Windows

Description

Microsoft Windows Server Message Block 1.0 (SMBv1) contains an unspecified vulnerability that allows for remote code execution.

Research & News Coverage

No mentions found in monitored research blogs or news feeds.

Referenced in Advisories

DateAdvisoryIssuer
2025-02-19 #StopRansomware: Ghost (Cring) Ransomware CISA
2025-02-19 #StopRansomware: Ghost (Cring) Ransomware FBI

Lifecycle Timeline

Each milestone comes from a different source, so gaps between them are gaps in what those sources publish, not evidence that nothing happened. EPSS history for this CVE holds 306 points from 2021-12-11, tracked daily from 2026-09-09; earlier points are weekly, which dates a spike to within a week. Peak probability 97.4% on 2023-03-11.

Published Applicability

CVE List v5 (CNA container) 1 affected · 0 fixed · 0 not affected

Check whether a specific version is affected →

What each source publishes about which product versions carry this vulnerability, kept as written rather than merged. Absence here means no source has published applicability data, not that nothing is affected.

Detection & Exploitation

Network IDS/IPS
Host / SIEM
none published

Coverage across public collections only: Nuclei and OpenVAS NVT (scan); Snort and Suricata ET Open (network); Sigma and YARA (host/SIEM); Metasploit, Exploit-DB, public GitHub repositories and NVD exploit references (exploit). Absence here means nothing public was found, not that detection is impossible.
GitHub PoC repositories are collected automatically by PoC-in-GitHub (CC0) and filtered to repositories that are still online, contain code, and are starred or at least two weeks old. They are still not vetted: some are fakes and some are malware. Treat them as evidence that code was published, not as code to run.
NVD exploit references are links NVD's analysts tag as exploits; they confirm an exploit was referenced but carry no date. This product uses data from the NVD but is not endorsed or certified by the NVD.
OpenVAS coverage derives from the Greenbone Community Feed, made available under the Open Database License (ODbL) v1.0; its individual Vulnerability Tests are licensed GNU GPL v2.

First seenToolEvidenceEarliest reference
2017-03-29 Metasploit Direct — curated exploit code MS17-010 SMB RCE Detection +4 more
2017-04-17 Exploit-DB Direct — curated exploit code Microsoft Windows - SMB Remote Code Execution Scanner (MS17-010) (Metasploit) +3 more
2017-05-16 GitHub PoC Unvetted — public repository valarauco/wannafind +4 more

Metasploit is dated by the first commit of the module file, Exploit-DB by its publication date, and GitHub repositories by their creation date. GitHub PoC repositories are filtered (still online, contain code, starred or at least two weeks old) but not vetted: some are fakes and some are malware, so they show that code was published, not that it works or is safe to run. Evidence tiers are explained on the About page.

Microsoft Assessment

published by the affected vendor via MSRC

Windows SMB Remote Code Execution Vulnerability

Exploitation More Likely
No
No
—
Remote Code Execution
Windows SMB Server
2017-03-14

The vendor's own judgement about their own code, shown alongside CISA's rather than merged into it. The exploitability index is a forward-looking prediction, distinct from a CVSS severity or CISA's SSVC decision, and vendors often report observed exploitation before a CVE reaches the KEV catalog. Vendor advisory →

CISA Assessment (Vulnrichment / SSVC)

active
no
total
8.8 HIGH
—
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
2025-02-10

Federal Remediation Window (BOD 26-04)

Yes — added 2021-11-03
no
total control
If the asset isRemediate withinTable 1 row
Publicly exposed 3 days + forensic triage 3 of 16
Not publicly exposed 14 days 11 of 16

BOD 26-04 replaced the single KEV deadline of BOD 22-01 with four inputs: whether the asset is publicly exposed, KEV status, whether exploitation is automatable, and technical impact. Exposure belongs to each agency's asset, not to the CVE, so both outcomes are shown. Automatable and technical impact come from the CISA assessment above. Days are calendar days; for KEV entries the clock starts on the date it was added. Agencies make the final exposure call asset by asset, and may set shorter timelines.

External References