CVE-2020-24511 [Medium] | Information Disclosure in Microcode

CVE-2020-24511 is rated Low Risk (37.4/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.40%). Monitor for updates and reassess as exploit intelligence or EPSS changes.

#	Date	Old EPSS score	New EPSS score	Delta (New - Old)
1	2026-06-15	0.07%	0.40%	+0.33%
2	2025-03-30	0.24%	0.07%	-0.17%
3	2025-03-29	—	0.24%	—

Date

Old EPSS score

New EPSS score

Delta (New - Old)

2026-06-15

0.07%

0.40%

+0.33%

2025-03-30

0.24%

0.07%

-0.17%

2025-03-29

—

0.24%

—

Base score	Version	Severity	Vector	Exploitability	Impact	Score source
6.5	3.1	MEDIUM	`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/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:C) Breaking this can reach past the original component and bite other resources—bigger blast radius. Confidentiality (C:H) Serious risk that confidential data gets exposed in a big way. Integrity (I:N) Data isn’t meaningfully altered or forged. Availability (A:N) Service keeps running; no real outage angle.	2.0	4.0	[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]

Base score

Version

Severity

Vector

Exploitability

Impact

Score source

6.5

3.1

MEDIUM

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/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:C): Breaking this can reach past the original component and bite other resources—bigger blast radius.
Confidentiality (C:H): Serious risk that confidential data gets exposed in a big way.
Integrity (I:N): Data isn’t meaningfully altered or forged.
Availability (A:N): Service keeps running; no real outage angle.

2.0

4.0

[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]

OS Trackers for CVE-2020-24511

vendor	priority	summary	link
`alpine`	medium	CVE-2020-24511: 1 source package rows (intel-ucode); 7 state rows across 7 repos (3.17-main, 3.18-main, 3.19-main, 3.20-main, 3.21-main, 3.22-main, edge-main); fixed 7, open 0.	https://security.alpinelinux.org/vuln/CVE-2020-24511
`debian`	not yet assigned	CVE-2020-24511 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-24511
`redhat`	medium	—	https://access.redhat.com/security/cve/CVE-2020-24511
`suse`	medium	CVE-2020-24511 severity moderate: 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-24511/
`ubuntu`	medium	CVE-2020-24511 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-24511

Affected software / configurations for CVE-2020-24511

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-24511

URL	Tags
https://cert-portal.siemens.com/productcert/pdf/ssa-309571.pdf	Third Party Advisory
https://lists.debian.org/debian-lts-announce/2021/07/msg00022.html	Third Party Advisory
https://security.netapp.com/advisory/ntap-20210611-0005/	Third Party Advisory
https://www.debian.org/security/2021/dsa-4934	Third Party Advisory
https://www.intel.com/content/www/us/en/security-center/advisory/intel-sa-00464.html	Vendor Advisory

URL

CVE-2020-24511

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

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

Weakness enumeration for CVE-2020-24511

OS Trackers for CVE-2020-24511

Affected software / configurations for CVE-2020-24511

References for CVE-2020-24511