CVE-2024-49126
8.1
Vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
Exploitability: 2.2 / Impact: 5.9
Source: secure@microsoft.com (Secondary)
Description
Windows Local Security Authority Subsystem Service (LSASS) Remote Code Execution Vulnerability
Affected (20)
Products: Microsoft: Windows 10 1507, Windows 10 1607, Windows 10 1809, Windows 10 21h2, Windows 10 22h2, Windows 11 22h2, Windows 11 23h2, Windows 11 24h2, Windows Server 2008, Windows Server 2012, Windows Server 2016, Windows Server 2019, Windows Server 2022, Windows Server 2022 23h2, Windows Server 2025
Configuration A
| Vulnerable Software | Affected Versions |
|---|---|
| Before 10.0.10240.20857 | |
| Before 10.0.14393.7606 | |
| Before 10.0.17763.6659 | |
| Before 10.0.19044.5247 | |
| Before 10.0.19045.5247 | |
| Before 10.0.22621.4602 | |
| Before 10.0.22631.4602 | |
| Before 10.0.26100.2605 | |
| All versions | |
| All versions | |
| Before 10.0.14393.7606 | |
| Before 10.0.17763.6659 | |
| Before 10.0.20348.2966 | |
| Before 10.0.25398.1308 | |
| Before 10.0.26100.2605 |
Related CWEs
CWE-362
Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')
The product contains a code sequence that can run concurrently with other code, and the code sequence requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence that is operating concurrently.
CWE-416
Use After Free
The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer.
CWE-591
Sensitive Data Storage in Improperly Locked Memory
The product stores sensitive data in memory that is not locked, or that has been incorrectly locked, which might cause the memory to be written to swap files on disk by the virtual memory manager. This can make the data more accessible to external actors.
References (1)
Source: secure@microsoft.com
Vendor Advisory
Timeline
No history available yet.