CVE-2024-38077: Windows Remote Desktop Licensing Service Remote Code Execution Vulnerability
Published Jul 9, 2024
·Updated
Windows Remote Desktop Licensing Service Remote Code Execution Vulnerability
Affected Software
26 affected componentsFixes available
Microsoft Windows Server 2012 R2
Microsoft Windows Server 2012 R2
Microsoft Windows Server 2022, 23H2 Edition
Microsoft Windows Server 2012
Microsoft Windows Server 2012
Microsoft Windows Server 2008
Microsoft Windows Server 2008
Microsoft Windows Server 2008
Microsoft Windows Server 2008
Microsoft Windows Server 2008=sp2
Microsoft Windows Server 2008=sp2
Microsoft Windows Server 2008=r2-sp1
Microsoft Windows Server 2012
Microsoft Windows Server 2012=r2
Microsoft Windows Server 2016<10.0.14393.7159
Microsoft Windows Server 2019<10.0.17763.6054
Microsoft Windows Server 2022<10.0.20348.2582
Microsoft Windows Server 2022 23h2<10.0.25398.1009
Microsoft Windows Server 2019
Microsoft Windows Server 2019
Microsoft Windows Server 2022
Microsoft Windows Server 2022
Microsoft Windows Server 2016
Microsoft Windows Server 2016
Microsoft Windows Server 2008 R2
Microsoft Windows Server 2008 R2
Remediation
Event History
Jul 9, 2024
CVE Published
via Microsoft·07:00 AM
Data Sourced
via Microsoft·07:00 AM
DescriptionSeverityWeakness
CVE Published
via MITRE·05:02 PM
Data Sourced
via MITRE·05:02 PM
DescriptionSeverity
Jul 10, 2024
News Published
via The Register·12:59 AM
News Published
via The Register·01:02 AM
Frequently Asked Questions
1
What is the severity of CVE-2024-38077?
CVE-2024-38077 has a critical severity level due to its potential to allow remote code execution.
2
How do I fix CVE-2024-38077?
To fix CVE-2024-38077, you should apply the latest security patch provided by Microsoft for your affected version of Windows Server.
3
Which versions of Windows Server are affected by CVE-2024-38077?
CVE-2024-38077 affects multiple Windows Server versions including 2008, 2012, 2016, 2019, and 2022.
4
What types of attacks can exploit CVE-2024-38077?
CVE-2024-38077 can be exploited through specially crafted requests sent to the Windows Remote Desktop Licensing Service.
5
Is there a workaround for CVE-2024-38077 before applying the patch?
Currently, the best practice is to apply the security patch, as there are no known effective workarounds for CVE-2024-38077.