Grub2 vulnerabilitiesRanked by how likely they are to be used.
Grub2 is made by Gnu. We track 43 published vulnerabilities in it, across 10 versions. None of them is on the list of flaws known to be exploited today. If you run Grub2, keep it on a version the vendor still supports.
We keep watching the known-exploited list.
Which Grub2 vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Grub2's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Grub2 flaws are most likely to be used?
Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.
- 1.7%CVE-2020-14372High
A flaw was found in grub2 in versions prior to 2.06, where it incorrectly enables the usage of the ACPI command when Secure Boot is enabled.
- 1.7%CVE-2020-10713High
A flaw was found in grub2, prior to version 2.06.
- 1.6%CVE-2020-15707Medium
Integer overflows were discovered in the functions grub_cmd_initrd and grub_initrd_init in the efilinux component of GRUB2, as shipped in Debian, Red Hat, and Ubuntu (the functionality is not included in GRUB2...
- 1.4%CVE-2020-15705Medium
GRUB2 fails to validate kernel signature when booted directly without shim, allowing secure boot to be bypassed.
- 1.3%CVE-2022-28733High
Integer underflow in grub_net_recv_ip4_packets; A malicious crafted IP packet can lead to an integer underflow in grub_net_recv_ip4_packets() function on rsm->total_len value.
- 1.2%CVE-2020-25632High
A flaw was found in grub2 in versions prior to 2.06.
- 1.1%CVE-2022-28734High
Out-of-bounds write when handling split HTTP headers; When handling split HTTP headers, GRUB2 HTTP code accidentally moves its internal data buffer point by one position.
- 1.1%CVE-2015-8370High
Multiple integer underflows in Grub2 1.98 through 2.02 allow physically proximate attackers to bypass authentication, obtain sensitive information, or cause a denial of service (disk corruption) via backspace...
- 1.0%CVE-2022-3775High
When rendering certain unicode sequences, grub2's font code doesn't proper validate if the informed glyph's width and height is constrained within bitmap size.
- 1.0%CVE-2021-20225Medium
A flaw was found in grub2 in versions prior to 2.06.
Running Grub2? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 new flaw affects software Acme tracks
A flaw was found in grub2 in versions prior to 2.06, where it incorrectly enables the usage of the ACPI command when Secure Boot is enabled. This flaw allows an attacker with privileged access to craft a Secondary System Description Table (SSDT) containing code to overwrite the Linux kernel lockdown variable content directly into memory. The table is further loaded and executed by the kernel, defeating its Secure Boot lockdown and allowing the attacker to load unsigned code. The highest threat from this vulnerability is to data confidentiality and integrity, as well as system availability.
- Matched to
- Grub2 on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
We track 43 published vulnerabilities listed under the name Grub2, across 10 versions.
None of Grub2's vulnerabilities is on the list of flaws known to be exploited today.
Create a EdgeProtect account and track Grub2. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.