Windows Mobile Hotspot Information Disclosure Vulnerability
🔗 CVE IDs covered (1)
📋 Description
What type of information could be disclosed by this vulnerability? The type of information that could be disclosed if an attacker successfully exploited this vulnerability is uninitialized memory.
According to the CVSS metric, user interaction is required (UI:R). What interaction would the user have to do? Exploitation of the vulnerability requires a user to first turn on the Mobile Hotspot before the attacker starts the exploitation.
According to the CVSS metric, user interaction is required (UI:R) and privileges required is Low (PR:L). What does that mean for this vulnerability? An authorized attacker with guest/low privileges must first gain access to the local system, then wait for or trick the user into turning on the Mobile Hotspot feature. Only when the Mobile Hotspot is turned on does the vulnerability become exploitable. Therefore, this attack vector requires both attacker authentication (to access the local system) and user interaction (to turn on the Mobile Hotspot).
🎯 Affected products26
- 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 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
KB5036896 (Security Update) — fixed build 10.0.17763.5696 KB5036909 (Security Update) — fixed build 10.0.20348.2402 KB5036894 (Security Update) — fixed build 10.0.22000.2899 KB5036892 (Security Update) — fixed build 10.0.19044.4291 KB5036893 (Security Update) — fixed build 10.0.22621.3447 KB5036892 (Security Update) — fixed build 10.0.19045.4291 KB5036893 (Security Update) — fixed build 10.0.22631.3447 KB5036910 (Security Update) — fixed build 10.0.25398.830 KB5036925 (Security Update) — fixed build 10.0.10240.20596 KB5036899 (Security Update) — fixed build 10.0.14393.6897
🔗 References (17)
- advisoryhttps://msrc.microsoft.com/update-guide/vulnerability/CVE-2024-26220
- patchhttps://catalog.update.microsoft.com/v7/site/Search.aspx?q=KB5036896
- referencehttps://support.microsoft.com/help/5036896
- patchhttps://catalog.update.microsoft.com/v7/site/Search.aspx?q=KB5036909
- referencehttps://support.microsoft.com/help/5036909
- patchhttps://catalog.update.microsoft.com/v7/site/Search.aspx?q=KB5036894
- referencehttps://support.microsoft.com/help/5036894
- patchhttps://catalog.update.microsoft.com/v7/site/Search.aspx?q=KB5036892
- referencehttps://support.microsoft.com/help/5036892
- patchhttps://catalog.update.microsoft.com/v7/site/Search.aspx?q=KB5036893
- referencehttps://support.microsoft.com/help/5036893
- patchhttps://catalog.update.microsoft.com/v7/site/Search.aspx?q=KB5036910
- referencehttps://support.microsoft.com/help/5036910
- patchhttps://catalog.update.microsoft.com/v7/site/Search.aspx?q=KB5036925
- referencehttps://support.microsoft.com/help/5036925
- patchhttps://catalog.update.microsoft.com/v7/site/Search.aspx?q=KB5036899
- referencehttps://support.microsoft.com/help/5036899