Code execution via crafted file memory corruption
Published Mar 12, 2020 · Updated Aug 4, 2024
Memory corruption in Microsoft Word components in Office, SharePoint Server, and Office Online Server allows remote attackers to execute code. Microsoft has disclosed only that Word mishandles objects in memory when processing a crafted file; no file format or faulty routine is public. Viewing the file in the Preview Pane is sufficient, and resulting code runs with the logged-on user's permissions.
Summary
What happened
Memory corruption in Microsoft Word components in Office, SharePoint Server, and Office Online Server allows remote attackers to execute code. Microsoft has disclosed only that Word mishandles objects in memory when processing a crafted file; no file format or faulty routine is public. Viewing the file in the Preview Pane is sufficient, and resulting code runs with the logged-on user's permissions.
The record
- CVE
- CVE-2020-0852
- Published
- Mar 12, 2020
- Updated
- Aug 4, 2024
- Vendor
- Microsoft
- Product
- Microsoft Office
- Classifications
- T1203, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 12, 2020CVE publishedPublication date reported by the CVE source.
- Aug 4, 2024Record 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=2016 for Mac
- Affected versionversion=2019 for 32-bit editions
- Affected versionversion=2019 for 64-bit editions
What conditions does exploitation require?
What is affected?
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