Code execution via malformed OBJ file parsing
Published Feb 14, 2023 · Updated Aug 19, 2026
Heap-based buffer overflow in Microsoft 3D Builder before 20.0.2.0 allows remote attackers to execute code via a crafted OBJ file. The OBJ file parser fails to validate user-supplied data before processing it, causing memory corruption within the application process. Exploitation requires the target to visit a malicious page or open the file, and successful code runs at the application's low-integrity level.
Summary
What happened
Heap-based buffer overflow in Microsoft 3D Builder before 20.0.2.0 allows remote attackers to execute code via a crafted OBJ file. The OBJ file parser fails to validate user-supplied data before processing it, causing memory corruption within the application process. Exploitation requires the target to visit a malicious page or open the file, and successful code runs at the application's low-integrity level.
The record
- CVE
- CVE-2023-23390
- Published
- Feb 14, 2023
- Updated
- Aug 19, 2026
- Vendor
- Microsoft
- Product
- 3D Builder
- Classifications
- CWE-122, T1203, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 14, 2023CVE publishedPublication date reported by the CVE source.
- Aug 19, 2026Record 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=20.0.0 <20.0.2.0
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