CVE Vulnerabilities

CVE-2024-25062

Use After Free

Published: Feb 04, 2024 | Modified: Feb 13, 2024
CVSS 3.x
7.5
HIGH
Source:
NVD
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
CVSS 2.x
RedHat/V2
RedHat/V3
7.5 MODERATE
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Ubuntu
MEDIUM

An issue was discovered in libxml2 before 2.11.7 and 2.12.x before 2.12.5. When using the XML Reader interface with DTD validation and XInclude expansion enabled, processing crafted XML documents can lead to an xmlValidatePopElement use-after-free.

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
Libxml2 Xmlsoft * 2.11.7 (excluding)
Libxml2 Xmlsoft 2.12.0 (including) 2.12.5 (excluding)
Libxml2 Ubuntu bionic *
Libxml2 Ubuntu devel *
Libxml2 Ubuntu esm-infra/bionic *
Libxml2 Ubuntu esm-infra/xenial *
Libxml2 Ubuntu focal *
Libxml2 Ubuntu jammy *
Libxml2 Ubuntu mantic *
Libxml2 Ubuntu trusty *
Libxml2 Ubuntu trusty/esm *
Libxml2 Ubuntu xenial *
Red Hat Enterprise Linux 8 RedHat libxml2-0:2.9.7-18.el8_10.1 *
Red Hat Enterprise Linux 8 RedHat libxml2-0:2.9.7-18.el8_10.1 *
Red Hat Enterprise Linux 8.6 Extended Update Support RedHat libxml2-0:2.9.7-13.el8_6.5 *
Red Hat Enterprise Linux 8.8 Extended Update Support RedHat libxml2-0:2.9.7-16.el8_8.4 *
Red Hat Enterprise Linux 9 RedHat libxml2-0:2.9.13-6.el9_4 *
Red Hat Enterprise Linux 9 RedHat libxml2-0:2.9.13-6.el9_4 *
Red Hat Enterprise Linux 9.2 Extended Update Support RedHat libxml2-0:2.9.13-3.el9_2.3 *
Red Hat JBoss Core Services 1 RedHat libxml2 *

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