7.8

CVE-2025-32709

Warnung
Medienbericht

Use after free in Windows Ancillary Function Driver for WinSock 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 Version < 10.0.10240.21014
Microsoft ≫ Windows 10 1607 Version < 10.0.14393.8066
Microsoft ≫ Windows 10 1809 HwPlatformx64 Version < 10.0.17763.7314
Microsoft ≫ Windows 10 1809 HwPlatformx86 Version < 10.0.17763.7314
Microsoft ≫ Windows 10 21h2 Version < 10.0.19044.5854
Microsoft ≫ Windows 10 22h2 Version < 10.0.19045.5854
Microsoft ≫ Windows 11 22h2 Version < 10.0.22621.5335
Microsoft ≫ Windows 11 23h2 Version < 10.0.22631.5335
Microsoft ≫ Windows 11 24h2 Version < 10.0.26100.4061
Microsoft ≫ Windows Server 2016 Version < 10.0.14393.8066
Microsoft ≫ Windows Server 2019 Version < 10.0.17763.7314
Microsoft ≫ Windows Server 2022 Version < 10.0.20348.3692
Microsoft ≫ Windows Server 2022 23h2 Version < 10.0.25398.1611
Microsoft ≫ Windows Server 2025 Version < 10.0.26100.4061

13.05.2025: CISA Known Exploited Vulnerabilities (KEV) Catalog

Microsoft Windows Ancillary Function Driver for WinSock Use-After-Free Vulnerability

Schwachstelle

Microsoft Windows Ancillary Function Driver for WinSock contains a use-after-free vulnerability that allows an authorized attacker to escalate privileges to administrator.

Beschreibung

Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.

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