CVE-2023-25003
HIGH
7.8
CVSS Score
Published: June 23, 2023 at 12:00 AM UTC
Updated: June 17, 2026 at 05:40 AM UTC
17 products affected across 1 vendorAutoCADAutoCAD ElectricalCivil 3D
Using AutoCAD, Maya by N/A?
Get instant alerts when new vulnerabilities affect AutoCAD, Maya - before attackers find them.
Real-time alertsTrack your software stackFree plan available
Severity
HIGH7.8
Exploit prediction
EPSS 0.3%
SSVC
No known exploit
Description
A maliciously crafted pskernel.dll file in Autodesk AutoCAD 2023 and Maya 2022 may be used to trigger out-of-bound read write / read vulnerabilities. Exploitation of this vulnerability may lead to code execution.
Affected
Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.
2020 ≤ v < 2020.1.62021 ≤ v < 2021.1.32022 ≤ v < 2022.1.32023 ≤ v < 2023.1.1
Affected range stops below 2020.1.6, so it looks safe — our inference, not a vendor statement
Affected range stops below 2021.1.3, so it looks safe — our inference, not a vendor statement
Affected range stops below 2022.1.3, so it looks safe — our inference, not a vendor statement
Affected range stops below 2023.1.1, so it looks safe — our inference, not a vendor statement
2023 ≤ v < 2023.1.1
Affected range stops below 2023.1.1, so it looks safe — our inference, not a vendor statement
Affected range stops below 2020.1.6, so it looks safe — our inference, not a vendor statement
Affected range stops below 2021.1.3, so it looks safe — our inference, not a vendor statement
Affected range stops below 2022.1.3, so it looks safe — our inference, not a vendor statement
Affected range stops below 2023.1.1, so it looks safe — our inference, not a vendor statement
2020 ≤ v < 2020.1.62021 ≤ v < 2021.1.32022 ≤ v < 2022.1.32023 ≤ v < 2023.1.1
Affected range stops below 2020.1.6, so it looks safe — our inference, not a vendor statement
Affected range stops below 2021.1.3, so it looks safe — our inference, not a vendor statement
Affected range stops below 2022.1.3, so it looks safe — our inference, not a vendor statement
Affected range stops below 2023.1.1, so it looks safe — our inference, not a vendor statement
2020 ≤ v < 2020.1.62021 ≤ v < 2021.1.32022 ≤ v < 2022.1.32023 ≤ v < 2023.1.1
Affected range stops below 2020.1.6, so it looks safe — our inference, not a vendor statement
Affected range stops below 2021.1.3, so it looks safe — our inference, not a vendor statement
Affected range stops below 2022.1.3, so it looks safe — our inference, not a vendor statement
Affected range stops below 2023.1.1, so it looks safe — our inference, not a vendor statement
2020 ≤ v < 2020.1.62021 ≤ v < 2021.1.32022 ≤ v < 2022.1.32023 ≤ v < 2023.1.1
Affected range stops below 2020.1.6, so it looks safe — our inference, not a vendor statement
Affected range stops below 2021.1.3, so it looks safe — our inference, not a vendor statement
Affected range stops below 2022.1.3, so it looks safe — our inference, not a vendor statement
Affected range stops below 2023.1.1, so it looks safe — our inference, not a vendor statement
2020 ≤ v < 2020.1.62021 ≤ v < 2021.1.32022 ≤ v < 2022.1.32023 ≤ v < 2023.1.1
Affected range stops below 2020.1.6, so it looks safe — our inference, not a vendor statement
Affected range stops below 2021.1.3, so it looks safe — our inference, not a vendor statement
Affected range stops below 2022.1.3, so it looks safe — our inference, not a vendor statement
Affected range stops below 2023.1.1, so it looks safe — our inference, not a vendor statement
2020 ≤ v < 2020.1.62021 ≤ v < 2021.1.32022 ≤ v < 2022.1.32023 ≤ v < 2023.1.1
Affected range stops below 2020.1.6, so it looks safe — our inference, not a vendor statement
Affected range stops below 2021.1.3, so it looks safe — our inference, not a vendor statement
Affected range stops below 2022.1.3, so it looks safe — our inference, not a vendor statement
Affected range stops below 2023.1.1, so it looks safe — our inference, not a vendor statement
2020 ≤ v < 2020.1.62021 ≤ v < 2021.1.32022 ≤ v < 2022.1.32023 ≤ v < 2023.1.1
Affected range stops below 2020.1.6, so it looks safe — our inference, not a vendor statement
Affected range stops below 2021.1.3, so it looks safe — our inference, not a vendor statement
Affected range stops below 2022.1.3, so it looks safe — our inference, not a vendor statement
Affected range stops below 2023.1.1, so it looks safe — our inference, not a vendor statement
2020 ≤ v < 2020.1.62021 ≤ v < 2021.1.32022 ≤ v < 2022.1.32023 ≤ v < 2023.1.1
Affected range stops below 2020.1.6, so it looks safe — our inference, not a vendor statement
Affected range stops below 2021.1.3, so it looks safe — our inference, not a vendor statement
Affected range stops below 2022.1.3, so it looks safe — our inference, not a vendor statement
Affected range stops below 2023.1.1, so it looks safe — our inference, not a vendor statement
Remediation
No guide yetNo remediation guidance has been written for this CVE yet. What the record does show:
Patch and advisory references
References (1)
Vendor Advisory
Source: [email protected]
https://www.autodesk.com/trust/security-advisories/adsk-sa-2023-0009SSVC — Action Prioritization
SSVCNo known exploitNot automatableTotal impact
SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.
CVSS
- Attack Vector
- LOCAL
- Complexity
- LOW
- Privileges
- NONE
- User Interaction
- REQUIRED
- Scope
- UNCHANGED
- Confidentiality
- HIGH
- Integrity
- HIGH
- Availability
- HIGH
Vector?
Quick Info
StatusMODIFIED
CWE
CWE-125CWE-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