CVE-2025-1427
Autodesk Autocad 2022 – 2022.1.6
Raw vector
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:HSummary
CVE-2025-1427 is a high-severity Use of Uninitialized Variable (CWE-457) vulnerability in Autodesk Autocad. Its CVSS base score is 7.8 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique OS Credential Dumping (T1003); ranked at the 16th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SA-15 (Development Process, Standards, and Tools) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2025-1427, published on 2025-03-13, is an uninitialized variable vulnerability (CWE-457, CWE-908) affecting Autodesk AutoCAD. The issue arises when AutoCAD parses a maliciously crafted CATPRODUCT file, leading to potential exploitation. It carries a CVSS v3.1 base score of 7.8 (AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H), indicating high confidentiality, integrity, and availability impacts.
A local attacker with low complexity can exploit this vulnerability by tricking a user into opening a malicious CATPRODUCT file within AutoCAD, requiring no privileges but necessitating user interaction. Successful exploitation enables the attacker to crash the application, read sensitive data from memory, or execute arbitrary code in the context of the AutoCAD process.
Autodesk has published security advisory ADSK-SA-2025-0001 addressing this issue. Mitigation involves applying the latest updates for AutoCAD, available through Autodesk's support resources, such as the update download page for AutoCAD and AutoCAD LT 2022. Additional details are provided in Autodesk Access product overview.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-6383
Vulnerability Data
A maliciously crafted CATPRODUCT file, when parsed through Autodesk AutoCAD, can force an Uninitialized Variable vulnerability. A malicious actor can leverage this vulnerability to cause a crash, read sensitive data, or execute arbitrary code in the context of the current…
more
process.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
Developer testing and static analysis directly find uses of uninitialized variables before deployment.
Documented development standards and tools can enforce initialization requirements in code.
Engineering principles can mandate explicit variable initialization to avoid uninitialized use.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices directly catch uninitialized-variable defects via static analysis and code review while the control encompasses many additional development controls.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing can detect uninitialized-variable bugs, but the control is broader.
Secure development life cycle mandates practices that reduce uninitialized-variable defects.
Application security requirements can specify initialization rules, but the control itself does not directly address the weakness.
Secure system architecture and engineering principles include defensive coding practices that prevent use of uninitialized memory or objects.
Secure coding explicitly requires variable initialization and static-analysis checks.