RHSA-2022:5099: Important: grub2, mokutil, shim, and shim-unsigned-x64 security update
The grub2 packages provide version 2 of the Grand Unified Boot Loader (GRUB), a highly configurable and customizable boot loader with modular architecture. The packages support a variety of kernel formats, file systems, computer architectures, and hardware devices.The shim package contains a first-stage UEFI boot loader that handles chaining to a trusted full boot loader under secure boot environments.Security Fix(es): grub2: Integer underflow in grubnetrecvip4packets (CVE-2022-28733) grub2: Crafted PNG grayscale images may lead to out-of-bounds write in heap (CVE-2021-3695) grub2: Crafted PNG image may lead to out-of-bound write during huffman table handling (CVE-2021-3696) grub2: Crafted JPEG image can lead to buffer underflow write in the heap (CVE-2021-3697) grub2: Out-of-bound write when handling split HTTP headers (CVE-2022-28734) grub2: shimlock verifier allows non-kernel files to be loaded (CVE-2022-28735) grub2: use-after-free in grubcmdchainloader() (CVE-2022-28736) shim: Buffer overflow when loading crafted EFI images (CVE-2022-28737) For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of RHSA-2022:5099?
The severity of RHSA-2022:5099 is classified as important.
How do I fix RHSA-2022:5099?
To fix RHSA-2022:5099, update the affected grub2, mokutil, and shim packages to the specified versions provided in the advisory.
Which packages are affected by RHSA-2022:5099?
Affected packages include grub2, grub2-common, mokutil, and shim with specific version constraints.
What vulnerabilities does RHSA-2022:5099 address?
RHSA-2022:5099 addresses various vulnerabilities related to the GRUB boot loader which could potentially allow unauthorized access or system compromise.
Is there a workaround for RHSA-2022:5099?
Officially, no workaround is provided for RHSA-2022:5099; applying the recommended updates is the advised solution.