Code execution via use-after-free during file opening
Published Jun 17, 2023 · Updated Feb 28, 2025
Use-after-free in Microsoft Publisher for affected Office releases allows attackers to execute code when a user opens a crafted file. Publisher reuses memory after freeing it while processing the document, but Microsoft has not disclosed the affected parser, object, or file format. Exploitation requires a victim to open attacker-controlled content and can run code in that user's security context, affecting data and application availability.
Summary
What happened
Use-after-free in Microsoft Publisher for affected Office releases allows attackers to execute code when a user opens a crafted file. Publisher reuses memory after freeing it while processing the document, but Microsoft has not disclosed the affected parser, object, or file format. Exploitation requires a victim to open attacker-controlled content and can run code in that user's security context, affecting data and application availability.
The record
- CVE
- CVE-2023-28287
- Published
- Jun 17, 2023
- Updated
- Feb 28, 2025
- Vendor
- Microsoft
- Product
- Microsoft Office 2019
- Classifications
- CWE-416, T1204.002, T1203
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 17, 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=19.0.0 <https://aka.ms/OfficeSecurityReleases
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