CVE Vulnerabilities

CVE-2022-28736

Use After Free

Published: Jul 20, 2023 | Modified: Aug 25, 2023
CVSS 3.x
7.8
HIGH
Source:
NVD
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CVSS 2.x
RedHat/V2
RedHat/V3
7 MODERATE
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
Ubuntu
MEDIUM

Theres a use-after-free vulnerability in grub_cmd_chainloader() function; The chainloader command is used to boot up operating systems that doesnt support multiboot and do not have direct support from GRUB2. When executing chainloader more than once a use-after-free vulnerability is triggered. If an attacker can control the GRUB2s memory allocation pattern sensitive data may be exposed and arbitrary code execution can be achieved.

Weakness

Referencing memory after it has been freed can cause a program to crash, use unexpected values, or execute code.

Affected Software

Name Vendor Start Version End Version
Grub2 Gnu 2.00 (including) 2.06-3 (excluding)
Red Hat Enterprise Linux 8 RedHat grub2-1:2.02-123.el8_6.8 *
Red Hat Enterprise Linux 8.1 Update Services for SAP Solutions RedHat grub2-1:2.02-87.el8_1.10 *
Red Hat Enterprise Linux 8.2 Extended Update Support RedHat grub2-1:2.02-87.el8_2.10 *
Red Hat Enterprise Linux 8.4 Extended Update Support RedHat grub2-1:2.02-99.el8_4.9 *
Red Hat Enterprise Linux 9 RedHat grub2-1:2.06-27.el9_0.7 *
Grub2 Ubuntu bionic *
Grub2 Ubuntu impish *
Grub2 Ubuntu upstream *
Grub2-signed Ubuntu bionic *
Grub2-signed Ubuntu esm-infra/xenial *
Grub2-signed Ubuntu focal *
Grub2-signed Ubuntu jammy *
Grub2-signed Ubuntu kinetic *
Grub2-signed Ubuntu trusty *
Grub2-signed Ubuntu xenial *
Grub2-unsigned Ubuntu bionic *
Grub2-unsigned Ubuntu esm-infra/xenial *
Grub2-unsigned Ubuntu focal *
Grub2-unsigned Ubuntu jammy *
Grub2-unsigned Ubuntu kinetic *
Grub2-unsigned Ubuntu trusty *
Grub2-unsigned Ubuntu xenial *

Extended Description

The use of previously-freed memory can have any number of adverse consequences, ranging from the corruption of valid data to the execution of arbitrary code, depending on the instantiation and timing of the flaw. The simplest way data corruption may occur involves the system’s reuse of the freed memory. Use-after-free errors have two common and sometimes overlapping causes:

In this scenario, the memory in question is allocated to another pointer validly at some point after it has been freed. The original pointer to the freed memory is used again and points to somewhere within the new allocation. As the data is changed, it corrupts the validly used memory; this induces undefined behavior in the process. If the newly allocated data happens to hold a class, in C++ for example, various function pointers may be scattered within the heap data. If one of these function pointers is overwritten with an address to valid shellcode, execution of arbitrary code can be achieved.

Potential Mitigations

References