Code execution via crafted Office file
Published Jan 12, 2021 · Updated Oct 8, 2024
Remote code execution in Microsoft Office 2010 SP2 through Office 2019 and Microsoft 365 Apps allows attackers to run code via a crafted file. Microsoft has not published the affected parser, file format, or erroneous operation used when Office processes the file. Exploitation requires a user to open the malicious document, after which attacker-supplied code runs in that user's security context.
Summary
What happened
Remote code execution in Microsoft Office 2010 SP2 through Office 2019 and Microsoft 365 Apps allows attackers to run code via a crafted file. Microsoft has not published the affected parser, file format, or erroneous operation used when Office processes the file. Exploitation requires a user to open the malicious document, after which attacker-supplied code runs in that user's security context.
The record
- CVE
- CVE-2021-1711
- Published
- Jan 12, 2021
- Updated
- Oct 8, 2024
- Vendor
- Microsoft
- Product
- Microsoft Office 2016
- Classifications
- T1204.002
- 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?
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