Security readout for executives and security teams
Plain-English summary
LibreOffice on Windows and macOS could launch a local executable when a user clicked a crafted document hyperlink. The attack depends on user interaction and the executable path existing on the victim system. The source bundle does not report active exploitation.
Executive priority
Treat this as a medium-priority endpoint hygiene issue unless affected LibreOffice versions are common in document-heavy teams. Patch legacy installations and reduce exposure to untrusted documents.
Technical view
CVE-2019-9847 affects LibreOffice hyperlink handling on Windows and macOS before 6.1.6, and 6.2 before 6.2.3. Activated hyperlinks targeting executable files were launched without an executable-file judgment. No CVSS, CWE, or exploit evidence is provided in the bundle.
Likely exposure
Exposure is likely where Windows or macOS endpoints still run affected LibreOffice versions and users open untrusted documents. Linux exposure is not identified in the provided sources.
Exploitation context
The provided KEV flag is false, and no cited source reports exploitation. A plausible attack path is social engineering a user into activating a crafted hyperlink in a document; the bundle does not support broader claims.
Researcher notes
Evidence is limited to the CVE description and LibreOffice advisory reference. The key boundary is user-activated hyperlinks to local executable targets on Windows and macOS; do not assume remote code execution without user interaction from these sources.
Mitigation direction
- Upgrade LibreOffice on Windows and macOS to 6.1.6, 6.2.3, or newer.
- Prioritize updates on systems that open external or emailed documents.
- Review vendor advisory details before applying compensating controls.
- Train users not to activate unexpected document hyperlinks.
Validation and detection
- Inventory LibreOffice versions on Windows and macOS endpoints.
- Confirm no affected versions remain below 6.1.6 or 6.2.3.
- Check document-handling workflows for untrusted external files.
- Verify endpoint controls log or restrict unexpected local executable launches.
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.
CVE-2019-9847 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
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
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.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://www.libreoffice.org/about-us/security/advisories/cve-2019-9847/CVE reference · x_refsource_CONFIRM
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.
