Memory disclosure via crafted-file out-of-bounds read
Published Feb 14, 2023 · Updated Aug 19, 2026
Out-of-bounds read in Microsoft Office 16.0.1 allows attackers to disclose memory contents through a crafted file opened by a user. Office reads beyond the intended buffer while processing the crafted file, exposing process memory; Microsoft has not disclosed the affected parser or function. Successful exploitation requires a user to open the file and provides read-only disclosure, with no reported ability to modify data or interrupt Office.
Summary
What happened
Out-of-bounds read in Microsoft Office 16.0.1 allows attackers to disclose memory contents through a crafted file opened by a user. Office reads beyond the intended buffer while processing the crafted file, exposing process memory; Microsoft has not disclosed the affected parser or function. Successful exploitation requires a user to open the file and provides read-only disclosure, with no reported ability to modify data or interrupt Office.
The record
- CVE
- CVE-2023-21714
- Published
- Feb 14, 2023
- Updated
- Aug 19, 2026
- Vendor
- Microsoft
- Product
- Microsoft Office LTSC 2021
- Classifications
- CWE-125, CWE-668, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 14, 2023CVE publishedPublication date reported by the CVE source.
- Aug 19, 2026Record 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 <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