Code execution via malformed FBX or DAE files
Published Aug 9, 2022 · Updated Jan 2, 2025
Memory corruption in affected Microsoft Visual Studio releases allows remote attackers to execute code by opening a crafted FBX or DAE file. The FBX parser copies user-controlled data into a fixed-length heap buffer without validating its length, while FBX and DAE parsing can also access data beyond allocated buffers. Exploitation requires the target to open a malicious file or visit a malicious page, and resulting code runs in the current process.
Summary
What happened
Memory corruption in affected Microsoft Visual Studio releases allows remote attackers to execute code by opening a crafted FBX or DAE file. The FBX parser copies user-controlled data into a fixed-length heap buffer without validating its length, while FBX and DAE parsing can also access data beyond allocated buffers. Exploitation requires the target to open a malicious file or visit a malicious page, and resulting code runs in the current process.
The record
- CVE
- CVE-2022-35825
- Published
- Aug 9, 2022
- Updated
- Jan 2, 2025
- Vendor
- Microsoft
- Product
- Microsoft Visual Studio 2019
- Classifications
- T1203, T1204.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 9, 2022CVE publishedPublication date reported by the CVE source.
- Jan 2, 2025Record 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=15.0.0 <16.9.24
- Affected versionversion=16.11.0 <16.11.18
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.
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