Code execution via undisclosed heap buffer overflow
Published Jun 13, 2023 · Updated Feb 28, 2025
Heap-based buffer overflow in Microsoft Office allows context-dependent attackers to execute code after a user opens a crafted file. Microsoft has not disclosed the affected parser or the operation that overruns heap memory while processing the crafted file. Successful exploitation runs attacker-controlled code with the affected user's privileges and requires user interaction.
Summary
What happened
Heap-based buffer overflow in Microsoft Office allows context-dependent attackers to execute code after a user opens a crafted file. Microsoft has not disclosed the affected parser or the operation that overruns heap memory while processing the crafted file. Successful exploitation runs attacker-controlled code with the affected user's privileges and requires user interaction.
The record
- CVE
- CVE-2023-33146
- Published
- Jun 13, 2023
- Updated
- Feb 28, 2025
- Vendor
- Microsoft
- Product
- Microsoft Office LTSC for Mac 2021
- Classifications
- CWE-122, T1203, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 13, 2023CVE publishedPublication date reported by the CVE source.
- Feb 28, 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=16.0.1 <16.74.23061100
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