Raw vector
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:HSummary
CVE-2025-1431 is a high-severity Out-of-bounds Read (CWE-125) vulnerability in Autodesk Autocad. Its CVSS base score is 7.8 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Client Execution (T1203); ranked at the 13th 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 RA-5 (Vulnerability Monitoring and Scanning) and SI-16 (Memory Protection) — 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-1431 is an Out-of-Bounds Read vulnerability (CWE-125) affecting Autodesk AutoCAD. The issue arises when AutoCAD parses a maliciously crafted SLDPRT file, potentially leading to a crash, disclosure of sensitive data, or arbitrary code execution in the context of the current process. Published on 2025-03-13, it has a CVSS v3.1 base score of 7.8 (AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H).
An attacker with local access can exploit this vulnerability by tricking a user into opening a specially crafted SLDPRT file in AutoCAD, requiring no privileges but relying on user interaction. Successful exploitation enables high-impact outcomes, including reading sensitive memory contents, modifying process behavior through code execution, or causing application denial of service via crashes, all within the user's process context.
Autodesk's security advisory (ADSK-SA-2025-0001) addresses the vulnerability, with patches and updates available through their support resources, such as the latest AutoCAD and AutoCAD LT 2022 downloads. Security practitioners should advise users to apply these updates promptly via Autodesk Access or the provided support articles.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-6379
Vulnerability Data
A maliciously crafted SLDPRT file, when parsed through Autodesk AutoCAD, can force an Out-of-Bounds Read 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 TechniquesAI
Why these techniques?
The vulnerability is a client-side file parsing flaw in AutoCAD triggered by opening a malicious SLDPRT file, directly enabling exploitation for client code execution (T1203) via user execution of a malicious file (T1204.002).
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
Mitigating Controls (NIST 800-53 r5) AI
Directly remediates the out-of-bounds read vulnerability by requiring timely application of Autodesk patches for AutoCAD as detailed in the security advisory.
Implements memory protections such as ASLR and DEP that mitigate exploitation of the out-of-bounds read for arbitrary code execution or sensitive data disclosure.
Requires vulnerability scanning to identify unpatched AutoCAD installations affected by CVE-2025-1431, enabling prompt remediation.
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-development practices such as bounds checking and memory-safe languages directly prevent out-of-bounds reads.
Vulnerability scanning and recording can discover instances of out-of-bounds reads after code is deployed.
Routine patching replaces vulnerable code containing out-of-bounds read flaws.
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 in development and acceptance includes fuzzing and static analysis that detect out-of-bounds read defects before release.
Logging can record evidence of an out-of-bounds read but does not prevent the weakness itself.
Secure development life cycle mandates input validation and bounds checking that directly prevent out-of-bounds reads.
Application security requirements include explicit bounds and memory-safety specifications that mitigate buffer over-reads.
Secure system architecture and engineering principles require memory-safe design patterns and runtime protections against out-of-bounds access.
Secure coding standards explicitly forbid unsafe pointer arithmetic and mandate bounds-checked reads, eliminating CWE-125.