Code execution via undisclosed object-memory mishandling
Published Feb 11, 2020 · Updated Aug 4, 2024
Memory corruption in affected Microsoft Excel, Office, and Office 365 ProPlus releases allows remote attackers to run code via a crafted file. Microsoft reports only that Excel mishandles objects in memory and has not disclosed the affected parser, object type, or invalid memory operation. Exploitation requires a user to open the file, after which code runs in that user's security context.
Summary
What happened
Memory corruption in affected Microsoft Excel, Office, and Office 365 ProPlus releases allows remote attackers to run code via a crafted file. Microsoft reports only that Excel mishandles objects in memory and has not disclosed the affected parser, object type, or invalid memory operation. Exploitation requires a user to open the file, after which code runs in that user's security context.
The record
- CVE
- CVE-2020-0759
- Published
- Feb 11, 2020
- Updated
- Aug 4, 2024
- Vendor
- Microsoft
- Product
- Microsoft Office
- Classifications
- T1203, T1204.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 11, 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
- Affected versionversion=2019 for Mac
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