CVE-2019-1125
CVE-2019-1125 · Windows Kernel Information Disclosure Vulnerability
This page contains facts from public vulnerability sources. Check the original advisory before updating.
This page shows selected source facts. See the linked advisories for the complete description and affected versions.
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.
CVSS 5.6 · Medium · EPSS 4.5% · Public exploit · Fix available
- Published
- Updated
Stack: system
Affected products and versions
windows 10 version 1703
- Versions
- ≥ 10.0.0, < publication: Affected (custom)
No fix published
windows 10 version 1803
- Versions
- ≥ 10.0.0, < publication: Affected (custom)
No fix published
windows server, version 1803 (server core installation)
- Versions
- ≥ 10.0.0, < publication: Affected (custom)
No fix published
windows 10 version 1809
- Versions
- ≥ 10.0.0, < publication: Affected (custom)
No fix published
windows server 2019
- Versions
- ≥ 10.0.0, < publication: Affected (custom)
No fix published
windows server 2019 (server core installation)
- Versions
- ≥ 10.0.0, < publication: Affected (custom)
No fix published
windows 10 version 1709 for 32-bit systems
- Versions
- ≥ 10.0.0, < publication: Affected (custom)
No fix published
windows 10 version 1709
- Versions
- ≥ 10.0.0, < publication: Affected (custom)
No fix published
windows 10 version 1903 for 32-bit systems
- Versions
- ≥ 10.0.0, < publication: Affected (custom)
No fix published
windows 10 version 1903 for x64-based systems
- Versions
- ≥ 10.0.0, < publication: Affected (custom)
No fix published
windows 10 version 1903 for arm64-based systems
- Versions
- ≥ 10.0.0, < publication: Affected (custom)
No fix published
windows server, version 1903 (server core installation)
- Versions
- ≥ 10.0.0, < publication: Affected (custom)
No fix published
windows 10 version 1507
- Versions
- ≥ 10.0.0, < publication: Affected (custom)
No fix published
windows 10 version 1607
- Versions
- ≥ 10.0.0, < publication: Affected (custom)
No fix published
windows server 2016
- Versions
- ≥ 10.0.0, < publication: Affected (custom)
No fix published
windows server 2016 (server core installation)
- Versions
- ≥ 10.0.0, < publication: Affected (custom)
No fix published
windows 7
- Versions
- ≥ 6.1.0, < publication: Affected (custom)
No fix published
windows 7 service pack 1
- Versions
- ≥ 6.1.0, < publication: Affected (custom)
No fix published
windows 8.1
- Versions
- ≥ 6.3.0, < publication: Affected (custom)
No fix published
windows server 2008 service pack 2
- Versions
- ≥ 6.0.0, < publication: Affected (custom)
No fix published
windows server 2008 service pack 2 (server core installation)
- Versions
- ≥ 6.0.0, < publication: Affected (custom)
No fix published
windows server 2008 service pack 2
- Versions
- ≥ 6.0.0, < publication: Affected (custom)
No fix published
windows server 2008 r2 systems service pack 1
- Versions
- ≥ 6.1.0, < publication: Affected (custom)
No fix published
windows server 2008 r2 service pack 1
- Versions
- ≥ 6.1.0, < publication: Affected (custom)
No fix published
Original sources
- https://portal.msrc.microsoft.com/en-US/security-guidance/advisory/CVE-2019-1125
- https://www.synology.com/security/advisory/Synology_SA_19_32
- https://access.redhat.com/errata/RHSA-2019:2600
- https://access.redhat.com/errata/RHSA-2019:2609
- https://access.redhat.com/errata/RHSA-2019:2695
- https://access.redhat.com/errata/RHSA-2019:2696
- https://access.redhat.com/errata/RHSA-2019:2730
- https://kc.mcafee.com/corporate/index?page=content&id=SB10297
- https://access.redhat.com/errata/RHSA-2019:2900
- https://access.redhat.com/errata/RHSA-2019:2899
- https://access.redhat.com/errata/RHSA-2019:2975
- https://access.redhat.com/errata/RHSA-2019:3011
- https://access.redhat.com/errata/RHBA-2019:2824
- https://access.redhat.com/errata/RHSA-2019:3220
- https://access.redhat.com/errata/RHBA-2019:3248
- http://packetstormsecurity.com/files/156337/SWAPGS-Attack-Proof-Of-Concept.html
- http://www.huawei.com/en/psirt/security-advisories/huawei-sa-20200408-01-swapgs-en
- https://nvd.nist.gov/vuln/detail/CVE-2019-1125