Code execution via undisclosed heap buffer overflow
Published Jan 10, 2023 · Updated Jan 1, 2025
Heap-based buffer overflow in Microsoft 3D Builder 20.0.0 allows remote attackers to execute code after a user opens crafted content. Microsoft identifies the weakness as a heap-based buffer overflow but has not disclosed the affected parser, file format, or faulty memory operation. Exploitation requires user interaction and runs code in the context of the current 3D Builder process.
Summary
What happened
Heap-based buffer overflow in Microsoft 3D Builder 20.0.0 allows remote attackers to execute code after a user opens crafted content. Microsoft identifies the weakness as a heap-based buffer overflow but has not disclosed the affected parser, file format, or faulty memory operation. Exploitation requires user interaction and runs code in the context of the current 3D Builder process.
The record
- CVE
- CVE-2023-21786
- Published
- Jan 10, 2023
- Updated
- Jan 1, 2025
- Vendor
- Microsoft
- Product
- 3D Builder
- Classifications
- CWE-122, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 10, 2023CVE publishedPublication date reported by the CVE source.
- Jan 1, 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.1
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