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.
References
Link | Resource |
---|---|
https://bugzilla.redhat.com/show_bug.cgi?id=1933757 | Issue Tracking Third Party Advisory |
https://bugzilla.redhat.com/show_bug.cgi?id=1933757 | Issue Tracking Third Party Advisory |
Configurations
History
21 Nov 2024, 06:21
Type | Values Removed | Values Added |
---|---|---|
References | () https://bugzilla.redhat.com/show_bug.cgi?id=1933757 - Issue Tracking, Third Party Advisory |
Information
Published : 2021-03-15 22:15
Updated : 2024-11-21 06:21
NVD link : CVE-2021-3418
Mitre link : CVE-2021-3418
CVE.ORG link : CVE-2021-3418
JSON object : View
Products Affected
gnu
- grub2
CWE
CWE-281
Improper Preservation of Permissions