Code execution via improper object handling
Published Jan 14, 2020 · Updated Aug 4, 2024
Object-handling flaw in Microsoft Excel in Microsoft 365 Apps for enterprise allows attackers to execute code via user-opened content. Excel improperly handles objects in memory while processing the content, but Microsoft has not disclosed the affected parser or erroneous memory operation. Opening attacker-controlled content is required, and successful exploitation runs code in the current user's security context.
Summary
What happened
Object-handling flaw in Microsoft Excel in Microsoft 365 Apps for enterprise allows attackers to execute code via user-opened content. Excel improperly handles objects in memory while processing the content, but Microsoft has not disclosed the affected parser or erroneous memory operation. Opening attacker-controlled content is required, and successful exploitation runs code in the current user's security context.
The record
- CVE
- CVE-2020-0653
- Published
- Jan 14, 2020
- Updated
- Aug 4, 2024
- Vendor
- Microsoft
- Product
- Microsoft 365 Apps for enterprise
- Classifications
- T1203, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 14, 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=32-bit Systems
- Affected versionversion=64-bit Systems
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.
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