CyberSecBulletin
CVE-2024-0446NVD status: Analyzed

AutoCAD: Out-of-bounds Write

Published Updated By the CyberSecBulletin desk

CVE-2024-0446 is a high-severity out-of-bounds write vulnerability in AutoCAD from Autodesk, 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. The record lists versions 2025.0.1, 2024.1.3, 2023.1.5 as the first without the flaw, so updating AutoCAD to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.46% chance of exploitation within 30 days, which is low compared with other CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Update AutoCAD to 2025.0.1 or 2024.1.3 or 2023.1.5 or 2022.1.4, whichever matches your release line, or a later version.
  2. Update AutoCAD Architecture to 2025.0.1 or 2024.1.3 or 2023.1.5 or 2022.1.4, whichever matches your release line, or a later version.
  3. Update AutoCAD Electrical to 2025.0.1 or 2024.1.3 or 2023.1.5 or 2022.1.4, whichever matches your release line, or a later version.
  4. Read the advisory on autodesk.com for workarounds and exact fixed builds.
  5. 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

VendorProductAffected versionsFixed in
AutodeskAutoCAD2025 up to, but not including, 2025.0.1; 2024 up to, but not including, 2024.1.3; 2023 up to, but not including, 2023.1.5; 2022 up to, but not including, 2022.1.4; 2021 up to, but not including, 2021.1.42025.0.1, 2024.1.3, 2023.1.5, 2022.1.4, 2021.1.4
AutodeskAutoCAD Architecture2025 up to, but not including, 2025.0.1; 2024 up to, but not including, 2024.1.3; 2023 up to, but not including, 2023.1.5; 2022 up to, but not including, 2022.1.4; 2021 up to, but not including, 2021.1.42025.0.1, 2024.1.3, 2023.1.5, 2022.1.4, 2021.1.4
AutodeskAutoCAD Electrical2025 up to, but not including, 2025.0.1; 2024 up to, but not including, 2024.1.3; 2023 up to, but not including, 2023.1.5; 2022 up to, but not including, 2022.1.4; 2021 up to, but not including, 2021.1.42025.0.1, 2024.1.3, 2023.1.5, 2022.1.4, 2021.1.4
AutodeskAutoCAD Mechanical2025 up to, but not including, 2025.0.1; 2024 up to, but not including, 2024.1.3; 2023 up to, but not including, 2023.1.5; 2022 up to, but not including, 2022.1.4; 2021 up to, but not including, 2021.1.42025.0.1, 2024.1.3, 2023.1.5, 2022.1.4, 2021.1.4
AutodeskAutoCAD MEP2025 up to, but not including, 2025.0.1; 2024 up to, but not including, 2024.1.3; 2023 up to, but not including, 2023.1.5; 2022 up to, but not including, 2022.1.4; 2021 up to, but not including, 2021.1.42025.0.1, 2024.1.3, 2023.1.5, 2022.1.4, 2021.1.4
AutodeskAutoCAD Plant 3D2025 up to, but not including, 2025.0.1; 2024 up to, but not including, 2024.1.3; 2023 up to, but not including, 2023.1.5; 2022 up to, but not including, 2022.1.4; 2021 up to, but not including, 2021.1.42025.0.1, 2024.1.3, 2023.1.5, 2022.1.4, 2021.1.4
AutodeskCivil 3D2025 up to, but not including, 2025.0.1; 2024 up to, but not including, 2024.1.3; 2023 up to, but not including, 2023.1.5; 2022 up to, but not including, 2022.1.4; 2021 up to, but not including, 2021.1.42025.0.1, 2024.1.3, 2023.1.5, 2022.1.4, 2021.1.4
AutodeskAdvance Steel2025 up to, but not including, 2025.0.1; 2024 up to, but not including, 2024.1.3; 2023 up to, but not including, 2023.1.5; 2022 up to, but not including, 2022.1.4; 2021 up to, but not including, 2021.1.42025.0.1, 2024.1.3, 2023.1.5, 2022.1.4, 2021.1.4
AutodeskAutoCAD MAP 3D2025 up to, but not including, 2025.0.1; 2024 up to, but not including, 2024.1.3; 2023 up to, but not including, 2023.1.5; 2022 up to, but not including, 2022.1.4; 2021 up to, but not including, 2021.1.42025.0.1, 2024.1.3, 2023.1.5, 2022.1.4, 2021.1.4
Autodeskautocad_advance_steel2021 up to, but not including, 2021.1.4; 2022 up to, but not including, 2022.1.4; 2023 up to, but not including, 2023.1.5; 2024 up to, but not including, 2024.1.3; 2025 up to, but not including, 2025.0.12021.1.4, 2022.1.4, 2023.1.5, 2024.1.3, 2025.0.1
Autodeskautocad_civil_3d2021 up to, but not including, 2021.1.4; 2022 up to, but not including, 2022.1.4; 2023 up to, but not including, 2023.1.5; 2024 up to, but not including, 2024.1.3; 2025 up to, but not including, 2025.0.12021.1.4, 2022.1.4, 2023.1.5, 2024.1.3, 2025.0.1

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 CNA (autodesk.com).

Official description

A maliciously crafted STP, CATPART or MODEL file, when parsed in ASMKERN228A.dll and ASMdatax229A.dll through Autodesk AutoCAD, may force an Out-of-Bounds Write vulnerability. A malicious actor may leverage this vulnerability to cause a crash, cause data corruption, or execute arbitrary code in the context of the current process.

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.

More Out-of-bounds Write vulnerabilities (CWE-787)

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
  3. Record last changed materially (score, affected products, status or references).

References

Other vulnerabilities in AutoCAD

All AutoCAD vulnerabilities

Recent Out-of-bounds Write vulnerabilities

Spotted an error? Tell us.