CVE-2021-3418

grub2: grub 2.05 reintroduced CVE-2020-15705

Published Mar 15, 2021 CVSS 3.1 · 6.4 Medium EPSS < 1% KEV · Not listed
Description
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.

Remediation

No solution or workaround provided in the CVE record

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
EUVD EUVD EUVD-2021-26746 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.
History

No history.

Weaknesses

Sources

Status
PUBLISHED
Assigner
redhat
Published
Updated
Aug 3, 2024, 4:53 PM
Reserved
Mar 1, 2021, 12:00 AM
Status
Modified
Published
Mar 15, 2021, 10:15 PM
Modified
Jun 17, 2026, 4:05 AM
Severity
Moderate
Public date
Mar 2, 2021, 6:00 PM