Code execution via double-free memory corruption
Published Jul 11, 2023 · Updated Feb 28, 2025
Double-free memory corruption in Microsoft Excel in affected Office releases allows local attackers to execute code via a crafted file. Microsoft identifies the weakness as a double free but has not disclosed the affected parser, object lifetime, or exact unsafe operation. Exploitation requires a user to open the file, after which attacker-controlled code runs with that user's privileges.
Summary
What happened
Double-free memory corruption in Microsoft Excel in affected Office releases allows local attackers to execute code via a crafted file. Microsoft identifies the weakness as a double free but has not disclosed the affected parser, object lifetime, or exact unsafe operation. Exploitation requires a user to open the file, after which attacker-controlled code runs with that user's privileges.
The record
- CVE
- CVE-2023-33161
- Published
- Jul 11, 2023
- Updated
- Feb 28, 2025
- Vendor
- Microsoft
- Product
- Microsoft Office LTSC for Mac 2021
- Classifications
- CWE-415, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jul 11, 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.75.23070901
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