# CVE-2017-0147: Microsoft Windows SMBv1 Information Disclosure

> Remote attackers can obtain sensitive process memory information via crafted packets in the Windows SMBv1 server.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Yes, since 24 May 2022 (CISA KEV), used in ransomware
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Mar 2017
- **Updated:** 21 Oct 2025
- **Also known as:** GHSA-xh7q-7r6g-64g2

## What is CVE-2017-0147?

CVE-2017-0147 is a high-severity vulnerability in Microsoft Windows 10 1507, published on 17 Mar 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

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

## Which versions are affected by CVE-2017-0147?

It affects 18 products.


Products: Microsoft Windows 10 1507, Microsoft Windows 10 1511, Microsoft Windows 10 1607, Microsoft Windows 7, Microsoft Windows 8.1, Microsoft Windows Rt 8.1, Microsoft Windows Server 2008, Microsoft Windows Server 2012, Microsoft Windows Server 2016, Microsoft Windows Vista, Siemens Acuson P300 Firmware, Siemens Acuson P500 Firmware, Siemens Acuson Sc2000 Firmware, Siemens Acuson X700 Firmware, Siemens Syngo Sc2000 Firmware, Siemens Tissue Preparation System Firmware, Siemens Versant Kpcr Molecular System Firmware, Siemens Versant Kpcr Sample Prep Firmware.

## How do I fix CVE-2017-0147?

No fix has been published for CVE-2017-0147 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 14 Jun 2022.

## Is CVE-2017-0147 being exploited?

Yes. Attackers have exploited CVE-2017-0147 in the wild since at least 24 May 2022, including in ransomware campaigns.

Public exploit code:

- MS17-010 EternalRomance/EternalSynergy/EternalChampion SMB Remote Windows Command Execution (metasploit)
- MS17-010 EternalBlue SMB Remote Windows Kernel Pool Corruption (metasploit)
- MS17-010 EternalRomance/EternalSynergy/EternalChampion SMB Remote Windows Code Execution (metasploit)
- SMB DOUBLEPULSAR Remote Code Execution (metasploit)
- Microsoft Windows - SMB Remote Code Execution Scanner (MS17-010) (Metasploit) (exploitdb)
- Microsoft Windows Server 2008 R2 (x64) - 'SrvOs2FeaToNt' SMB Remote Code Execution (MS17-010) (exploitdb)

## Other vulnerabilities in Microsoft Windows 10 1507

- [CVE-2017-8543](https://insights.sbomify.com/CVE-2017-8543/): Microsoft Windows Search Remote Code Execution (critical 9.8, exploited in the wild)
- [CVE-2025-33053](https://insights.sbomify.com/CVE-2025-33053/): Microsoft Windows External Control of File Name or Path (high 8.8, exploited in the wild)
- [CVE-2025-33073](https://insights.sbomify.com/CVE-2025-33073/): Microsoft Windows SMB Client Improper Access Control (high 8.8, exploited in the wild)
- [CVE-2024-49039](https://insights.sbomify.com/CVE-2024-49039/): Microsoft Windows Task Scheduler Privilege Escalation (high 8.8, exploited in the wild)
- [CVE-2024-43461](https://insights.sbomify.com/CVE-2024-43461/): Microsoft Windows MSHTML Platform Spoofing (high 8.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-0147 and fix it if it is affected.

What it is: CVE-2017-0147 is a high-severity vulnerability in Microsoft Windows 10 1507, published on 17 Mar 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2017-0147 in the wild since at least 24 May 2022, including in ransomware campaigns.

Affected product: Microsoft Windows 10 1507. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2017-0147/ (Markdown: https://insights.sbomify.com/CVE-2017-0147/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2017-0147
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2017-0147
- OSV: https://osv.dev/vulnerability/CVE-2017-0147

---
From sbomify Insights: https://insights.sbomify.com/CVE-2017-0147/
Summaries are generated and may contain mistakes; the official description above is the record.