CVE-2020-24512

Observable timing discrepancy in some Intel(R) Processors may allow an authenticated user to potentially enable information disclosure via local access.

Published: 2021-06-09 Last update: 2024-11-21 Assigner: [email protected] Source: [email protected]

Conclusion & alert: CVE-2020-24512 is rated Low Risk (24/100): CVSS Low severity, with low exploitation likelihood (EPSS 0.39%). Mandatory action: Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2020-24512

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.19% 0.39% +0.19%
2 2026-05-04 0.06% 0.19% +0.13%
3 2025-10-11 0.06%

Full EPSS history (18 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2020-24512

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
3.3 3.1 LOW
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:L)
Some sensitive info could get out, but not a total data dump.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:N)
Service keeps running; no real outage angle.
1.8 1.4 [email protected]
2.1 2.0 LOW
AV:L/AC:L/Au:N/C:P/I:N/A:N Click to expand
Access vector (AV:L)
Requires local access to the target system.
Access complexity (AC:L)
Exploitation conditions are straightforward and predictable.
Authentication (AU:N)
No authentication is required.
Confidentiality impact (C:P)
Partial confidentiality impact.
Integrity impact (I:N)
No integrity impact.
Availability impact (A:N)
No availability impact.
3.9 2.9 [email protected]

Weakness enumeration for CVE-2020-24512

OS Trackers for CVE-2020-24512

vendor priority summary link
debian not yet assigned CVE-2020-24512 not yet assigned priority: Debian including 1 source packages (intel-microcode), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2020-24512
redhat low https://access.redhat.com/security/cve/CVE-2020-24512
suse low CVE-2020-24512 severity low: SUSE including 17 source package names (microcode_ctl-1.17-102.83.71.1, microcode_ctl-2.1-73.11.el7_9, …), 72 product×package rows across 72 product lines (HPE Helion OpenStack 8, Image SLES12-SP5-SAP-Azure-LI-BYOS-Production, … (72 product lines)): Fixed 72. https://www.suse.com/security/cve/CVE-2020-24512/
ubuntu medium CVE-2020-24512 medium priority: Ubuntu including 1 source packages (intel-microcode), 9 status rows across 9 suites (bionic, focal, groovy, hirsute, impish, jammy, trusty, upstream, xenial): released 8, needs-triage 1. https://ubuntu.com/security/CVE-2020-24512

Affected software / configurations for CVE-2020-24512

Vendor Product Version Raw CPE
intel microcode < 20210608 cpe:2.3:o:intel:microcode:*:*:*:*:*:*:*:*
debian debian_linux 10.0 cpe:2.3:o:debian:debian_linux:10.0:*:*:*:*:*:*:*
netapp fas\/aff_bios cpe:2.3:o:netapp:fas\/aff_bios:-:*:*:*:*:*:*:*
netapp hci_compute_node_bios cpe:2.3:o:netapp:hci_compute_node_bios:-:*:*:*:*:*:*:*
netapp solidfire_bios cpe:2.3:o:netapp:solidfire_bios:-:*:*:*:*:*:*:*

References for CVE-2020-24512

cvelogic Threat Intelligence