7.8
CVE-2021-40449
- EPSS 86.22%
- Veröffentlicht 13.10.2021 01:15:09
- Zuletzt bearbeitet 13.03.2025 16:36:21
- Quelle secure@microsoft.com
- Teams Watchlist Login
- Unerledigt Login
Win32k Elevation of Privilege Vulnerability
Daten sind bereitgestellt durch National Vulnerability Database (NVD)
Microsoft ≫ Windows 10 1507 Version < 10.0.10240.19086
Microsoft ≫ Windows 10 1607 Version < 10.0.14393.4704
Microsoft ≫ Windows 10 1809 Version < 10.0.17763.2237
Microsoft ≫ Windows 10 1909 Version < 10.0.18363.1854
Microsoft ≫ Windows 10 2004 Version < 10.0.19041.1288
Microsoft ≫ Windows 10 20h2 Version < 10.0.19041.1288
Microsoft ≫ Windows 10 21h1 Version < 10.0.19041.1288
Microsoft ≫ Windows 11 21h2 Version < 10.0.22000.258
Microsoft ≫ Windows 8.1 Version-
Microsoft ≫ Windows Rt 8.1 Version-
Microsoft ≫ Windows Server 2004 Version < 10.0.19041.1288
Microsoft ≫ Windows Server 2008 Version- Updatesp2
Microsoft ≫ Windows Server 2008 Versionr2 Updatesp1 HwPlatformx64
Microsoft ≫ Windows Server 2012 Version-
Microsoft ≫ Windows Server 2012 Versionr2
Microsoft ≫ Windows Server 2016 Version < 10.0.14393.4704
Microsoft ≫ Windows Server 2019 Version < 10.0.17763.2237
Microsoft ≫ Windows Server 2022 Version < 10.0.20348.288
Microsoft ≫ Windows Server 20h2 Version < 10.0.19042.1288
17.11.2021: CISA Known Exploited Vulnerabilities (KEV) Catalog
Microsoft Windows Win32k Privilege Escalation Vulnerability
SchwachstelleUnspecified vulnerability allows for an authenticated user to escalate privileges.
BeschreibungApply updates per vendor instructions.
Erforderliche MaßnahmenTyp | Quelle | Score | Percentile |
---|---|---|---|
EPSS | FIRST.org | 86.22% | 0.994 |
Quelle | Base Score | Exploit Score | Impact Score | Vector String |
---|---|---|---|---|
nvd@nist.gov | 4.6 | 3.9 | 6.4 |
AV:L/AC:L/Au:N/C:P/I:P/A:P
|
nvd@nist.gov | 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
|
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.