Code execution via GLB out-of-bounds write
Published Sep 12, 2023 · Updated Oct 30, 2025
Heap-based buffer overflow in Microsoft 3D Builder before 20.0.4.0 allows attackers to execute code by opening a crafted GLB file. The GLB parser fails to validate user-supplied data before writing past the end of an allocated heap object. Exploitation requires the target to visit a malicious page or open a malicious file, and resulting code runs in the current process at low integrity.
Summary
What happened
Heap-based buffer overflow in Microsoft 3D Builder before 20.0.4.0 allows attackers to execute code by opening a crafted GLB file. The GLB parser fails to validate user-supplied data before writing past the end of an allocated heap object. Exploitation requires the target to visit a malicious page or open a malicious file, and resulting code runs in the current process at low integrity.
The record
- CVE
- CVE-2023-36770
- Published
- Sep 12, 2023
- Updated
- Oct 30, 2025
- Vendor
- Microsoft
- Product
- 3D Builder
- Classifications
- CWE-122, T1203
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 12, 2023CVE publishedPublication date reported by the CVE source.
- Oct 30, 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=20.0.0 <20.0.4.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.
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