Microsoft Windows Kernel Privilege Escalation
CVE-2024-38106 is a high-severity sensitive data storage in improperly locked memory vulnerability in Windows 10 Version 1809 from Microsoft, with a CVSS 3.1 base score of 7.0 out of 10. It can be exploited with local access to the system by an attacker with a low-privileged account, without any action from a user. The record lists version 10.0.17763.6189 as the first without the flaw, so updating Windows 10 Version 1809 to that release or later removes the exposure. CISA added it to the Known Exploited Vulnerabilities catalogue on August 13, 2024, which means attacks have been observed in the wild.
Attackers are already exploiting this vulnerability, according to CISA.
What to do
- Update Windows 10 Version 1809 to 10.0.17763.6189 or a later version.
- Update Windows Server 2019 to 10.0.17763.6189 or a later version.
- Update Windows Server 2019 (Server Core installation) to 10.0.17763.6189 or a later version.
- CISA's required action: Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.
- Read the advisory on msrc.microsoft.com for workarounds and exact fixed builds.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Microsoft | Windows 10 Version 1809 | 10.0.17763.0 up to, but not including, 10.0.17763.6189 | 10.0.17763.6189 |
| Microsoft | Windows Server 2019 | 10.0.17763.0 up to, but not including, 10.0.17763.6189 | 10.0.17763.6189 |
| Microsoft | Windows Server 2019 (Server Core installation) | 10.0.17763.0 up to, but not including, 10.0.17763.6189 | 10.0.17763.6189 |
| Microsoft | Windows Server 2022 | 10.0.20348.0 up to, but not including, 10.0.20348.2655 | 10.0.20348.2655 |
| Microsoft | Windows 11 version 21H2 | 10.0.0 up to, but not including, 10.0.22000.3147 | 10.0.22000.3147 |
| Microsoft | Windows 10 Version 21H2 | 10.0.19043.0 up to, but not including, 10.0.19044.4780 | 10.0.19044.4780 |
| Microsoft | Windows 11 version 22H2 | 10.0.22621.0 up to, but not including, 10.0.22621.4037 | 10.0.22621.4037 |
| Microsoft | Windows 10 Version 22H2 | 10.0.19045.0 up to, but not including, 10.0.19045.4780 | 10.0.19045.4780 |
| Microsoft | Windows 11 version 22H3 | 10.0.22631.0 up to, but not including, 10.0.22631.4037 | 10.0.22631.4037 |
| Microsoft | Windows 11 Version 23H2 | 10.0.22631.0 up to, but not including, 10.0.22631.4037 | 10.0.22631.4037 |
| Microsoft | Windows Server 2022, 23H2 Edition (Server Core installation) | 10.0.25398.0 up to, but not including, 10.0.25398.1085 | 10.0.25398.1085 |
| Microsoft | Windows 10 Version 1507 | 10.0.10240.0 up to, but not including, 10.0.10240.20751 | 10.0.10240.20751 |
| Microsoft | Windows 10 Version 1607 | 10.0.14393.0 up to, but not including, 10.0.14393.7259 | 10.0.14393.7259 |
| Microsoft | Windows Server 2016 | 10.0.14393.0 up to, but not including, 10.0.14393.7259 | 10.0.14393.7259 |
| Microsoft | Windows Server 2016 (Server Core installation) | 10.0.14393.0 up to, but not including, 10.0.14393.7259 | 10.0.14393.7259 |
| Microsoft | Windows 11 Version 24H2 | 10.0.26100.0 up to, but not including, 10.0.26100.1457 | 10.0.26100.1457 |
| Microsoft | Windows 10 1507 | before 10.0.10240.20751 | 10.0.10240.20751 |
| Microsoft | Windows 10 1607 | before 10.0.14393.7259 | 10.0.14393.7259 |
| Microsoft | Windows 10 1809 | before 10.0.17763.6189 | 10.0.17763.6189 |
| Microsoft | Windows 10 21h2 | before 10.0.19044.4780 | 10.0.19044.4780 |
| Microsoft | Windows 10 22h2 | before 10.0.19045.4780 | 10.0.19045.4780 |
| Microsoft | Windows 11 21h2 | before 10.0.22000.3147 | 10.0.22000.3147 |
| Microsoft | Windows 11 22h2 | before 10.0.22621.4037 | 10.0.22621.4037 |
| Microsoft | Windows 11 23h2 | before 10.0.22631.4037 | 10.0.22631.4037 |
| Microsoft | Windows 11 24h2 | before 10.0.26100.1457 | 10.0.26100.1457 |
Version data comes from the organisation that assigned the CVE; 1 further products are omitted here. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- LocalThe attacker needs local access or must trick a user into running something.
- Attack complexity
- HighSuccess depends on conditions outside the attacker's control.
- Privileges required
- LowA basic user account is enough.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H. Scored by CNA (microsoft.com).
Official description
Windows Kernel Elevation of Privilege Vulnerability
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Sensitive Data Storage in Improperly Locked Memory
The product stores sensitive data in memory that is not locked, or that has been incorrectly locked.
How developers prevent this class of flaw
- Identify data that needs to be protected from swapping and choose platform-appropriate protection mechanisms.
- When using potentially risky functions such as mlock() or VirtualLock(), check return values to ensure that locking operations are successful.
More Sensitive Data Storage in Improperly Locked Memory vulnerabilities (CWE-591)
Timeline
- CVE record published.
- Added to CISA's Known Exploited Vulnerabilities catalogue.
- CISA published its SSVC assessment (exploitation: active, automatable: no, technical impact: total).
- Deadline for US federal agencies to remediate, set by CISA.
- Record last changed materially (score, affected products, status or references).
References
Third-party and government advisories
- cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2024-38106US Government Resource
Recent Sensitive Data Storage in Improperly Locked Memory vulnerabilities
- 7.0 High severity
Spotted an error? Tell us.