Autodesk® Design Review, Autodesk® Advance…: Out-of-bounds Write
CVE-2022-33889 is a high-severity out-of-bounds write vulnerability in Autodesk® Design Review, Autodesk® Advance Steel, Autodesk® Civil 3D®, with a CVSS 3.1 base score of 7.8 out of 10. It can be exploited with local access to the system by an unauthenticated attacker, but only if a user takes part, for example by opening a link or file. Affected Autodesk® Design Review, Autodesk® Advance Steel, Autodesk® Civil 3D® versions: 2018, 2023, 2022. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 0.39% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update Autocad to 2022.1.3 or 2023.1.1, whichever matches your release line, or a later version.
- Update Autocad Advance Steel to 2022.1.3 or 2023.1.1, whichever matches your release line, or a later version.
- Update Autocad Architecture to 2022.1.3 or 2023.1.1, whichever matches your release line, or a later version.
- Read the advisory on autodesk.com for workarounds and exact fixed builds.
- Because the attack needs a user to take part, warn users about unexpected links and files related to this product until it is patched.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Autodesk® Design Review, Autodesk® Advance Steel, Autodesk® Civil 3D® | Autodesk® Design Review, Autodesk® Advance Steel, Autodesk® Civil 3D® | 2018, 2023, 2022 | Not stated |
| Autodesk | Autocad | before 2022.1.3; 2023.0.0 up to, but not including, 2023.1.1 | 2022.1.3, 2023.1.1 |
| Autodesk | Autocad Advance Steel | before 2022.1.3; 2023.0.0 up to, but not including, 2023.1.1 | 2022.1.3, 2023.1.1 |
| Autodesk | Autocad Architecture | before 2022.1.3; 2023.0.0 up to, but not including, 2023.1.1 | 2022.1.3, 2023.1.1 |
| Autodesk | Autocad Civil 3d | before 2022.1.3; 2023.0.0 up to, but not including, 2023.1.1 | 2022.1.3, 2023.1.1 |
| Autodesk | Autocad Electrical | before 2022.1.3; 2023.0.0 up to, but not including, 2023.1.1 | 2022.1.3, 2023.1.1 |
| Autodesk | Autocad Lt | before 2022.1.3; 2023.0.0 up to, but not including, 2023.1.1 | 2022.1.3, 2023.1.1 |
| Autodesk | Autocad Map 3d | before 2022.1.3; 2023.0.0 up to, but not including, 2023.1.1 | 2022.1.3, 2023.1.1 |
| Autodesk | Autocad Mechanical | before 2022.1.3; 2023.0.0 up to, but not including, 2023.1.1 | 2022.1.3, 2023.1.1 |
| Autodesk | Autocad Mep | before 2022.1.3; 2023.0.0 up to, but not including, 2023.1.1 | 2022.1.3, 2023.1.1 |
| Autodesk | Autocad Plant 3d | before 2022.1.3; 2023.0.0 up to, but not including, 2023.1.1 | 2022.1.3, 2023.1.1 |
| Autodesk | Design Review | before 2018; 2018 | 2018 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- LocalThe attacker needs local access or must trick a user into running something.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- RequiredA user must take an action such as opening a file or link.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H. Scored by NVD.
Official description
A maliciously crafted GIF or JPEG files when parsed through Autodesk Design Review 2018, and AutoCAD 2023 and 2022 could be used to write beyond the allocated heap buffer. This vulnerability could lead to arbitrary code execution.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Out-of-bounds Write
The product writes data past the end, or before the beginning, of the intended buffer.
How developers prevent this class of flaw
- Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, many languages that perform their own memory management, such as Java and Perl, are not subject to buffer overflows. Other languages, such as Ada and C#, typically provide overflow protection, but the protection can be disabled by the programmer. Be wary that a language's interface to native code may still be subject to overflows, even if the language itself is theoretically safe.
- Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. Examples include the Safe C String Library (SafeStr) by Messier and Viega, and the Strsafe.h library from Microsoft. These libraries provide safer versions of overflow-prone string-handling functions.
- 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 discusses canary-based detection in detail.
Timeline
- CVE record published.
- Record last changed materially (score, affected products, status or references).
References
Recent Out-of-bounds Write vulnerabilities
- 7.8 High severity
- 7.8 High severity
- 7.8 High severity
- 7.8 High severity
- 7.8 High severity
- 9.1 Critical severity
Spotted an error? Tell us.