7.8

CVE-2024-38193

Warnung
Exploit

Windows Ancillary Function Driver for WinSock Elevation of Privilege Vulnerability

Daten sind bereitgestellt durch National Vulnerability Database (NVD)
Microsoft ≫ Windows 10 1507 Version < 10.0.10240.20751
Microsoft ≫ Windows 10 1607 Version < 10.0.14393.7259
Microsoft ≫ Windows 10 1809 Version < 10.0.17763.6189
Microsoft ≫ Windows 10 21h2 Version < 10.0.19044.4780
Microsoft ≫ Windows 10 22h2 Version < 10.0.19045.4780
Microsoft ≫ Windows 11 21h2 Version < 10.0.22000.3147
Microsoft ≫ Windows 11 22h2 Version < 10.0.22621.4037
Microsoft ≫ Windows 11 23h2 Version < 10.0.22631.4037
Microsoft ≫ Windows 11 24h2 Version < 10.0.26100.1457
Microsoft ≫ Windows Server 2008 Version- Updatesp2
Microsoft ≫ Windows Server 2008 Versionr2 Updatesp1 HwPlatformx64
Microsoft ≫ Windows Server 2012 Version < 6.2.9200.25031
Microsoft ≫ Windows Server 2016 Version < 10.0.14393.7259
Microsoft ≫ Windows Server 2019 Version < 10.0.17763.6189
Microsoft ≫ Windows Server 2022 Version < 10.0.20348.2655
Microsoft ≫ Windows Server 2022 23h2 Version < 10.0.25398.1085

13.08.2024: CISA Known Exploited Vulnerabilities (KEV) Catalog

Microsoft Windows Ancillary Function Driver for WinSock Privilege Escalation Vulnerability

Schwachstelle

Microsoft Windows Ancillary Function Driver for WinSock contains an unspecified vulnerability that allows for privilege escalation, enabling a local attacker to gain SYSTEM privileges.

Beschreibung

Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable.

Erforderliche Maßnahmen
EPSS Metriken
Typ Quelle Score Percentile
EPSS FIRST.org 65.95% 0.985
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-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.