CVE Vulnerabilities

CVE-2018-14424

Use After Free

Published: Aug 14, 2018 | Modified: Nov 21, 2024
CVSS 3.x
7.8
HIGH
Source:
NVD
CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CVSS 2.x
4.6 MEDIUM
AV:L/AC:L/Au:N/C:P/I:P/A:P
RedHat/V2
RedHat/V3
7.3 MODERATE
CVSS:3.0/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H
Ubuntu
MEDIUM

The daemon in GDM through 3.29.1 does not properly unexport display objects from its D-Bus interface when they are destroyed, which allows a local attacker to trigger a use-after-free via a specially crafted sequence of D-Bus method calls, resulting in a denial of service or potential code execution.

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
Gnome_display_manager Gnome * 3.29.1 (including)
Gdm3 Ubuntu bionic *
Gdm3 Ubuntu cosmic *
Gdm3 Ubuntu devel *
Gdm3 Ubuntu disco *
Gdm3 Ubuntu eoan *
Gdm3 Ubuntu esm-apps/xenial *
Gdm3 Ubuntu focal *
Gdm3 Ubuntu groovy *
Gdm3 Ubuntu hirsute *
Gdm3 Ubuntu impish *
Gdm3 Ubuntu jammy *
Gdm3 Ubuntu kinetic *
Gdm3 Ubuntu lunar *
Gdm3 Ubuntu mantic *
Gdm3 Ubuntu noble *
Gdm3 Ubuntu oracular *
Gdm3 Ubuntu upstream *
Gdm3 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