Security readout for executives and security teams
Plain-English summary
CVE-2024-20673 is a high-severity Microsoft Office vulnerability that could allow code execution on an affected computer after user interaction. Successful exploitation could seriously affect data confidentiality, integrity, and system availability. The supplied evidence identifies multiple Office 2016 applications, Office 2019, Office LTSC 2021, and Skype for Business 2016 as affected.
Executive priority
Treat this as a high-priority remediation item because successful exploitation could fully compromise affected systems and requires only user interaction, not existing privileges. Prioritize exposed user workstations and confirm update coverage. The supplied evidence does not establish active exploitation, so urgency should be driven by impact and affected-product prevalence rather than claims of an ongoing campaign.
Technical view
The vulnerability is rated CVSS 3.1 7.8 with vector AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H. Exploitation requires user interaction, needs no prior privileges, and can cause high confidentiality, integrity, and availability impact. It is categorized as CWE-693, Protection Mechanism Failure. The supplied sources do not describe the underlying flaw or triggering content.
Likely exposure
Exposure is most likely where the listed Microsoft Office, Excel, Word, PowerPoint, Publisher, Visio, or Skype for Business 2016 products remain installed without the Microsoft security update. The bundle also identifies Office 2019 and Office LTSC 2021. Actual exposure requires comparing installed editions, versions, and update status against Microsoft’s advisory.
Exploitation context
The CVSS vector indicates local attack conditions and required user interaction, despite the remote-code-execution classification. No prior privileges are required. The bundle marks the CVE as absent from KEV and provides no cited evidence of active exploitation. It also provides no public exploit details or observed attack campaign information.
Researcher notes
Public evidence in the bundle is limited to the RCE classification, affected-product list, CVSS vector, CWE-693 mapping, and Microsoft advisory. It does not disclose the vulnerable component, root cause, attack format, security boundary failure, or exploit reliability. Researchers should avoid inferring these details and use Microsoft’s advisory to establish product-specific update applicability.
Mitigation direction
- Review Microsoft’s CVE advisory for applicable security updates.
- Prioritize updating affected Office and Skype for Business installations.
- Use normal software deployment controls to distribute and verify the vendor update.
- Reduce unnecessary user interaction with untrusted Office content while remediation is pending.
Validation and detection
- Inventory installations of every affected product listed in the CVE bundle.
- Compare installed versions and update status with Microsoft’s advisory.
- Verify the applicable Microsoft security update is successfully installed.
- Re-scan endpoints after deployment and investigate systems still reported vulnerable.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-693: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2024-20673 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C1.85.9microsoftVulnerability scoring details
Base CVSS 3.1 score
7.8HighVector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- Microsoft Office Remote Code Execution VulnerabilityCVE reference, microsoft · vendor-advisory, patch
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Protection Mechanism Failure
Protection Mechanism Failure represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.