# CVE-2017-0146: Microsoft Windows SMB Remote Code Execution

> Remote attackers can execute arbitrary code on Windows systems by sending crafted packets to the SMBv1 server.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Yes, since 25 Mar 2022 (CISA KEV), used in ransomware
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Mar 2017
- **Updated:** 21 Oct 2025
- **Also known as:** GHSA-3c3r-82gp-wc94

## What is CVE-2017-0146?

CVE-2017-0146 is a high-severity memory corruption vulnerability in Microsoft Corporation Windows SMB, published on 17 Mar 2017. Any signed-in user can exploit it over the network, 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 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-0148.

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

It affects 9 products.


Products: Microsoft Server Message Block, 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-0146?

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

## Is CVE-2017-0146 being exploited?

Yes. Attackers have exploited CVE-2017-0146 in the wild since at least 25 Mar 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 Corporation Windows SMB

- [CVE-2017-0143](https://insights.sbomify.com/CVE-2017-0143/): Microsoft Windows Server Message Block (SMBv1) Remote Code Execution (high 8.8, exploited in the wild)
- [CVE-2017-0144](https://insights.sbomify.com/CVE-2017-0144/): Microsoft SMBv1 Remote Code Execution (high 8.8, exploited in the wild)
- [CVE-2017-0145](https://insights.sbomify.com/CVE-2017-0145/): Microsoft SMBv1 Remote Code Execution (high 8.8, exploited in the wild)
- [CVE-2017-0148](https://insights.sbomify.com/CVE-2017-0148/): Microsoft SMBv1 Server Remote Code Execution (high 8.1, exploited in the wild)

## Fix prompt for AI coding agents

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

What it is: CVE-2017-0146 is a high-severity memory corruption vulnerability in Microsoft Corporation Windows SMB, published on 17 Mar 2017. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2017-0146 in the wild since at least 25 Mar 2022, including in ransomware campaigns.

Affected product: Microsoft Corporation Windows SMB. 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-0146/ (Markdown: https://insights.sbomify.com/CVE-2017-0146/index.md)
```

## Sources

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

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