Code execution via FBX parser heap overflow
Published Aug 9, 2022 · Updated May 29, 2025
Heap overflow in the FBX file parser in Microsoft Visual Studio allows remote attackers to execute code through a crafted FBX file. Microsoft identifies the locus as the FBX file parser and the wrong operation as a heap overflow, but has not disclosed the malformed field or allocation error. Exploitation requires a user to open the crafted file, after which attacker-controlled code runs in that user's security context.
Summary
What happened
Heap overflow in the FBX file parser in Microsoft Visual Studio allows remote attackers to execute code through a crafted FBX file. Microsoft identifies the locus as the FBX file parser and the wrong operation as a heap overflow, but has not disclosed the malformed field or allocation error. Exploitation requires a user to open the crafted file, after which attacker-controlled code runs in that user's security context.
The record
- CVE
- CVE-2022-35777
- Published
- Aug 9, 2022
- Updated
- May 29, 2025
- Vendor
- Microsoft
- Product
- Microsoft Visual Studio 2019
- Classifications
- CWE-94, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 9, 2022CVE publishedPublication date reported by the CVE source.
- May 29, 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.
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