A maliciously crafted DWG file when parsed through Autodesk DWG TrueView can be used to cause a Stack-based 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 stack-based buffer overflow condition is a condition where the buffer being overwritten is allocated on the stack (i.e., is a local variable or, rarely, a parameter to a function).
Affected Software
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Advance_steel | Autodesk | 2021 (including) | 2021.1.4 (excluding) |
| Advance_steel | Autodesk | 2022 (including) | 2022.1.4 (excluding) |
| Advance_steel | Autodesk | 2023 (including) | 2023.1.5 (excluding) |
| Advance_steel | Autodesk | 2024 (including) | 2024.1.3 (excluding) |
| Autocad | Autodesk | 2021 (including) | 2021.1.4 (excluding) |
| Autocad | Autodesk | 2022 (including) | 2022.1.4 (excluding) |
| Autocad | Autodesk | 2022 (including) | 2022.4.1 (excluding) |
| Autocad | Autodesk | 2023 (including) | 2023.1.5 (excluding) |
| Autocad | Autodesk | 2023 (including) | 2023.3.1 (excluding) |
| Autocad | Autodesk | 2024 (including) | 2024.1.2 (excluding) |
| Autocad | Autodesk | 2024 (including) | 2024.1.3 (excluding) |
| Autocad_architecture | Autodesk | 2021 (including) | 2021.1.4 (excluding) |
| Autocad_architecture | Autodesk | 2022 (including) | 2022.1.4 (excluding) |
| Autocad_architecture | Autodesk | 2023 (including) | 2023.1.5 (including) |
| Autocad_architecture | Autodesk | 2024 (including) | 2024.1.3 (excluding) |
| Autocad_electrical | Autodesk | 2021 (including) | 2021.1.4 (excluding) |
| Autocad_electrical | Autodesk | 2022 (including) | 2022.1.4 (excluding) |
| Autocad_electrical | Autodesk | 2023 (including) | 2023.1.5 (excluding) |
| Autocad_electrical | Autodesk | 2024 (including) | 2024.1.3 (excluding) |
| Autocad_lt | Autodesk | 2021 (including) | 2021.1.4 (excluding) |
| Autocad_lt | Autodesk | 2022 (including) | 2022.1.4 (excluding) |
| Autocad_lt | Autodesk | 2022 (including) | 2022.4.1 (excluding) |
| Autocad_lt | Autodesk | 2023 (including) | 2023.1.5 (excluding) |
| Autocad_lt | Autodesk | 2023 (including) | 2023.3.1 (excluding) |
| Autocad_lt | Autodesk | 2024 (including) | 2024.1.2 (excluding) |
| Autocad_lt | Autodesk | 2024 (including) | 2024.1.3 (excluding) |
| Autocad_map_3d | Autodesk | 2021 (including) | 2021.1.4 (excluding) |
| Autocad_map_3d | Autodesk | 2022 (including) | 2022.1.4 (excluding) |
| Autocad_map_3d | Autodesk | 2023 (including) | 2023.1.5 (excluding) |
| Autocad_map_3d | Autodesk | 2024 (including) | 2024.1.3 (excluding) |
| Autocad_mechanical | Autodesk | 2021 (including) | 2021.1.4 (excluding) |
| Autocad_mechanical | Autodesk | 2022 (including) | 2022.1.4 (excluding) |
| Autocad_mechanical | Autodesk | 2023 (including) | 2023.1.5 (excluding) |
| Autocad_mechanical | Autodesk | 2024 (including) | 2024.1.3 (excluding) |
| Autocad_mep | Autodesk | 2021 (including) | 2021.1.4 (excluding) |
| Autocad_mep | Autodesk | 2022 (including) | 2022.1.4 (excluding) |
| Autocad_mep | Autodesk | 2023 (including) | 2023.15 (excluding) |
| Autocad_mep | Autodesk | 2024 (including) | 2024.1.3 (excluding) |
| Autocad_plant_3d | Autodesk | 2021 (including) | 2021.1.4 (excluding) |
| Autocad_plant_3d | Autodesk | 2022 (including) | 2022.1.4 (excluding) |
| Autocad_plant_3d | Autodesk | 2023 (including) | 2023.1.5 (excluding) |
| Autocad_plant_3d | Autodesk | 2024 (including) | 2024.1.3 (excluding) |
| Civil_3d | Autodesk | 2021 (including) | 2021.1.4 (excluding) |
| Civil_3d | Autodesk | 2022 (including) | 2022.1.4 (excluding) |
| Civil_3d | Autodesk | 2023 (including) | 2023.1.5 (excluding) |
| Civil_3d | Autodesk | 2024 (including) | 2024.1.3 (excluding) |
| Dwg_trueview | Autodesk | 2022 (including) | 2022.1.4 (excluding) |
| Dwg_trueview | Autodesk | 2023 (including) | 2023.1.5 (excluding) |
| Dwg_trueview | Autodesk | 2024 (including) | 2024.1.3 (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].