CVE-2023-41140

HIGH
7.8
CVSS Score
Published: November 23, 2023 at 03:56 AM UTC
Updated: June 17, 2026 at 06:20 AM UTC
10 products affected across 1 vendorAutoCADAutoCAD ElectricalCivil 3D

Using AutoCAD, Advance Steel and Civil 3D by Autodesk?

Get instant alerts when new vulnerabilities affect AutoCAD, Advance Steel and Civil 3D - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.8
Exploit prediction
EPSS 0.3%

Description

A maliciously crafted PRT file when parsed through Autodesk AutoCAD 2024 and 2023 can be used to cause a Heap-Based Buffer Overflow. A malicious actor can leverage this vulnerability to cause a crash, read sensitive data, or execute arbitrary code in the context of the current process.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v < 2023.1.42024.0.0 ≤ v < 2024.1.120232024
Affected range stops below 2023.1.4, so it looks safe — our inference, not a vendor statement
Affected range stops below 2024.1.1, so it looks safe — our inference, not a vendor statement
v < 2024.12023.0.0 ≤ v < 2023.1.42024.0.0 ≤ v < 2024.1.120232024
Affected range stops below 2023.1.4, so it looks safe — our inference, not a vendor statement
Affected range stops below 2024.1, so it looks safe — our inference, not a vendor statement
Affected range stops below 2024.1.1, so it looks safe — our inference, not a vendor statement
v < 2023.1.42024.0.0 ≤ v < 2024.1.1
Affected range stops below 2023.1.4, so it looks safe — our inference, not a vendor statement
Affected range stops below 2024.1.1, so it looks safe — our inference, not a vendor statement
v < 2023.1.42024.0.0 ≤ v < 2024.1.1
Affected range stops below 2023.1.4, so it looks safe — our inference, not a vendor statement
Affected range stops below 2024.1.1, so it looks safe — our inference, not a vendor statement
v < 2023.1.4v < 2024.12024.0.0 ≤ v < 2024.1.1
Affected range stops below 2023.1.4, so it looks safe — our inference, not a vendor statement
Affected range stops below 2024.1, so it looks safe — our inference, not a vendor statement
Affected range stops below 2024.1.1, so it looks safe — our inference, not a vendor statement
v < 2023.1.42024.0.0 ≤ v < 2024.1.1
Affected range stops below 2023.1.4, so it looks safe — our inference, not a vendor statement
Affected range stops below 2024.1.1, so it looks safe — our inference, not a vendor statement
v < 2023.1.42024.0.0 ≤ v < 2024.1.1
Affected range stops below 2023.1.4, so it looks safe — our inference, not a vendor statement
Affected range stops below 2024.1.1, so it looks safe — our inference, not a vendor statement
v < 2023.1.42024.0.0 ≤ v < 2024.1.1
Affected range stops below 2023.1.4, so it looks safe — our inference, not a vendor statement
Affected range stops below 2024.1.1, so it looks safe — our inference, not a vendor statement
v < 2023.1.42024.0.0 ≤ v < 2024.1.1
Affected range stops below 2023.1.4, so it looks safe — our inference, not a vendor statement
Affected range stops below 2024.1.1, so it looks safe — our inference, not a vendor statement
v < 2023.1.42024.0.0 ≤ v < 2024.1.120232024
Affected range stops below 2023.1.4, so it looks safe — our inference, not a vendor statement
Affected range stops below 2024.1.1, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

CVSS

Attack Vector
LOCAL
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
HIGH
Integrity
HIGH
Availability
HIGH
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-122CWE-787

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card