Autodesk products: Integer Overflow or Wraparound
CVE-2023-25004 is a high-severity integer overflow or wraparound vulnerability in Autodesk products, 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 products versions: 2023, 2022, 2021, 2020. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 0.24% 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 Alias to 2023.1.1 or a later version.
- Update Autocad to 2020.1.6 or 2021.1.3 or 2022.1.3 or 2023.1.1, whichever matches your release line, or a later version.
- Update Autocad Advance Steel to 2020.1.6 or 2021.1.3 or 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 products | Autodesk products | 2023, 2022, 2021, 2020 | Not stated |
| Autodesk | Alias | 2023 up to, but not including, 2023.1.1 | 2023.1.1 |
| Autodesk | Autocad | 2020 up to, but not including, 2020.1.6; 2021 up to, but not including, 2021.1.3; 2022 up to, but not including, 2022.1.3; 2023 up to, but not including, 2023.1.1 | 2020.1.6, 2021.1.3, 2022.1.3, 2023.1.1 |
| Autodesk | Autocad Advance Steel | 2020 up to, but not including, 2020.1.6; 2021 up to, but not including, 2021.1.3; 2022 up to, but not including, 2022.1.3; 2023 up to, but not including, 2023.1.1 | 2020.1.6, 2021.1.3, 2022.1.3, 2023.1.1 |
| Autodesk | Autocad Architecture | 2020 up to, but not including, 2020.1.6; 2021 up to, but not including, 2021.1.3; 2022 up to, but not including, 2022.1.3; 2023 up to, but not including, 2023.1.1 | 2020.1.6, 2021.1.3, 2022.1.3, 2023.1.1 |
| Autodesk | Autocad Civil 3d | 2020 up to, but not including, 2020.1.6; 2021 up to, but not including, 2021.1.3; 2022 up to, but not including, 2022.1.3; 2023 up to, but not including, 2023.1.1 | 2020.1.6, 2021.1.3, 2022.1.3, 2023.1.1 |
| Autodesk | Autocad Electrical | 2020 up to, but not including, 2020.1.6; 2021 up to, but not including, 2021.1.3; 2022 up to, but not including, 2022.1.3; 2023 up to, but not including, 2023.1.1 | 2020.1.6, 2021.1.3, 2022.1.3, 2023.1.1 |
| Autodesk | Autocad Lt | 2020 up to, but not including, 2020.1.6; 2021 up to, but not including, 2021.1.3; 2022 up to, but not including, 2022.1.3; 2023 up to, but not including, 2023.1.1 | 2020.1.6, 2021.1.3, 2022.1.3, 2023.1.1 |
| Autodesk | Autocad Map 3d | 2020 up to, but not including, 2020.1.6; 2021 up to, but not including, 2021.1.3; 2022 up to, but not including, 2022.1.3; 2023 up to, but not including, 2023.1.1 | 2020.1.6, 2021.1.3, 2022.1.3, 2023.1.1 |
| Autodesk | Autocad Mechanical | 2020 up to, but not including, 2020.1.6; 2021 up to, but not including, 2021.1.3; 2022 up to, but not including, 2022.1.3; 2023 up to, but not including, 2023.1.1 | 2020.1.6, 2021.1.3, 2022.1.3, 2023.1.1 |
| Autodesk | Autocad Mep | 2020 up to, but not including, 2020.1.6; 2021 up to, but not including, 2021.1.3; 2022 up to, but not including, 2022.1.3; 2023 up to, but not including, 2023.1.1 | 2020.1.6, 2021.1.3, 2022.1.3, 2023.1.1 |
| Autodesk | Autocad Plant 3d | 2020 up to, but not including, 2020.1.6; 2021 up to, but not including, 2021.1.3; 2022 up to, but not including, 2022.1.3; 2023 up to, but not including, 2023.1.1 | 2020.1.6, 2021.1.3, 2022.1.3, 2023.1.1 |
| Autodesk | Infraworks | 2021 up to, but not including, 2021.2; 2022 up to, but not including, 2022.1; 2023 up to, but not including, 2023.1 | 2021.2, 2022.1, 2023.1 |
| Autodesk | Inventor | 2021 up to, but not including, 2021.5; 2022 up to, but not including, 2022.4; 2023 up to, but not including, 2023.3.1 | 2021.5, 2022.4, 2023.3.1 |
| Autodesk | Maya Usd | 2022 up to, but not including, 2022.5; 2023 up to, but not including, 2023.3 | 2022.5, 2023.3 |
| Autodesk | Navisworks | 2022 up to, but not including, 2022.4; 2023 up to, but not including, 2023.2 | 2022.4, 2023.2 |
| Autodesk | Revit | 2021 up to, but not including, 2021.1.8 | 2021.1.8 |
| Autodesk | Vred | 2023 up to, but not including, 2023.4 | 2023.4 |
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 pskernel.dll file in Autodesk products is used to trigger integer overflow vulnerabilities. Exploitation of these vulnerabilities may lead to code execution.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Integer Overflow or Wraparound
The product performs a calculation that can produce an integer overflow or wraparound when the logic assumes that the resulting value will always be larger than the original value. This occurs when an integer value is incremented to a value that is too large to store in the associated representation. When this occurs, the value may become a very small or negative number.
How developers prevent this class of flaw
- Ensure that all protocols are strictly defined, such that all out-of-bounds behavior can be identified simply, and require strict conformance to the protocol.
- Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. If possible, choose a language or compiler that performs automatic bounds checking.
- Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. Use libraries or frameworks that make it easier to handle numbers without unexpected consequences. Examples include safe integer handling packages such as SafeInt (C++) or IntegerLib (C or C++).
More Integer Overflow or Wraparound vulnerabilities (CWE-190)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Other vulnerabilities in Autodesk products
- 7.8 High severity
Recent Integer Overflow or Wraparound vulnerabilities
- 9.8 Critical severity
- 7.8 High severity
Apple Multiple Products Integer Overflow Exploited
- 7.5 High severity
- 7.5 High severity
- 9.8 Critical severity
- 9.8 Critical severity
Spotted an error? Tell us.