This page was not yet optimized for use on mobile devices.
CVE-2022-44669
Data ?
Vulnerability ID | CVE-2022-44669 |
---|---|
Published on | 13.12.2022 19:15 |
Severity | HIGH |
Vulnerable configurations ?
- cpe:2.3:o:microsoft:windows_10:20h2:*:*:*:*:*:*:*, cpe:2.3:o:microsoft:windows_10:20h2:*:*:*:*:*:arm64:*, cpe:2.3:o:microsoft:windows_10:20h2:*:*:*:*:*:x64:*, cpe:2.3:o:microsoft:windows_10:20h2:*:*:*:*:*:x86:*
- cpe:2.3:o:microsoft:windows_10:21h1:*:*:*:*:*:*:*, cpe:2.3:o:microsoft:windows_10:21h1:*:*:*:*:*:arm64:*, cpe:2.3:o:microsoft:windows_10:21h1:*:*:*:*:*:x64:*, cpe:2.3:o:microsoft:windows_10:21h1:*:*:*:*:*:x86:*
-
cpe:2.3:o:microsoft:windows_10:21h2:*:*:*:*:*:*:*,
cpe:2.3:o:microsoft:windows_10:21h2:*:*:*:*:*:arm64:*,
…
Vulnerable certificates ?
This CVE has no assigned vulnerable CC or FIPS certificates.
Looking for more?
Explore the landscape of Common Criteria and FIPS 140 certificates.