Code execution via crafted Office file
Published Jan 12, 2021 · Updated Oct 8, 2024
Remote code execution in Microsoft Excel products allows attackers to execute code as the current user after a crafted Office file is opened. Microsoft has not published the affected parser, memory operation, or malformed file element that triggers the flaw. Exploitation requires user interaction, and resulting code runs with the privileges of the user who opens the file.
Summary
What happened
Remote code execution in Microsoft Excel products allows attackers to execute code as the current user after a crafted Office file is opened. Microsoft has not published the affected parser, memory operation, or malformed file element that triggers the flaw. Exploitation requires user interaction, and resulting code runs with the privileges of the user who opens the file.
The record
- CVE
- CVE-2021-1714
- Published
- Jan 12, 2021
- Updated
- Oct 8, 2024
- Vendor
- Microsoft
- Product
- Microsoft Office 2016
- Classifications
- T1204.002, T1203
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 12, 2021CVE publishedPublication date reported by the CVE source.
- Oct 8, 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=16.0.0 <publication
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