Security readout for executives and security teams
Plain-English summary
A flaw in listed Microsoft Office products could let an attacker run code after a user interacts with malicious content. Successful exploitation could compromise sensitive information, alter data, or disrupt the device. The CVSS score is 7.8, making timely patching important, especially where users routinely receive external documents.
Executive priority
Treat as a high-priority patching item, but not an emergency based solely on the supplied evidence. Prioritize externally exposed user populations, validate deployment coverage, and escalate if internal telemetry or later authoritative reporting indicates exploitation.
Technical view
CVE-2024-30104 is an Office remote-code-execution vulnerability associated with CWE-59, improper link resolution before file access. Its CVSS 3.1 vector indicates local delivery, low complexity, no privileges required, and required user interaction. Successful exploitation can have high confidentiality, integrity, and availability impact within the affected user's security context.
Likely exposure
Potential exposure includes Microsoft 365 Apps for Enterprise, Office 2016, Office 2019, and Office LTSC 2021 installations listed in the source bundle. Actual exposure depends on installed builds and update status. The supplied version labels are not sufficient to determine precise vulnerable build ranges.
Exploitation context
Exploitation requires user interaction and local delivery according to the CVSS vector. The supplied sources do not establish active exploitation, and the CVE is not listed as KEV in the bundle. No exploit procedure or confirmed public weaponization evidence is provided.
Researcher notes
The bundle supplies a CVSS score, affected product families, CWE-59 classification, and Microsoft patch reference, but lacks precise vulnerable build boundaries and mechanism details. Researchers should use Microsoft's advisory and the authoritative CVE record to resolve build applicability. Do not infer active exploitation from severity or the recent record update.
Mitigation direction
- Apply the security updates identified in Microsoft's CVE-2024-30104 advisory.
- Prioritize Office endpoints handling documents from external or untrusted sources.
- Use existing controls to restrict or isolate suspicious Office content.
- Review Microsoft guidance for any product-specific mitigations or prerequisites.
Validation and detection
- Inventory installations of the four listed Microsoft Office product families.
- Compare installed Office builds and update status with Microsoft's advisory.
- Confirm the applicable security update installed successfully across managed endpoints.
- Review endpoint telemetry for suspicious Office-launched child processes or unexpected file access.
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-59: 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-30104 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.
Improper Link Resolution Before File Access ('Link Following')
Improper Link Resolution Before File Access ('Link Following') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.