CVE-2020-1237

Kernel-mode code execution via mishandled memory objects

Published Jun 9, 2020 · Updated Aug 4, 2024

Windows kernel object handling in Microsoft Windows allows local users to elevate privileges by running a crafted application. Microsoft identifies the locus only as the Windows kernel's handling of objects in memory and has not published the faulty operation or object type. Successful exploitation requires local code execution and user interaction and grants kernel-mode code execution with control over data, programs, and accounts.

CVSS severity7.8
High
EPSS probability3.16%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Windows kernel object handling in Microsoft Windows allows local users to elevate privileges by running a crafted application. Microsoft identifies the locus only as the Windows kernel's handling of objects in memory and has not published the faulty operation or object type. Successful exploitation requires local code execution and user interaction and grants kernel-mode code execution with control over data, programs, and accounts.

The record

CVE
CVE-2020-1237
Published
Jun 9, 2020
Updated
Aug 4, 2024
Vendor
Microsoft
Product
Windows 10 Version 1909
Classifications
T1068
Attack vector
local
Privileges
authenticated

Timeline

How it unfolded

  1. Jun 9, 2020CVE publishedPublication date reported by the CVE source.
  2. Aug 4, 2024Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=unspecified

What conditions does exploitation require?

Attack vectorlocal
Required privilegesauthenticated

What is affected?

Microsoft · Windows 10 Version 1909version=unspecified
Microsoft · Windows Server, version 1903 (Server Core installation)version=unspecified
Microsoft · Windowsversion=10 Version 1709 for 32-bit Systems; version=10 Version 1709 for ARM64-based Systems; version=10 Version 1709 for x64-based Systems; version=10 Version 1803 for 32-bit Systems; version=10 Version 1803 for ARM64-based Systems; version=10 Version 1803 for x64-based Systems; version=10 Version 1809 for 32-bit Systems; version=10 Version 1809 for ARM64-based Systems; version=10 Version 1809 for x64-based Systems
Microsoft · Windows 10 Version 2004version=unspecified
Microsoft · Windows Server, version 2004 (Server Core installation)version=unspecified
Microsoft · Windows Serverversion=2019; version=2019 (Core installation); version=version 1803 (Core Installation)
Microsoft · Windows Server, version 1909 (Server Core installation)version=unspecified
Microsoft · Windows 10 Version 1903version=unspecified

Published CVSS scores

7.8NIST NVDCVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
6.8NIST NVDAV:N/AC:M/Au:N/C:P/I:P/A:P

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectorlocal
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

T1068Exploitation for Privilege Escalation

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo