CVE Vulnerabilities

CVE-2023-29073

Heap-based Buffer Overflow

Published: Nov 23, 2023 | Modified: Nov 21, 2024
CVSS 3.x
9.8
CRITICAL
Source:
NVD
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CVSS 2.x
RedHat/V2
RedHat/V3
Ubuntu

A maliciously crafted MODEL file when parsed through Autodesk AutoCAD 2024 and 2023 can be used to cause a Heap-Based Buffer Overflow. A malicious actor can leverage this vulnerability to cause a crash, read sensitive data, or execute arbitrary code in the context of the current process.

Weakness

A heap overflow condition is a buffer overflow, where the buffer that can be overwritten is allocated in the heap portion of memory, generally meaning that the buffer was allocated using a routine such as malloc().

Affected Software

Name Vendor Start Version End Version
Autocad Autodesk * 2024.1 (excluding)
Autocad Autodesk 2023.0.0 (including) 2023.1.4 (excluding)
Autocad Autodesk 2024.0.0 (including) 2024.1.1 (excluding)
Autocad_advance_steel Autodesk * 2023.1.4 (excluding)
Autocad_advance_steel Autodesk 2024.0.0 (including) 2024.1.1 (excluding)
Autocad_architecture Autodesk * 2023.1.4 (excluding)
Autocad_architecture Autodesk 2024.0.0 (including) 2024.1.1 (excluding)
Autocad_civil_3d Autodesk * 2023.1.4 (excluding)
Autocad_civil_3d Autodesk 2024.0.0 (including) 2024.1.1 (excluding)
Autocad_electrical Autodesk * 2023.1.4 (excluding)
Autocad_electrical Autodesk 2024.0.0 (including) 2024.1.1 (excluding)
Autocad_lt Autodesk * 2023.1.4 (excluding)
Autocad_lt Autodesk * 2024.1 (excluding)
Autocad_lt Autodesk 2024.0.0 (including) 2024.1.1 (excluding)
Autocad_map_3d Autodesk * 2023.1.4 (excluding)
Autocad_map_3d Autodesk 2024.0.0 (including) 2024.1.1 (excluding)
Autocad_mechanical Autodesk * 2023.1.4 (excluding)
Autocad_mechanical Autodesk 2024.0.0 (including) 2024.1.1 (excluding)
Autocad_mep Autodesk * 2023.1.4 (excluding)
Autocad_mep Autodesk 2024.0.0 (including) 2024.1.1 (excluding)
Autocad_plant_3d Autodesk * 2023.1.4 (excluding)
Autocad_plant_3d Autodesk 2024.0.0 (including) 2024.1.1 (excluding)

Potential Mitigations

  • Use automatic buffer overflow detection mechanisms that are offered by certain compilers or compiler extensions. Examples include: the Microsoft Visual Studio /GS flag, Fedora/Red Hat FORTIFY_SOURCE GCC flag, StackGuard, and ProPolice, which provide various mechanisms including canary-based detection and range/index checking.
  • D3-SFCV (Stack Frame Canary Validation) from D3FEND [REF-1334] discusses canary-based detection in detail.
  • Run or compile the software using features or extensions that randomly arrange the positions of a program’s executable and libraries in memory. Because this makes the addresses unpredictable, it can prevent an attacker from reliably jumping to exploitable code.
  • Examples include Address Space Layout Randomization (ASLR) [REF-58] [REF-60] and Position-Independent Executables (PIE) [REF-64]. Imported modules may be similarly realigned if their default memory addresses conflict with other modules, in a process known as “rebasing” (for Windows) and “prelinking” (for Linux) [REF-1332] using randomly generated addresses. ASLR for libraries cannot be used in conjunction with prelink since it would require relocating the libraries at run-time, defeating the whole purpose of prelinking.
  • For more information on these techniques see D3-SAOR (Segment Address Offset Randomization) from D3FEND [REF-1335].

References