Windows Remote Desktop Licensing Service Spoofing Vulnerability
🔗 CVE IDs covered (1)
📋 Description
How could an attacker exploit this vulnerability? To successfully exploit this vulnerability an attacker must send specially crafted requests to the Terminal Server Licensing Service, which must be running and accessible over the network.
🎯 Affected products17
- Windows Server 2008 R2 for x64-based Systems Service Pack 1
- Windows Server 2008 R2 for x64-based Systems Service Pack 1 (Server Core installation)
- Windows Server 2008 for 32-bit Systems Service Pack 2
- Windows Server 2008 for 32-bit Systems Service Pack 2 (Server Core installation)
- Windows Server 2008 for x64-based Systems Service Pack 2
- Windows Server 2008 for x64-based Systems Service Pack 2 (Server Core installation)
- Windows Server 2012
- Windows Server 2012 (Server Core installation)
- Windows Server 2012 R2
- Windows Server 2012 R2 (Server Core installation)
- Windows Server 2016
- Windows Server 2016 (Server Core installation)
- Windows Server 2019
- Windows Server 2019 (Server Core installation)
- Windows Server 2022
- Windows Server 2022 (Server Core installation)
- Windows Server 2022, 23H2 Edition (Server Core installation)
✅ Remediation
KB5043050 (Security Update) — fixed build 10.0.17763.6293 KB5042881 (Security Update) — fixed build 10.0.20348.2700 KB5042880 (SecurityHotpatchUpdate) — fixed build 10.0.20348.2695 KB5043055 (Security Update) — fixed build 10.0.25398.1128 KB5043051 (Security Update) — fixed build 10.0.14393.7336 KB5043135 (Monthly Rollup) — fixed build 6.0.6003.22870 KB5043087 (Security Only) — fixed build 6.0.6003.22870 KB5043129 (Monthly Rollup) — fixed build 6.1.7601.27320 KB5043092 (Security Only) — fixed build 6.1.7601.27320 KB5043125 (Monthly Rollup) — fixed build 6.2.9200.25073 KB5043138 (Monthly Rollup) — fixed build 6.3.9600.22175
🔗 References (23)
- advisoryhttps://msrc.microsoft.com/update-guide/vulnerability/CVE-2024-43455
- patchhttps://catalog.update.microsoft.com/v7/site/Search.aspx?q=KB5043050
- referencehttps://support.microsoft.com/help/5043050
- patchhttps://catalog.update.microsoft.com/v7/site/Search.aspx?q=KB5042881
- referencehttps://support.microsoft.com/help/5042881
- patchhttps://catalog.update.microsoft.com/v7/site/Search.aspx?q=KB5042880
- referencehttps://support.microsoft.com/help/5042880
- patchhttps://catalog.update.microsoft.com/v7/site/Search.aspx?q=KB5043055
- referencehttps://support.microsoft.com/help/5043055
- patchhttps://catalog.update.microsoft.com/v7/site/Search.aspx?q=KB5043051
- referencehttps://support.microsoft.com/help/5043051
- patchhttps://catalog.update.microsoft.com/v7/site/Search.aspx?q=KB5043135
- referencehttps://support.microsoft.com/help/5043135
- patchhttps://catalog.update.microsoft.com/v7/site/Search.aspx?q=KB5043087
- referencehttps://support.microsoft.com/help/5043087
- patchhttps://catalog.update.microsoft.com/v7/site/Search.aspx?q=KB5043129
- referencehttps://support.microsoft.com/help/5043129
- patchhttps://catalog.update.microsoft.com/v7/site/Search.aspx?q=KB5043092
- referencehttps://support.microsoft.com/help/5043092
- patchhttps://catalog.update.microsoft.com/v7/site/Search.aspx?q=KB5043125
- referencehttps://support.microsoft.com/help/5043125
- patchhttps://catalog.update.microsoft.com/v7/site/Search.aspx?q=KB5043138
- referencehttps://support.microsoft.com/help/5043138