CVE-2024-38074: Windows Remote Desktop Licensing Service Remote Code Execution Vulnerability
First published: Tue Jul 09 2024(Updated: )
Windows Remote Desktop Licensing Service Remote Code Execution Vulnerability
Credit: secure@microsoft.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Microsoft Windows Server 2012 R2 | ||
| Microsoft Windows Server 2022 | ||
| Microsoft Windows Server 2016 | ||
| Microsoft Windows Server 2008 R2 | ||
| Microsoft Windows Server 2019 | ||
| Microsoft Windows Server 2008 R2 | ||
| Microsoft Windows Server 2019 | ||
| Microsoft Windows Server 2012 R2 | ||
| Microsoft Windows Server 2016 | ||
| Microsoft Windows Server 2022 | ||
| Microsoft Windows Server 2012 x64 | ||
| Microsoft Windows Server 2012 x64 | ||
| Microsoft Windows Server 2022 23H2 | ||
| Microsoft Windows Server 2008 Itanium | =r2-sp1 | |
| Microsoft Windows Server 2012 x64 | ||
| Microsoft Windows Server 2012 x64 | =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 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2024-38074?
CVE-2024-38074 is classified as a critical remote code execution vulnerability in the Windows Remote Desktop Licensing Service.
How do I fix CVE-2024-38074?
To fix CVE-2024-38074, apply the appropriate security patches provided by Microsoft for your affected Windows Server version.
Which versions of Windows Server are affected by CVE-2024-38074?
CVE-2024-38074 affects multiple versions of Windows Server, including 2008 R2, 2012, 2016, 2019, 2022, and 2022 23H2 Edition.
What are the potential impacts of exploiting CVE-2024-38074?
Exploiting CVE-2024-38074 can allow an attacker to execute arbitrary code on a vulnerable system, leading to full system compromise.
Is there a workaround for CVE-2024-38074 if I cannot apply the patch immediately?
No official workaround is provided for CVE-2024-38074; applying the patch is the recommended immediate mitigation.
- collector/msrc
- source/Microsoft
- agent/type
- agent/description
- agent/first-publish-date
- collector/msrc-cve
- agent/software-canonical-lookup
- agent/title
- agent/severity
- agent/weakness
- agent/author
- collector/the-register
- source/The Register
- alias/CVE-2024-38080
- alias/CVE-2024-38112
- alias/CVE-2024-35264
- alias/CVE-2024-37985
- alias/CVE-2024-38074
- alias/CVE-2024-38076
- alias/CVE-2024-38077
- alias/CVE-2024-38060
- alias/CVE-2024-38023
- alias/CVE-2024-34123
- alias/CVE-2024-20781
- alias/CVE-2024-20782
- alias/CVE-2024-20783
- alias/CVE-2024-20785
- alias/CVE-2024-34139
- alias/CVE-2024-34140
- alias/CVE-2024-26006
- alias/CVE-2024-26015
- alias/CVE-2024-6151
- alias/CVE-2024-6286
- alias/CVE-2024-31320
- agent/references
- agent/remedy
- agent/event
- agent/trending
- collector/mitre-cve
- source/MITRE
- agent/last-modified-date
- agent/source
- agent/software-canonical-lookup-request
- agent/softwarecombine
- agent/tags
- collector/nvd-api
- source/NVD
- vendor/microsoft
- canonical/microsoft windows server 2012 r2
- canonical/microsoft windows server 2022
- canonical/microsoft windows server 2016
- canonical/microsoft windows server 2008 r2
- canonical/microsoft windows server 2019
- canonical/microsoft windows server 2012 x64
- canonical/microsoft windows server 2022 23h2
- canonical/microsoft windows server 2008 itanium
- version/microsoft windows server 2008 itanium/r2-sp1
- version/microsoft windows server 2012 x64/r2