CVE Vulnerabilities

CVE-2022-25789

Use After Free

Published: Apr 11, 2022 | Modified: Apr 19, 2022
CVSS 3.x
7.8
HIGH
Source:
NVD
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
CVSS 2.x
6.8 MEDIUM
AV:N/AC:M/Au:N/C:P/I:P/A:P
RedHat/V2
RedHat/V3
Ubuntu

A maliciously crafted DWF, 3DS and DWFX files in Autodesk AutoCAD 2022, 2021, 2020, 2019 can be used to trigger use-after-free vulnerability. Exploitation of this vulnerability may lead to 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
Autocad Autodesk 2022 *
Autocad_architecture Autodesk 2022 *
Autocad_electrical Autodesk 2022 *
Autocad_map_3d Autodesk 2022 *
Autocad_mechanical Autodesk 2022 *
Autocad_mep Autodesk 2022 *
Autocad_plant_3d Autodesk 2022 *
Autocad_lt Autodesk 2022 *
Civil_3d Autodesk 2022 *
Advance_steel Autodesk 2022 *
Autocad Autodesk 2019 *
Autocad Autodesk 2020 *
Autocad Autodesk 2021 *
Autocad_architecture Autodesk 2019 *
Autocad_architecture Autodesk 2020 *
Autocad_architecture Autodesk 2021 *
Autocad_electrical Autodesk 2019 *
Autocad_electrical Autodesk 2020 *
Autocad_electrical Autodesk 2021 *
Autocad_map_3d Autodesk 2021 *
Autocad_map_3d Autodesk 2020 *
Autocad_map_3d Autodesk 2019 *
Autocad_mechanical Autodesk 2019 *
Autocad_mechanical Autodesk 2020 *
Autocad_mechanical Autodesk 2021 *
Autocad_mep Autodesk 2021 *
Autocad_mep Autodesk 2020 *
Autocad_mep Autodesk 2019 *
Autocad_plant_3d Autodesk 2019 *
Autocad_plant_3d Autodesk 2020 *
Autocad_plant_3d Autodesk 2021 *
Autocad_lt Autodesk 2021 *
Autocad_lt Autodesk 2020 *
Autocad_lt Autodesk 2019 *
Civil_3d Autodesk 2019 *
Civil_3d Autodesk 2020 *
Civil_3d Autodesk 2021 *
Advance_steel Autodesk 2019 *
Advance_steel Autodesk 2020 *
Advance_steel Autodesk 2021 *
Autocad Autodesk 2022 *

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