Cyber Resilience

CVE-2023-25004

Memory Safety in Autodesk Autocad 2020 – 2020.1.6

Published
27 June 2023
Modified
21 November 2024
Patch / advisory
CVSS Score v3.1 7.8
Click a component to see what it means
Raw vectorCVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
EPSS Score 0.0024 15th percentile
Risk Priority 55 floored blend · peak EPSS

Summary

CVE-2023-25004 is a high-severity Integer Overflow or Wraparound (CWE-190) vulnerability in Autodesk Autocad. Its CVSS base score is 7.8 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked at the 15th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

EU & UK References

Vulnerability Data

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.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1068 Exploitation for Privilege Escalation Privilege Escalation
Adversaries may exploit software vulnerabilities in an attempt to elevate privileges.
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
T1203 Exploitation for Client Execution Execution
Adversaries may exploit software vulnerabilities in client applications to execute code.
T1210 Exploitation of Remote Services Lateral Movement
Adversaries may exploit remote services to gain unauthorized access to internal systems once inside of a network.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2023-27913Same product: Autodesk Autocad
CVE-2023-29068Same product: Autodesk Alias
CVE-2023-25003Same product: Autodesk Alias
CVE-2023-29076Same product: Autodesk Autocad
CVE-2023-41139Same product: Autodesk Autocad
CVE-2023-27912Same product: Autodesk Autocad
CVE-2023-29073Same product: Autodesk Autocad
CVE-2023-27915Same product: Autodesk Autocad
CVE-2023-29074Same product: Autodesk Autocad
CVE-2023-41140Same product: Autodesk Autocad

Affected Assets

autodesk
alias
2023 — 2023.1.1
autodesk
autocad
2020 — 2020.1.6 · 2021 — 2021.1.3 · 2022 — 2022.1.3
autodesk
autocad advance steel
2020 — 2020.1.6 · 2021 — 2021.1.3 · 2022 — 2022.1.3
autodesk
autocad architecture
2020 — 2020.1.6 · 2021 — 2021.1.3 · 2022 — 2022.1.3
autodesk
autocad civil 3d
2020 — 2020.1.6 · 2021 — 2021.1.3 · 2022 — 2022.1.3
autodesk
autocad electrical
2020 — 2020.1.6 · 2021 — 2021.1.3 · 2022 — 2022.1.3
autodesk
autocad lt
2020 — 2020.1.6 · 2021 — 2021.1.3 · 2022 — 2022.1.3
autodesk
autocad map 3d
2020 — 2020.1.6 · 2021 — 2021.1.3 · 2022 — 2022.1.3
autodesk
autocad mechanical
2020 — 2020.1.6 · 2021 — 2021.1.3 · 2022 — 2022.1.3
autodesk
autocad mep
2020 — 2020.1.6 · 2021 — 2021.1.3 · 2022 — 2022.1.3
+7 more product configuration(s) — see NVD for full list

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)

Validate
Prove the fix (OWASP ASVS)
  • V5.2.6

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.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require use of safe arithmetic, bounds checks, and testing that prevent integer overflows.

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.

finds

Security testing in development can detect integer overflows before release.

prevents

Secure SDLC mandates input validation and arithmetic checks that prevent integer overflows.

degrades

Application security requirements include bounds checking and safe arithmetic to avoid overflow conditions.

degrades

Secure architecture principles require defensive coding patterns that mitigate integer wraparound risks.

prevents

Secure coding standards explicitly forbid unsafe integer operations and mandate overflow-safe constructs.

References