CVE-2019-1125

Windows Kernel Information Disclosure Vulnerability

MEDIUM
5.6
CVSS Score
Published: September 3, 2019 at 05:52 PM UTC
Updated: June 17, 2026 at 02:27 AM UTC
24 products affected across 2 vendorsWindows Server 2016Windows Server 2019Windows Server 2012

Using Windows 10 Version 1703 by Microsoft?

Get instant alerts when new vulnerabilities affect Windows 10 Version 1703 - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM5.6
Exploit prediction
EPSS 5%

Description

An information disclosure vulnerability exists when certain central processing units (CPU) speculatively access memory. An attacker who successfully exploited the vulnerability could read privileged data across trust boundaries. To exploit this vulnerability, an attacker would have to log on to an affected system and run a specially crafted application. The vulnerability would not allow an attacker to elevate user rights directly, but it could be used to obtain information that could be used to try to compromise the affected system further. On January 3, 2018, Microsoft released an advisory and security updates related to a newly-discovered class of hardware vulnerabilities (known as Spectre) involving speculative execution side channels that affect AMD, ARM, and Intel CPUs to varying degrees. This vulnerability, released on August 6, 2019, is a variant of the Spectre Variant 1 speculative execution side channel vulnerability and has been assigned CVE-2019-1125. Microsoft released a security update on July 9, 2019 that addresses the vulnerability through a software change that mitigates how the CPU speculatively accesses memory. Note that this vulnerability does not require a microcode update from your device OEM.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

6.1.0 ≤ v < publication6.1.0sp1
Affected range stops below publication, so it looks safe — our inference, not a vendor statement
6.3.0 ≤ v < publication6.3.0
Affected range stops below publication, so it looks safe — our inference, not a vendor statement
6.0.0 ≤ v < publication6.1.0 ≤ v < publication6.0.06.1.0r2 sp1sp2
Affected range stops below publication, so it looks safe — our inference, not a vendor statement
6.2.0 ≤ v < publication6.3.0 ≤ v < publication6.2.06.3.0r2
Affected range stops below publication, so it looks safe — our inference, not a vendor statement
10.0.0 ≤ v < publication10.0.018031903
Affected range stops below publication, so it looks safe — our inference, not a vendor statement
10.0.0 ≤ v < publication10.0.0
Affected range stops below publication, so it looks safe — our inference, not a vendor statement

CVSS

5.6MEDIUMmicrosoft
Vector?

Quick Info

StatusMODIFIED
CWE
NVD-CWE-noinfo

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card