CVE-2021-3418
First published: Mon Mar 01 2021(Updated: )
If certificates that signed grub are installed into db, grub can be booted directly. It will then boot any kernel without signature validation. The booted kernel will think it was booted in secureboot mode and will implement lockdown, yet it could have been tampered. This flaw is a reintroduction of CVE-2020-15705 and only affects grub2 versions prior to 2.06 and upstream and distributions using the shim_lock mechanism.
Credit: secalert@redhat.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| redhat/grub | <2.06 | 2.06 |
| Gnu Grub2 | <2.06 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is CVE-2021-3418?
CVE-2021-3418 is a vulnerability that allows grub to be booted directly without signature validation, potentially leading to tampered kernels being loaded.
What is the severity of CVE-2021-3418?
CVE-2021-3418 has a severity value of 6.4, which is considered medium.
Which software is affected by CVE-2021-3418?
Grub versions up to and excluding 2.06 are affected by CVE-2021-3418.
How can I fix CVE-2021-3418?
You can fix CVE-2021-3418 by updating Grub to version 2.06 or above.
Where can I find more information about CVE-2021-3418?
You can find more information about CVE-2021-3418 on the Red Hat Bugzilla and Red Hat Security Advisories websites.
- collector/nvd-index
- agent/type
- agent/softwarecombine
- agent/first-publish-date
- collector/mitre-cve
- source/MITRE
- agent/author
- agent/severity
- agent/last-modified-date
- agent/references
- agent/weakness
- agent/description
- agent/tags
- agent/event
- collector/redhat-bugzilla
- source/Red Hat
- alias/CVE-2021-3418
- agent/software-canonical-lookup
- vendor/gnu
- canonical/gnu grub2
- package-manager/redhat