Code execution via crafted file opening
Published Jun 8, 2021 · Updated Feb 28, 2025
Code injection in Microsoft Outlook in affected Office 2019, Outlook 2013/2016, and Microsoft 365 Apps builds allows attackers to execute code. Microsoft has not disclosed the affected parser, file format, or unsafe operation performed on the crafted file. Exploitation requires a user to open the file in Outlook; the Preview Pane alone is not an attack vector.
Summary
What happened
Code injection in Microsoft Outlook in affected Office 2019, Outlook 2013/2016, and Microsoft 365 Apps builds allows attackers to execute code. Microsoft has not disclosed the affected parser, file format, or unsafe operation performed on the crafted file. Exploitation requires a user to open the file in Outlook; the Preview Pane alone is not an attack vector.
The record
- CVE
- CVE-2021-31949
- Published
- Jun 8, 2021
- Updated
- Feb 28, 2025
- Vendor
- Microsoft
- Product
- Microsoft Office 2019
- Classifications
- CWE-94, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 8, 2021CVE publishedPublication date reported by the CVE source.
- Feb 28, 2025Record 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=19.0.0 <https://aka.ms/OfficeSecurityReleases
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