First published: Mon Jul 27 2020(Updated: )
GRUB2 fails to validate kernel signature when booted directly without shim, allowing secure boot to be bypassed. This only affects systems where the kernel signing certificate has been imported directly into the secure boot database and the GRUB image is booted directly without the use of shim. This issue affects GRUB2 version 2.04 and prior versions.
Credit: security@ubuntu.com security@ubuntu.com
Affected Software | Affected Version | How to fix |
---|---|---|
redhat/fwupdate | <0:12-6.el7_8 | 0:12-6.el7_8 |
redhat/grub2 | <1:2.02-0.86.el7_8 | 1:2.02-0.86.el7_8 |
redhat/shim | <0:15-7.el7_9 | 0:15-7.el7_9 |
redhat/shim-signed | <0:15-7.el7_8 | 0:15-7.el7_8 |
redhat/grub2 | <1:2.02-0.86.el7_2 | 1:2.02-0.86.el7_2 |
redhat/shim | <0:15-8.el7 | 0:15-8.el7 |
redhat/shim-signed | <0:15-8.el7_2 | 0:15-8.el7_2 |
redhat/grub2 | <1:2.02-0.86.el7 | 1:2.02-0.86.el7 |
redhat/shim-signed | <0:15-8.el7_3 | 0:15-8.el7_3 |
redhat/fwupdate | <0:9-10.el7_4 | 0:9-10.el7_4 |
redhat/grub2 | <1:2.02-0.86.el7_4 | 1:2.02-0.86.el7_4 |
redhat/shim-signed | <0:15-8.el7_4 | 0:15-8.el7_4 |
redhat/fwupdate | <0:12-6.el7_6 | 0:12-6.el7_6 |
redhat/grub2 | <1:2.02-0.86.el7_6 | 1:2.02-0.86.el7_6 |
redhat/shim-signed | <0:15-8.el7_6 | 0:15-8.el7_6 |
redhat/fwupdate | <0:12-6.el7_7 | 0:12-6.el7_7 |
redhat/grub2 | <1:2.02-0.86.el7_7 | 1:2.02-0.86.el7_7 |
redhat/shim-signed | <0:15-8.el7_7 | 0:15-8.el7_7 |
redhat/fwupd | <0:1.1.4-7.el8_2 | 0:1.1.4-7.el8_2 |
redhat/grub2 | <1:2.02-87.el8_2 | 1:2.02-87.el8_2 |
redhat/shim | <0:15-14.el8_2 | 0:15-14.el8_2 |
redhat/shim-unsigned-x64 | <0:15-7.el8 | 0:15-7.el8 |
redhat/fwupd | <0:1.1.4-2.el8_0 | 0:1.1.4-2.el8_0 |
redhat/grub2 | <1:2.02-87.el8_0 | 1:2.02-87.el8_0 |
redhat/shim | <0:15-14.el8_0 | 0:15-14.el8_0 |
redhat/fwupd | <0:1.1.4-2.el8_1 | 0:1.1.4-2.el8_1 |
redhat/grub2 | <1:2.02-87.el8_1 | 1:2.02-87.el8_1 |
redhat/shim | <0:15-14.el8_1 | 0:15-14.el8_1 |
redhat/grub | <2.06 | 2.06 |
Gnu Grub2 | <=2.04 | |
Redhat Enterprise Linux Atomic Host | ||
Redhat Openshift Container Platform | =4.0 | |
Canonical Ubuntu Linux | =14.04 | |
Canonical Ubuntu Linux | =16.04 | |
Canonical Ubuntu Linux | =18.04 | |
Canonical Ubuntu Linux | =20.04 | |
Debian Debian Linux | =10.0 | |
openSUSE Leap | =15.1 | |
openSUSE Leap | =15.2 | |
Redhat Enterprise Linux | =7.0 | |
Redhat Enterprise Linux | =8.0 | |
SUSE SUSE Linux Enterprise Server | =11 | |
SUSE SUSE Linux Enterprise Server | =12 | |
SUSE SUSE Linux Enterprise Server | =15 | |
Microsoft Windows 10 | ||
Microsoft Windows 10 | =1607 | |
Microsoft Windows 10 | =1709 | |
Microsoft Windows 10 | =1803 | |
Microsoft Windows 10 | =1809 | |
Microsoft Windows 10 | =1903 | |
Microsoft Windows 10 | =1909 | |
Microsoft Windows 10 | =2004 | |
Microsoft Windows 8.1 | ||
Microsoft Windows RT 8.1 | ||
Microsoft Windows Server 2012 | ||
Microsoft Windows Server 2012 | =r2 | |
Microsoft Windows Server 2016 | ||
Microsoft Windows Server 2016 | =1903 | |
Microsoft Windows Server 2016 | =1909 | |
Microsoft Windows Server 2016 | =2004 | |
Microsoft Windows Server 2019 | ||
debian/grub2 | 2.06-3~deb11u6 2.06-13+deb12u1 2.12-5 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
(Appears in the following advisories)
The vulnerability ID for this issue is CVE-2020-15705.
The severity of CVE-2020-15705 is medium (6.4).
This vulnerability affects systems where the kernel signing certificate has been imported directly into the secure boot database and the GRUB image is booted directly without the use of shim.
This vulnerability allows secure boot to be bypassed by failing to validate kernel signature when booted directly without shim.
You can find more information about CVE-2020-15705 on the Red Hat website (https://access.redhat.com/security/cve/cve-2020-15705).