Skip to content

CVE-2024-38106

Windows Kernel Elevation of Privilege Vulnerability

High Known exploited
Severity
7.0 / 10
High · CVSS 3.1
Exploit chance (EPSS)
6.34%
Chance of exploitation in the next 30 days. Higher than 93.63% of scored vulnerabilities.
Known exploited
Yes
In CISA's catalog since Aug 13, 2024
Weakness
CWE-591 Sensitive Data Storage in Improperly Locked Memory
Fix
None yet
No fixed version published
Exploited in the wild. Microsoft Windows Kernel Privilege Escalation Vulnerability (Microsoft Windows). Required action: Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable. Due for U.S. federal agencies by Sep 3, 2024.

Description

Windows Kernel Elevation of Privilege Vulnerability

How to fix

No fixed version has been published yet. Until one is, remove or replace the package, or turn off or isolate the affected feature. This page updates when a fix ships.

Severity breakdown

CVSS 3.1 7.0

CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H

Attack vector
Local
Attack complexity
High
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Weakness

CWE-591: Sensitive Data Storage in Improperly Locked Memory

The product stores sensitive data in memory that is not locked, or that has been incorrectly locked, which might cause the memory to be written to swap files on disk by the virtual memory manager. This can make the data more accessible to external actors.

How to prevent it
  • Architecture and Design: Identify data that needs to be protected from swapping and choose platform-appropriate protection mechanisms.
  • Implementation: Check return values to ensure locking operations are successful.

References

Timeline

  1. Added to CISA's Known Exploited Vulnerabilities catalog
  2. Published
  3. Remediation due for U.S. federal agencies
  4. Last updated by the source
  5. Latest EPSS score
AdvisorySeverityWhy it's related
CVE-2023-28229
Windows CNG Key Isolation Service Elevation of Privilege Vulnerability
High Known exploited Same weakness, CWE-591
Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor