Windows 10 Version 1507 vulnerability

An elevation of privilege vulnerability exists in Windows when the Windows kernel-mode driver fails to properly handle objects in memory. An attacker who successfully exploited this vulnerability could run arbitrary code in kernel mode. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. To exploit this vulnerability, an attacker would first have to log on to the system. An attacker could then run a specially crafted application that could exploit the vulnerability and take control of an affected system. The update addresses this vulnerability by correcting how the Windows kernel-mode driver handles objects in memory.

Published 21 May 2020Updated 7 Oct 202690 sources
CVSS 7.0 ✓ VERIFIED REFERENCE△ CISA KEV

What happened

An elevation of privilege vulnerability exists in Windows when the Windows kernel-mode driver fails to properly handle objects in memory. An attacker who successfully exploited this vulnerability could run arbitrary code in kernel mode. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. To exploit this vulnerability, an attacker would first have to log on to the system. An attacker could then run a specially crafted application that could exploit the vulnerability and take control of an affected system. The update addresses this vulnerability by correcting how the Windows kernel-mode driver handles objects in memory.

Affected versions

Windows 10 Version 1507: 10.0.10240.0 through before publication (custom); 10.0.14393.0 through before publication (custom); 10.0.0 through before publication (custom); 10.0.17763.0 through before publication (custom); 6.1.0 through before publication (custom); 6.3.0 through before publication (custom); 6.1.7601.0 through before publication (custom); 6.0.6003.0 through before publication (custom); 6.2.9200.0 through before publication (custom); 6.3.9600.0 through before publication (custom) Fixed: See vendor advisory.

Why it matters

Review the vendor advisory and exposure of the affected product to determine operational impact.

Detection & mitigation

  • Apply vendor-provided updates or mitigations.
  • Review affected product exposure and access logs.

Public PoC references