This page was not yet optimized for use on mobile devices.
CVE-2022-26028
Data ?
Vulnerability ID | CVE-2022-26028 |
---|---|
Published on | 11.11.2022 16:15 |
Severity | HIGH |
Vulnerable configurations ?
-
cpe:2.3:a:intel:vtune_profiler:-:*:*:*:*:*:*:*,
cpe:2.3:a:intel:vtune_profiler:2017:-:*:*:*:linux:*:*,
cpe:2.3:a:intel:vtune_profiler:2017:-:*:*:*:macos:*:*,
cpe:2.3:a:intel:vtune_profiler:2017:-:*:*:*:windows:*:*,
cpe:2.3:a:intel:vtune_profiler:2017:update_1:*:*:*:linux:*:*,
cpe:2.3:a:intel:vtune_profiler:2017:update_1:*:*:*:macos:*:*,
cpe:2.3:a:intel:vtune_profiler:2017:update_1:*:*:*:windows:*:*,
cpe:2.3:a:intel:vtune_profiler:2017:update_2:*:*:*:linux:*:*,
cpe:2.3:a:intel:vtune_profiler:2017:update_2:*:*:*:macos:*:*,
cpe:2.3:a:intel:vtune_profiler:2017:update_2:*:*:*:windows:*:*,
…
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.