Microsoft Local Security Authority Subsystem Service Information Disclosure Vulnerability
🔗 CVE IDs covered (1)
📋 Description
How could an attacker exploit this vulnerability? An attacker could exploit the vulnerability by convincing, or waiting for, a user to connect to an Active Directory Domain Controller and then stealing network secrets. When the vulnerability is successfully exploited this could allow the attacker to retrieve sensitive data in plain-text which could be exploited for further attacks.
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 must be on the network to monitor domain network traffic (PR:L) while monitoring for user (UI:R) generated network traffic, or alternatively that attacker convinces an authenticated user to execute a malicious script, as a step to exploit this vulnerability.
🎯 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
KB5034127 (Security Update) — fixed build 10.0.17763.5329 KB5034129 (Security Update) — fixed build 10.0.20348.2227 KB5034121 (Security Update) — fixed build 10.0.22000.2713 KB5034122 (Security Update) — fixed build 10.0.19044.3930 KB5034123 (Security Update) — fixed build 10.0.22621.3007 KB5034122 (Security Update) — fixed build 10.0.19045.3930 KB5034123 (Security Update) — fixed build 10.0.22631.3007 KB5034130 (Security Update) — fixed build 10.0.25398.643 KB5034134 (Security Update) — fixed build 10.0.10240.20402 KB5034119 (Security Update) — fixed build 10.0.14393.6614 KB5034173 (Monthly Rollup) — fixed build 6.0.6003.22464 KB5034176 (Security Only) — fixed build 6.0.6003.22464 KB5034169 (Monthly Rollup) — fixed build 6.1.7601.26910 KB5034167 (Security Only) — fixed build 6.1.7601.26910 KB5034184 (Monthly Rollup) — fixed build 6.2.9200.24664 KB5034171 (Monthly Rollup) — fixed build 6.3.9600.21765
🔗 References (29)
- advisoryhttps://msrc.microsoft.com/update-guide/vulnerability/CVE-2024-20692
- patchhttps://catalog.update.microsoft.com/v7/site/Search.aspx?q=KB5034127
- referencehttps://support.microsoft.com/help/5034127
- patchhttps://catalog.update.microsoft.com/v7/site/Search.aspx?q=KB5034129
- referencehttps://support.microsoft.com/help/5034129
- patchhttps://catalog.update.microsoft.com/v7/site/Search.aspx?q=KB5034121
- referencehttps://support.microsoft.com/help/5034121
- patchhttps://catalog.update.microsoft.com/v7/site/Search.aspx?q=KB5034122
- referencehttps://support.microsoft.com/help/5034122
- patchhttps://catalog.update.microsoft.com/v7/site/Search.aspx?q=KB5034123
- referencehttps://support.microsoft.com/help/5034123
- patchhttps://catalog.update.microsoft.com/v7/site/Search.aspx?q=KB5034130
- referencehttps://support.microsoft.com/help/5034130
- patchhttps://catalog.update.microsoft.com/v7/site/Search.aspx?q=KB5034134
- referencehttps://support.microsoft.com/help/5034134
- patchhttps://catalog.update.microsoft.com/v7/site/Search.aspx?q=KB5034119
- referencehttps://support.microsoft.com/help/5034119
- patchhttps://catalog.update.microsoft.com/v7/site/Search.aspx?q=KB5034173
- referencehttps://support.microsoft.com/help/5034173
- patchhttps://catalog.update.microsoft.com/v7/site/Search.aspx?q=KB5034176
- referencehttps://support.microsoft.com/help/5034176
- patchhttps://catalog.update.microsoft.com/v7/site/Search.aspx?q=KB5034169
- referencehttps://support.microsoft.com/help/5034169
- patchhttps://catalog.update.microsoft.com/v7/site/Search.aspx?q=KB5034167
- referencehttps://support.microsoft.com/help/5034167
- patchhttps://catalog.update.microsoft.com/v7/site/Search.aspx?q=KB5034184
- referencehttps://support.microsoft.com/help/5034184
- patchhttps://catalog.update.microsoft.com/v7/site/Search.aspx?q=KB5034171
- referencehttps://support.microsoft.com/help/5034171