7.8

CVE-2025-49665

Concurrent execution using shared resource with improper synchronization ('race condition') in Workspace Broker allows an authorized attacker to elevate privileges locally.

Verknüpft mit AI von unstrukturierten Daten zu bestehenden CPE der NVD
Diese Information steht angemeldeten Benutzern zur Verfügung.
Daten sind bereitgestellt durch National Vulnerability Database (NVD)
Microsoft ≫ Windows 10 1507 HwPlatformx64 Version < 10.0.10240.21073
Microsoft ≫ Windows 10 1507 HwPlatformx86 Version < 10.0.10240.21073
Microsoft ≫ Windows 10 1607 HwPlatformx64 Version < 10.0.14393.8246
Microsoft ≫ Windows 10 1607 HwPlatformx86 Version < 10.0.14393.8246
Microsoft ≫ Windows 10 1809 HwPlatformx64 Version < 10.0.17763.7558
Microsoft ≫ Windows 10 1809 HwPlatformx86 Version < 10.0.17763.7558
Microsoft ≫ Windows 10 21h2 Version < 10.0.19044.6093
Microsoft ≫ Windows 10 22h2 Version < 10.0.19045.6093
Microsoft ≫ Windows 11 22h2 Version < 10.0.22621.5624
Microsoft ≫ Windows 11 23h2 Version < 10.0.22631.5624
Microsoft ≫ Windows 11 24h2 Version < 10.0.26100.4652
Microsoft ≫ Windows Server 2016 Version < 10.0.14393.8246
Microsoft ≫ Windows Server 2019 Version < 10.0.17763.7558
Microsoft ≫ Windows Server 2022 Version < 10.0.20348.3932
Microsoft ≫ Windows Server 2022 23h2 Version < 10.0.25398.1732
Microsoft ≫ Windows Server 2025 Version < 10.0.26100.4652
Zu dieser CVE wurde keine CISA KEV oder CERT.AT-Warnung gefunden.
EPSS Metriken
Typ Quelle Score Percentile
EPSS FIRST.org 0.05% 0.155
CVSS Metriken
Quelle Base Score Exploit Score Impact Score Vector String
secure@microsoft.com 7.8 1.8 5.9
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CWE-362 Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')

The product contains a concurrent code sequence that 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 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.