CVE-2021-3418: Medium severity GNU GRUB2 vulnerability

Published Mar 1, 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 shimlock mechanism.

Other sources

The GRUB2 upstream version reintroduced the CVE-2020-15705. This refers to a distro specific flaw which made upstream in the mentioned version.

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 only affects upstream and distributions using the shimlock mechanism.

Red Hat

Affected Software

2 affected componentsFixes available
redhat/grub<2.06
2.06
GNU GRUB2<2.06

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade redhat/grub to a version that resolves this vulnerability.

    Fixed in 2.06
  2. Upgrade

    Upgrade GRUB2 (upstream) to a version that resolves this vulnerability.

    Fixed in 2.06
  3. Compensating control

    Ensure GRUB2 is not bootable without signature validation by avoiding installing certificates that signed GRUB into db (i.e., do not place GRUB-signer certificates in UEFI db).

  4. Operational

    Reboot/verify the system boot chain after upgrading to GRUB2 2.06 to ensure the kernel is not booted without signature validation and that lockdown behavior corresponds to an untampered boot state.

Event History

Mar 15, 2021
CVE Published
via MITRE·09:17 PM
Data Sourced
via MITRE·09:17 PM
DescriptionWeakness
Data Sourced
via NVD·10:15 PM
DescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

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.

2

What is the severity of CVE-2021-3418?

CVE-2021-3418 has a severity value of 6.4, which is considered medium.

3

Which software is affected by CVE-2021-3418?

Grub versions up to and excluding 2.06 are affected by CVE-2021-3418.

4

How can I fix CVE-2021-3418?

You can fix CVE-2021-3418 by updating Grub to version 2.06 or above.

5

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.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203