CVE-2024-38137: Windows Resource Manager PSM Service Extension Elevation of Privilege Vulnerability
Published Aug 13, 2024
·Updated
Windows Resource Manager PSM Service Extension Elevation of Privilege Vulnerability
Affected Software
25 affected componentsFixes available
Microsoft Windows Server 2022, 23H2 Edition
Microsoft Windows 11=23H2
Microsoft Windows 11=22H2
Microsoft Windows 11=22H2
Microsoft Windows 11=24H2
Microsoft Windows 11=24H2
Microsoft Windows 11=21H2
Microsoft Windows 11=21H2
Microsoft Windows 11=23H2
Microsoft Windows Server 2022
Microsoft Windows Server 2022
Microsoft Windows 10 21h2<10.0.19044.4780
Microsoft Windows 10 22h2<10.0.19045.4780
Microsoft Windows 11 21h2<10.0.22000.3147
Microsoft Windows 11 22h2<10.0.22621.4037
Microsoft Windows 11 23h2<10.0.22631.4037
Microsoft Windows 11 24h2<10.0.26100.1457
Microsoft Windows Server 2022<10.0.20348.2655
Microsoft Windows Server 2022 23h2<10.0.25398.1085
Microsoft Windows 10=22H2
Microsoft Windows 10=22H2
Microsoft Windows 10=22H2
Microsoft Windows 10=21H2
Microsoft Windows 10=21H2
Microsoft Windows 10=21H2
Remediation
Event History
Aug 13, 2024
CVE Published
via Microsoft·07:00 AM
Data Sourced
via Microsoft·07:00 AM
DescriptionSeverityWeakness
CVE Published
via MITRE·05:30 PM
Data Sourced
via MITRE·05:30 PM
DescriptionSeverity
Data Sourced
via NVD·06:15 PM
DescriptionSeverityWeakness
Frequently Asked Questions
1
What is the severity of CVE-2024-38137?
CVE-2024-38137 has been categorized as an elevation of privilege vulnerability, which could allow unauthorized access.
2
How do I fix CVE-2024-38137?
To fix CVE-2024-38137, apply the relevant security updates provided by Microsoft for your version of Windows.
3
Which Windows versions are affected by CVE-2024-38137?
CVE-2024-38137 affects multiple versions of Windows, including Windows 10 and Windows 11 across various builds.
4
What could happen if CVE-2024-38137 is exploited?
Exploiting CVE-2024-38137 could allow an attacker to elevate their privileges and execute arbitrary code on the system.
5
Is there a workaround for CVE-2024-38137?
There are no known workarounds for CVE-2024-38137; applying patches is the recommended course of action.