# CVE-2019-9847: Executable hyperlink targets executed unconditionally on activation

> Attackers can execute arbitrary code by tricking users into clicking hyperlinks pointing to local executables in LibreOffice documents.

- **Severity:** High 7.8 (`CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 9 May 2019
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-cxqx-7gmj-4vg7

## What is CVE-2019-9847?

CVE-2019-9847 is a high-severity code injection vulnerability in Libreoffice Libreoffice, published on 9 May 2019. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

A vulnerability in LibreOffice hyperlink processing allows an attacker to construct documents containing hyperlinks pointing to the location of an executable on the target users file system. If the hyperlink is activated by the victim the executable target is unconditionally launched. Under Windows and macOS when processing a hyperlink target explicitly activated by the user there was no judgment made on whether the target was an executable file, so such executable targets were launched unconditionally. This issue affects: All LibreOffice Windows and macOS versions prior to 6.1.6; LibreOffice Windows and macOS versions in the 6.2 series prior to 6.2.3.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2019-9847?

It affects 1 product.


Products: Libreoffice Libreoffice.

## How do I fix CVE-2019-9847?

No fix has been published for CVE-2019-9847 yet. Limit exposure of the affected software until one is available.

## Is CVE-2019-9847 being exploited?

There is no known exploitation of CVE-2019-9847 in the wild and no public exploit code.

## Other vulnerabilities in Libreoffice Libreoffice

- [CVE-2024-5261](https://insights.sbomify.com/CVE-2024-5261/): TLS certificate are not properly verified when utilizing LibreOfficeKit (critical 10.0)
- [CVE-2019-9855](https://insights.sbomify.com/CVE-2019-9855/): Windows 8.3 path equivalence handling flaw allows LibreLogo script execution (critical 9.8)
- [CVE-2018-14939](https://insights.sbomify.com/CVE-2018-14939/): Memory corruption in n/a (critical 9.8)
- [CVE-2017-8358](https://insights.sbomify.com/CVE-2017-8358/): Memory corruption in n/a (critical 9.8)
- [CVE-2017-7882](https://insights.sbomify.com/CVE-2017-7882/): Memory corruption in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-9847 and fix it if it is affected.

What it is: CVE-2019-9847 is a high-severity code injection vulnerability in Libreoffice Libreoffice, published on 9 May 2019. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2019-9847 in the wild and no public exploit code.

Affected product: Libreoffice Libreoffice. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2019-9847/ (Markdown: https://insights.sbomify.com/CVE-2019-9847/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2019-9847
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2019-9847
- OSV: https://osv.dev/vulnerability/CVE-2019-9847

---
From sbomify Insights: https://insights.sbomify.com/CVE-2019-9847/
Summaries are generated and may contain mistakes; the official description above is the record.