Code execution via crafted cursor file memory corruption
Published Oct 11, 2022 · Updated Aug 3, 2024
Memory corruption in SAP 3D Visual Enterprise Author 9 allows context-dependent attackers to execute code through a crafted cursor file. The cursor-file parser mishandles memory when a crafted .cur or ico.x3d payload causes a stack-based overflow or reuses a dangling pointer whose storage has been overwritten. Execution requires a user to open the untrusted file, after which successful corruption runs the payload with the application's access.
Summary
What happened
Memory corruption in SAP 3D Visual Enterprise Author 9 allows context-dependent attackers to execute code through a crafted cursor file. The cursor-file parser mishandles memory when a crafted .cur or ico.x3d payload causes a stack-based overflow or reuses a dangling pointer whose storage has been overwritten. Execution requires a user to open the untrusted file, after which successful corruption runs the payload with the application's access.
The record
- CVE
- CVE-2022-41184
- Published
- Oct 11, 2022
- Updated
- Aug 3, 2024
- Vendor
- SAP SE
- Product
- SAP 3D Visual Enterprise Author
- Classifications
- CWE-119, CWE-787, T1204.002, T1203
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 11, 2022CVE publishedPublication date reported by the CVE source.
- Aug 3, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=9
What conditions does exploitation require?
What is affected?
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.
Weakness, pattern, technique
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