A maliciously crafted file consumed through pskernel.dll file could lead to memory corruption vulnerabilities.
A maliciously crafted file consumed through pskernel.dll file could lead to memory corruption vulnerabilities. These vulnerabilities in conjunction with other vulnerabilities could lead to code execution in the context of the current process.
- Published
- Jun 27, 2023
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 13th percentile
- CWE
- CWE-787
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
31
Monitor
Low priority for now.
- CVSS
- 31 / 40 · 7.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
Affected systems
| Vendor | Product | CPE |
|---|---|---|
| autodesk | alias | cpe:2.3:a:autodesk:alias |
| autodesk | autocad | cpe:2.3:a:autodesk:autocad |
| autodesk | autocad advance steel | cpe:2.3:a:autodesk:autocad_advance_steel |
| autodesk | autocad architecture | cpe:2.3:a:autodesk:autocad_architecture |
| autodesk | autocad civil 3d | cpe:2.3:a:autodesk:autocad_civil_3d |
| autodesk | autocad electrical | cpe:2.3:a:autodesk:autocad_electrical |
| autodesk | autocad lt | cpe:2.3:a:autodesk:autocad_lt |
| autodesk | autocad map 3d | cpe:2.3:a:autodesk:autocad_map_3d |
| autodesk | autocad mechanical | cpe:2.3:a:autodesk:autocad_mechanical |
| autodesk | autocad mep | cpe:2.3:a:autodesk:autocad_mep |
| autodesk | autocad plant 3d | cpe:2.3:a:autodesk:autocad_plant_3d |
| autodesk | infraworks | cpe:2.3:a:autodesk:infraworks |
and 5 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- autodesk alias2023 and later · before 2023.1.1
- autodesk autocad2020 and later · before 2020.1.6
- autodesk autocad2021 and later · before 2021.1.3
- autodesk autocad2022 and later · before 2022.1.3
- autodesk autocad2023 and later · before 2023.1.1
- autodesk autocad advance steel2020 and later · before 2020.1.6
- autodesk autocad advance steel2021 and later · before 2021.1.3
- autodesk autocad advance steel2022 and later · before 2022.1.3
- autodesk autocad advance steel2023 and later · before 2023.1.1
- autodesk autocad architecture2020 and later · before 2020.1.6
- autodesk autocad architecture2021 and later · before 2021.1.3
- autodesk autocad architecture2022 and later · before 2022.1.3
- autodesk autocad architecture2023 and later · before 2023.1.1
- autodesk autocad civil 3d2020 and later · before 2020.1.6
- autodesk autocad civil 3d2021 and later · before 2021.1.3
- autodesk autocad civil 3d2022 and later · before 2022.1.3
- autodesk autocad civil 3d2023 and later · before 2023.1.1
- autodesk autocad electrical2020 and later · before 2020.1.6
- autodesk autocad electrical2021 and later · before 2021.1.3
- autodesk autocad electrical2022 and later · before 2022.1.3
Versions reported by the vendor
Affected version ranges reported by the assigning authority (autodesk). Independent of NVD's CPE analysis and usually ahead of it.
n/a Autodesk products
- 2023, 2022, 2021, 2020affected
Same product
autodesk: all recordsOther highest-scoring records for the same primary product.
- CVE-2023-25004A maliciously crafted pskernel.dll file in Autodesk products is used to trigger integer overflow vulnerabilities.31Monitor
- CVE-2023-25003A maliciously crafted pskernel.dll file in Autodesk AutoCAD 2023 and Maya 2022 may be used to trigger out-of-bound read write / read vulnera31Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- No account or password is required.
- A user must open a link or visit a page.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-787 · Out-of-bounds WriteCVSS vector
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpChange log
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.