Code execution via FBX use-after-free
Published Jan 9, 2024 · Updated May 3, 2025
An FBX parsing flaw in affected Microsoft Office and 3D Viewer releases allows attackers to execute code through a malicious FBX file. The parser operates on an object without first validating that the object still exists, producing a use-after-free condition. A target must open a malicious file or visit a malicious page; successful exploitation runs code with the current process's rights.
Summary
What happened
An FBX parsing flaw in affected Microsoft Office and 3D Viewer releases allows attackers to execute code through a malicious FBX file. The parser operates on an object without first validating that the object still exists, producing a use-after-free condition. A target must open a malicious file or visit a malicious page; successful exploitation runs code with the current process's rights.
The record
- CVE
- CVE-2024-20677
- Published
- Jan 9, 2024
- Updated
- May 3, 2025
- Vendor
- Microsoft
- Product
- Microsoft Office 2019
- Classifications
- CWE-122, T1203
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 9, 2024CVE publishedPublication date reported by the CVE source.
- May 3, 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=19.0.0 <https://aka.ms/OfficeSecurityReleases
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