Windows Distributed File System (DFS) Remote Code Execution Vulnerability
🔗 CVE IDs covered (1)
📋 Description
According to the CVSS metric, user interaction is required (UI:R). What interaction would the user have to do? This vulnerability could be triggered when a user connects a Windows client to a malicious server.
According to the CVSS metric, privileges required is low (PR:L). What does that mean for this vulnerability? Successful exploitation of this vulnerability requires an attacker to have obtained low privileged code execution on target host first.
According to the CVSS score, the attack vector is adjacent (AV:A). What does this mean for this vulnerability? Exploiting this vulnerability requires an attacker to be on the same network segment as the target system. Traffic associated with exploitation of this vulnerability is not routable and is bound to the data link layer of the OSI model.
🎯 Affected products36
- Windows 10 Version 1607 for 32-bit Systems
- Windows 10 Version 1607 for x64-based Systems
- Windows 10 Version 1809 for 32-bit Systems
- Windows 10 Version 1809 for ARM64-based Systems
- Windows 10 Version 1809 for x64-based Systems
- Windows 10 Version 21H2 for 32-bit Systems
- Windows 10 Version 21H2 for ARM64-based Systems
- Windows 10 Version 21H2 for x64-based Systems
- Windows 10 Version 22H2 for 32-bit Systems
- Windows 10 Version 22H2 for ARM64-based Systems
- Windows 10 Version 22H2 for x64-based Systems
- Windows 10 for 32-bit Systems
- Windows 10 for x64-based Systems
- Windows 11 Version 22H2 for ARM64-based Systems
- Windows 11 Version 22H2 for x64-based Systems
- Windows 11 Version 23H2 for ARM64-based Systems
- Windows 11 Version 23H2 for x64-based Systems
- Windows 11 version 21H2 for ARM64-based Systems
- Windows 11 version 21H2 for x64-based Systems
- 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
- +6 more not shown
✅ Remediation
KB5039217 (Security Update) — fixed build 10.0.17763.5936 KB5039227 (Security Update) — fixed build 10.0.20348.2527 KB5039330 (Security Hotpatch Update) — fixed build 10.0.20348.2522 KB5039213 (Security Update) — fixed build 10.0.22000.3019 KB5039211 (Security Update) — fixed build 10.0.19044.4529 KB5039212 (Security Update) — fixed build 10.0.22621.3737 KB5039211 (Security Update) — fixed build 10.0.19045.4529 KB5039212 (Security Update) — fixed build 10.0.22631.3737 KB5039236 (Security Update) — fixed build 10.0.25398.950 KB5039225 (Security Update) — fixed build 10.0.10240.20680 KB5039214 (Security Update) — fixed build 10.0.14393.7070 KB5039245 (Monthly Rollup) — fixed build 6.0.6003.22720 KB5039266 (Security Only) — fixed build 6.0.6003.22720 KB5039289 (Monthly Rollup) — fixed build 6.1.7601.27170 KB5039274 (Security Only) — fixed build 6.1.7601.27170 KB5039260 (Monthly Rollup) — fixed build 6.2.9200.24919 KB5039294 (Monthly Rollup) — fixed build 6.3.9600.22023
🔗 References (31)
- advisoryhttps://msrc.microsoft.com/update-guide/vulnerability/CVE-2024-30063
- patchhttps://catalog.update.microsoft.com/v7/site/Search.aspx?q=KB5039217
- referencehttps://support.microsoft.com/help/5039217
- patchhttps://catalog.update.microsoft.com/v7/site/Search.aspx?q=KB5039227
- referencehttps://support.microsoft.com/help/5039227
- patchhttps://catalog.update.microsoft.com/v7/site/Search.aspx?q=KB5039330
- referencehttps://support.microsoft.com/help/5039330
- patchhttps://catalog.update.microsoft.com/v7/site/Search.aspx?q=KB5039213
- referencehttps://support.microsoft.com/help/5039213
- patchhttps://catalog.update.microsoft.com/v7/site/Search.aspx?q=KB5039211
- referencehttps://support.microsoft.com/help/5039211
- patchhttps://catalog.update.microsoft.com/v7/site/Search.aspx?q=KB5039212
- referencehttps://support.microsoft.com/help/5039212
- patchhttps://catalog.update.microsoft.com/v7/site/Search.aspx?q=KB5039236
- referencehttps://support.microsoft.com/help/5039236
- patchhttps://catalog.update.microsoft.com/v7/site/Search.aspx?q=KB5039225
- referencehttps://support.microsoft.com/help/5039225
- patchhttps://catalog.update.microsoft.com/v7/site/Search.aspx?q=KB5039214
- referencehttps://support.microsoft.com/help/5039214
- patchhttps://catalog.update.microsoft.com/v7/site/Search.aspx?q=KB5039245
- referencehttps://support.microsoft.com/help/5039245
- patchhttps://catalog.update.microsoft.com/v7/site/Search.aspx?q=KB5039266
- referencehttps://support.microsoft.com/help/5039266
- patchhttps://catalog.update.microsoft.com/v7/site/Search.aspx?q=KB5039289
- referencehttps://support.microsoft.com/help/5039289
- patchhttps://catalog.update.microsoft.com/v7/site/Search.aspx?q=KB5039274
- referencehttps://support.microsoft.com/help/5039274
- patchhttps://catalog.update.microsoft.com/v7/site/Search.aspx?q=KB5039260
- referencehttps://support.microsoft.com/help/5039260
- patchhttps://catalog.update.microsoft.com/v7/site/Search.aspx?q=KB5039294
- referencehttps://support.microsoft.com/help/5039294