CVE-2022-25792NVD status: Modified
Autodesk Advanced Steel, Civil 3D, AutoCAD…: Out-of-bounds Write
CVE-2022-25792 is a high-severity out-of-bounds write vulnerability in Autodesk Advanced Steel, Civil 3D, AutoCAD, AutoCAD LT, AutoCAD Architecture, AutoCAD Electrical, AutoCAD Map 3D, AutoCAD Mechanical, AutoCAD MEP, AutoCAD Plant 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 Advanced Steel, Civil 3D, AutoCAD, AutoCAD LT, AutoCAD Architecture, AutoCAD Electrical, AutoCAD Map 3D, AutoCAD Mechanical, AutoCAD MEP, AutoCAD Plant 3D versions: 2022.1.1. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 1.56% chance of exploitation within 30 days, higher than 76% of scored CVEs.
Next patch cycle
High severity with no evidence of exploitation so far.
What to do
- Update Advance Steel to 2019.1.4 or 2020.1.5 or 2021.1.2 or 2022.1.2, whichever matches your release line, or a later version.
- Update Autocad to 2019.1.4 or 2020.1.5 or 2021.1.2 or 2022.1.2, whichever matches your release line, or a later version.
- Update Autocad Architecture to 2019.1.4 or 2020.1.5 or 2021.1.2 or 2022.1.2, 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 Advanced Steel, Civil 3D, AutoCAD, AutoCAD LT, AutoCAD Architecture, AutoCAD Electrical, AutoCAD Map 3D, AutoCAD Mechanical, AutoCAD MEP, AutoCAD Plant 3D | Autodesk Advanced Steel, Civil 3D, AutoCAD, AutoCAD LT, AutoCAD Architecture, AutoCAD Electrical, AutoCAD Map 3D, AutoCAD Mechanical, AutoCAD MEP, AutoCAD Plant 3D | 2022.1.1 | Not stated |
| Autodesk | Advance Steel | 2019 up to, but not including, 2019.1.4; 2020 up to, but not including, 2020.1.5; 2021 up to, but not including, 2021.1.2; 2022 up to, but not including, 2022.1.2 | 2019.1.4, 2020.1.5, 2021.1.2, 2022.1.2 |
| Autodesk | Autocad | 2019 up to, but not including, 2019.1.4; 2020 up to, but not including, 2020.1.5; 2021 up to, but not including, 2021.1.2; 2022 up to, but not including, 2022.1.2; 2022 up to, but not including, 2022.2.2 | 2019.1.4, 2020.1.5, 2021.1.2, 2022.1.2, 2022.2.2 |
| Autodesk | Autocad Architecture | 2019 up to, but not including, 2019.1.4; 2020 up to, but not including, 2020.1.5; 2021 up to, but not including, 2021.1.2; 2022 up to, but not including, 2022.1.2 | 2019.1.4, 2020.1.5, 2021.1.2, 2022.1.2 |
| Autodesk | Autocad Electrical | 2019 up to, but not including, 2019.1.4; 2020 up to, but not including, 2020.1.5; 2021 up to, but not including, 2021.1.2; 2022 up to, but not including, 2022.1.2 | 2019.1.4, 2020.1.5, 2021.1.2, 2022.1.2 |
| Autodesk | Autocad Lt | 2019 up to, but not including, 2019.1.4; 2020 up to, but not including, 2020.1.5; 2021 up to, but not including, 2021.1.2; 2022 up to, but not including, 2022.1.2 | 2019.1.4, 2020.1.5, 2021.1.2, 2022.1.2 |
| Autodesk | Autocad Map 3d | 2019 up to, but not including, 2019.1.4; 2020 up to, but not including, 2020.1.5; 2021 up to, but not including, 2021.1.2; 2022 up to, but not including, 2022.1.2 | 2019.1.4, 2020.1.5, 2021.1.2, 2022.1.2 |
| Autodesk | Autocad Mechanical | 2019 up to, but not including, 2019.1.4; 2020 up to, but not including, 2020.1.5; 2021 up to, but not including, 2021.1.2; 2022 up to, but not including, 2022.1.2 | 2019.1.4, 2020.1.5, 2021.1.2, 2022.1.2 |
| Autodesk | Autocad Mep | 2019 up to, but not including, 2019.1.4; 2020 up to, but not including, 2020.1.5; 2021 up to, but not including, 2021.1.2; 2022 up to, but not including, 2022.1.2 | 2019.1.4, 2020.1.5, 2021.1.2, 2022.1.2 |
| Autodesk | Autocad Plant 3d | 2019 up to, but not including, 2019.1.4; 2020 up to, but not including, 2020.1.5; 2021 up to, but not including, 2021.1.2; 2022 up to, but not including, 2022.1.2 | 2019.1.4, 2020.1.5, 2021.1.2, 2022.1.2 |
| Autodesk | Civil 3d | 2019 up to, but not including, 2019.1.4; 2020 up to, but not including, 2020.1.5; 2021 up to, but not including, 2021.1.2; 2022 up to, but not including, 2022.1.2 | 2019.1.4, 2020.1.5, 2021.1.2, 2022.1.2 |
| Autodesk | Navisworks | 2022 up to, but not including, 2022.2 | 2022.2 |
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.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 7.8 | High | NVD |
| CVSS 2.0 | 6.8 | Medium | NVD |
Official description
A maliciously crafted DXF file in Autodesk AutoCAD 2022, 2021, 2020, 2019 and Autodesk Navisworks 2022 can be used to write beyond the allocated buffer through Buffer overflow vulnerability. This vulnerability can be exploited to execute arbitrary code.
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
Other vulnerabilities in Autodesk Advanced Steel, Civil 3D, AutoCAD, AutoCAD LT, AutoCAD Architecture, AutoCAD Electrical, AutoCAD Map 3D, AutoCAD Mechanical, AutoCAD MEP, AutoCAD Plant 3D
- 7.8 High severity
- 7.8 High severity
- 7.8 High severity
- 7.8 High severity
- 7.8 High severity
- 7.8 High severity
Recent Out-of-bounds Write vulnerabilities
- 7.2 High severity
- 7.2 High severity
- 9.8 Critical severity
- 9.8 Critical severity
- 9.8 Critical severity
- 9.8 Critical severity
Spotted an error? Tell us.