Safety instructions for AMI-SA-2023009 LogoFail

From Thomas-Krenn-Wiki
Jump to navigation Jump to search

With the help of prepared bootlogos, safety mechanisms such as Secure Boot can be bypassed due to a UEFI vulnerability ("LogoFail"). Staff of the IT security company Binarly presented details about this vulnerability at the Black Hat Europe Conference on December 6, 2023.[1][2][3]

Background information

Potential attackers may execute malicious codes and bypass security mechanisms such as Secure Boot by manipulating bootlogos.

There are two different ways to use bootlogos:

  • Normally, bootlogos are stored in the BIOS image. Normal users can not change them. Administrator rights are required for the installation of a new BIOS image with a modified logo.
  • Alternatively, on some systems, bootlogs can be stored in the EFI system partitions (for example as "\EFI\OEM\Logo.jpg"). Operating systems only allow administrator writing access in case of emergency.

Updates for products of Thomas-Krenn

You will find updates for the corresponding system in the download area of Thomas-Krenn as soon as available.

More information

References


Author: Werner Fischer

Werner Fischer, working in the Knowledge Transfer team at Thomas-Krenn, completed his studies of Computer and Media Security at FH Hagenberg in Austria. He is a regular speaker at many conferences like LinuxTag, OSMC, OSDC, LinuxCon, and author for various IT magazines. In his spare time he enjoys playing the piano and training for a good result at the annual Linz marathon relay.


Translator: Alina Ranzinger

Alina has been working at Thomas-Krenn.AG since 2024. After her training as multilingual business assistant, she got her job as assistant of the Product Management and is responsible for the translation of texts and for the organisation of the department.


Related articles

Creating a log file for the RI2212+
Installation NICCLI under Proxmox VE
Reading out BIOS image Intel microcodes and Intel firmware versions