Описание
A local attacker with control over GRUB's configuration can bypass lockdown restrictions when booting with Secure Boot and load an unsigned GRUB module, while GRUB continues to report lockdown is enabled.
The vulnerability is caused by insufficient validation of the MMIO base address passed to the GRUB serial command. GRUB does not validate that the base address corresponds to a UART device, rather than being an arbitrary memory address. This allows an attacker to trick GRUB into writing non-arbitrary data at an attacker-controlled address, including resetting the grub_file_verifiers list in a way that disables the subsequent verification of loaded modules.
A flaw was found in GRUB2. The bootloader insufficiently validates memory addresses passed to the serial configuration command, allowing arbitrary system memory to be targeted instead of a legitimate serial communication device. A local attacker with control over GRUB's boot configuration can exploit this issue to overwrite internal verification structures. This vulnerability allows the attacker to bypass Secure Boot lockdown restrictions and load arbitrary unsigned modules during system boot.
Меры по смягчению последствий
There is no complete mitigation for this issue other than applying a fixed GRUB build; the underlying fix requires validating the UART/MMIO resource used by the serial command and making the module-verification path fail closed when the verifier list is empty under lockdown. Until a fixed build is available, exposure can be reduced by:
- Restricting who can modify or supply GRUB boot configuration (grub.cfg) and disallowing untrusted or attacker-controlled removable boot media.
- Avoiding use of the serial console/terminal_input during boot on systems relying on Secure Boot lockdown, where serial input is not otherwise required.
- Treating administrator-level control over boot configuration as equivalent to the ability to bypass lockdown module verification on affected GRUB builds, and applying the same access controls accordingly. These steps reduce the attack surface but do not close the underlying validation flaw; they do not help if the attacker already controls boot configuration or removable boot media.
Затронутые пакеты
| Платформа | Пакет | Состояние | Рекомендация | Релиз |
|---|---|---|---|---|
| Red Hat Enterprise Linux 10 | grub2 | Fix deferred | ||
| Red Hat Enterprise Linux 7 | grub2 | Fix deferred | ||
| Red Hat Enterprise Linux 8 | grub2 | Fix deferred | ||
| Red Hat Enterprise Linux 9 | grub2 | Fix deferred | ||
| Red Hat OpenShift Container Platform 4 | openshift/ose-rhel-coreos-8 | Fix deferred | ||
| Red Hat OpenShift Container Platform 4 | openshift/ose-rhel-coreos-9 | Fix deferred |
Показывать по
Дополнительная информация
Статус:
6.4 Medium
CVSS3
Связанные уязвимости
A local attacker with control over GRUB's configuration can bypass lockdown restrictions when booting with Secure Boot and load an unsigned GRUB module, while GRUB continues to report lockdown is enabled. The vulnerability is caused by insufficient validation of the MMIO base address passed to the GRUB serial command. GRUB does not validate that the base address corresponds to a UART device, rather than being an arbitrary memory address. This allows an attacker to trick GRUB into writing non-arbitrary data at an attacker-controlled address, including resetting the grub_file_verifiers list in a way that disables the subsequent verification of loaded modules.
A local attacker with control over GRUB's configuration can bypass lockdown restrictions when booting with Secure Boot and load an unsigned GRUB module, while GRUB continues to report lockdown is enabled. The vulnerability is caused by insufficient validation of the MMIO base address passed to the GRUB serial command. GRUB does not validate that the base address corresponds to a UART device, rather than being an arbitrary memory address. This allows an attacker to trick GRUB into writing non-arbitrary data at an attacker-controlled address, including resetting the grub_file_verifiers list in a way that disables the subsequent verification of loaded modules.
A local attacker with control over GRUB's configuration can bypass loc ...
A local attacker with control over GRUB's configuration can bypass lockdown restrictions when booting with Secure Boot and load an unsigned GRUB module, while GRUB continues to report lockdown is enabled. The vulnerability is caused by insufficient validation of the MMIO base address passed to the GRUB serial command. GRUB does not validate that the base address corresponds to a UART device, rather than being an arbitrary memory address. This allows an attacker to trick GRUB into writing non-arbitrary data at an attacker-controlled address, including resetting the grub_file_verifiers list in a way that disables the subsequent verification of loaded modules.
6.4 Medium
CVSS3