How severe is CVE-2017-0147?

CVE-2017-0147 has a CVSS score of 7.5/10, rated HIGH. Immediate patching is strongly recommended.

Which products are affected by CVE-2017-0147?

Affected package information for CVE-2017-0147 is not yet fully mapped. Check the official advisory links for details.

How do I patch CVE-2017-0147?

Apply the microsoft windows 7 security patch or hotfix for CVE-2017-0147 on the affected version, following the vendor advisory for your exact build.

How do I detect CVE-2017-0147 across my infrastructure?

Inventory every microsoft windows 7 deployment and check each version against the affected-products list above. Because the exploit targets the running system rather than your application code, also watch for exploitation at the network and runtime layer — O3 flags the exploit behaviour from runtime telemetry and egress traffic even before a vulnerable build is confirmed.

How do I mitigate CVE-2017-0147 if there is no patch (or I can't update yet)?

Cut exposure now: restrict the management/admin interface to trusted networks, segment the device, and apply the vendor's recommended configuration mitigations and any WAF/IPS signature. O3's runtime protection blocks the exploit chain at execution, holding the line on unpatched or end-of-life systems until you can patch.

How does O3 Security protect against CVE-2017-0147?

O3 detects and blocks CVE-2017-0147 exploitation at runtime: eBPF exploit-chain detection, plus L7 egress monitoring that catches the post-exploitation callback and severs the attacker's outbound channel.

Is CVE-2017-0147 actively exploited in the wild?

Yes. There are 18 known exploit references for CVE-2017-0147, including 4 documented proof-of-concept exploits on Exploit-DB and 13 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2017-0147?

CVE-2017-0147 has an EPSS (Exploit Prediction Scoring System) score of 99.7%, placing it in the 100th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

Is CVE-2017-0147 in the CISA Known Exploited Vulnerabilities catalog?

Yes. CVE-2017-0147 (Microsoft Windows SMBv1 Information Disclosure Vulnerability) was added to CISA's Known Exploited Vulnerabilities (KEV) catalog on 2022-05-24. CISA required all US federal civilian agencies to remediate this vulnerability by 2022-06-14. The required action was: Apply updates per vendor instructions. This CVE has been used in known ransomware campaigns. Being listed in the KEV catalog is the strongest possible confirmation of active exploitation — treat this as a critical priority.

Which products and versions are affected by CVE-2017-0147?

CVE-2017-0147 affects microsoft windows 7; microsoft windows 8.1; microsoft windows 10 1507; microsoft windows 10 1511, and 14 more product(s). Check the affected-products list on this page against your deployed version to confirm exposure.

Is there exploit tooling available for CVE-2017-0147?

2 Metasploit modules reference CVE-2017-0147, which lowers the barrier to weaponization. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

When was CVE-2017-0147 published, and has it been updated?

CVE-2017-0147 was published on March 17, 2017 and was last updated on June 17, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

CISA KEV·Added 2022-05-24 — agencies required to remediate by 2022-06-14 · Ransomware

CVE-2017-0147

HIGH

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,…

Published

Mar 17, 2017

Updated

Jun 17, 2026

Affected

0 pkgs

Patched

None yet

Exploits

18 known

EPSS Exploitation Probability

via FIRST.org ↗

99.7%probability of exploitation in next 30 days

Very High Risk100th percentile0.00%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

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 obtain sensitive information from process memory via a crafted packets, aka "Windows SMB Information Disclosure Vulnerability."

Affected Products

18 products · 27 configurations

windows 7microsoft

all

windows 8.1microsoft

all

windows 10 1507microsoft

all

windows 10 1511microsoft

all

windows 10 1607microsoft

all

windows rt 8.1microsoft

all

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

EDB-41891doswindows✓ Verified

Microsoft Windows - SMB Remote Code Execution Scanner (MS17-010) (Metasploit)

by Sean Dillon · Apr 17, 2017

Exploit-DB Source

EDB-47456remotewindows✓ Verified

DOUBLEPULSAR - Payload Execution and Neutralization (Metasploit)

by Metasploit · Oct 2, 2019

Exploit-DB Source

EDB-43970remotewindows✓ Verified

Microsoft Windows - 'EternalRomance'/'EternalSynergy'/'EternalChampion' SMB Remote Code Execution (Metasploit) (MS17-010)

by Metasploit · Feb 5, 2018

Exploit-DB Source

EDB-41987remotewindows_x86-64

Microsoft Windows Server 2008 R2 (x64) - 'SrvOs2FeaToNt' SMB Remote Code Execution (MS17-010)

by Juan Sacco · May 10, 2017

Exploit-DB Source

Detection & mitigation playbook

Vendor / appliance

Detect
Inventory every microsoft windows 7 deployment and check each version against the affected-products list above. Because the exploit targets the running system rather than your application code, also watch for exploitation at the network and runtime layer — O3 flags the exploit behaviour from runtime telemetry and egress traffic even before a vulnerable build is confirmed.
Fix
Apply the microsoft windows 7 security patch or hotfix for CVE-2017-0147 on the affected version, following the vendor advisory for your exact build.
Workarounds
Cut exposure now: restrict the management/admin interface to trusted networks, segment the device, and apply the vendor's recommended configuration mitigations and any WAF/IPS signature. O3's runtime protection blocks the exploit chain at execution, holding the line on unpatched or end-of-life systems until you can patch.
How O3 protects you
O3 detects and blocks CVE-2017-0147 exploitation at runtime: eBPF exploit-chain detection, plus L7 egress monitoring that catches the post-exploitation callback and severs the attacker's outbound channel.

Tailored to CVE-2017-0147. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

O3 Security · Runtime Protection

Is CVE-2017-0147 being exploited in your environment?

O3's eBPF runtime sensors and L7 egress monitoring detect and block the CVE-2017-0147 exploit chain at execution — protecting unpatched and end-of-life systems until the vendor patch is applied.

Protect my workloads How runtime protection works

CVE-2017-0147

EPSS Exploitation Probability

Description

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

How O3 protects you

Frequently Asked Questions

Is CVE-2017-0147 being exploited in your environment?