Code execution via out-of-bounds file parsing
Published Jun 27, 2023 · Updated Dec 5, 2024
Memory corruption in pskernel.dll in Autodesk products from 2020 through 2023 allows attackers to execute code via a crafted file. The component writes beyond the intended memory buffer while parsing attacker-controlled file data, corrupting the current process. Exploitation requires a user to open the file and, according to Autodesk, code execution depends on chaining this flaw with other vulnerabilities.
Summary
What happened
Memory corruption in pskernel.dll in Autodesk products from 2020 through 2023 allows attackers to execute code via a crafted file. The component writes beyond the intended memory buffer while parsing attacker-controlled file data, corrupting the current process. Exploitation requires a user to open the file and, according to Autodesk, code execution depends on chaining this flaw with other vulnerabilities.
The record
- CVE
- CVE-2023-29068
- Published
- Jun 27, 2023
- Updated
- Dec 5, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 27, 2023CVE publishedPublication date reported by the CVE source.
- Dec 5, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo