Cyber Resilience

CVE-2023-27913

Memory Safety in Autodesk Autocad 2023 – 2023.1.3

Memory Safety
Published
14 April 2023
Modified
06 February 2025
Patch / advisory
View 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-27913 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 X_B file when parsed through Autodesk® AutoCAD® 2023 can be used to cause an Integer Overflow. A malicious actor can leverage this vulnerability to cause a crash or read sensitive data, or execute arbitrary code in the…

more

context of the current process.

CWE(s)
CWE-190

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.
attack.mitre.org →
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.
attack.mitre.org →
T1203 Exploitation for Client Execution Execution
Adversaries may exploit software vulnerabilities in client applications to execute code.
attack.mitre.org →
T1210 Exploitation of Remote Services Lateral Movement
Adversaries may exploit remote services to gain unauthorized access to internal systems once inside of a network.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2023-25004Same product: Autodesk Autocad
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
CVE-2023-27914Same product: Autodesk Autocad
CVE-2023-29075Same product: Autodesk Autocad

Affected Assets

autodesk
autocad
2023 — 2023.1.3
autodesk
autocad advance steel
2023 — 2023.1.3
autodesk
autocad architecture
2023 — 2023.1.3
autodesk
autocad civil 3d
2023 — 2023.1.3
autodesk
autocad electrical
2023 — 2023.1.3
autodesk
autocad lt
2023 — 2023.1.3
autodesk
autocad map 3d
2023 — 2023.1.3
autodesk
autocad mechanical
2023 — 2023.1.3
autodesk
autocad mep
2023 — 2023.1.3
autodesk
autocad plant 3d
2023 — 2023.1.3

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.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing in development can detect integer overflows before release.

A.8.25 Secure development life cycle partial match
prevents

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

A.8.26 Application security requirements partial match
degrades

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

A.8.27 Secure system architecture and engineering principles partial match
degrades

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

A.8.28 Secure coding partial match
prevents

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

References