{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-9847 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-9847 yet. Limit exposure of the affected software until one is available.","what":"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."},"fix_prompt":"Check this codebase for CVE-2019-9847 and fix it if it is affected.\n\nWhat 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.\nExploitation: There is no known exploitation of CVE-2019-9847 in the wild and no public exploit code.\n\nAffected product: Libreoffice Libreoffice. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2019-9847/ (Markdown: https://insights.sbomify.com/CVE-2019-9847/index.md)","id":"CVE-2019-9847","markdown":"https://insights.sbomify.com/CVE-2019-9847/index.md","name":"CVE-2019-9847","record":{"aliases":["GHSA-cxqx-7gmj-4vg7"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"LibreOffice office suite","requires_auth":"none","summary":"Attackers can execute arbitrary code by tricking users into clicking hyperlinks pointing to local executables in LibreOffice documents.","user_interaction":"required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Document Fdn.","cpe":[{"product":"libreoffice","vendor":"libreoffice"}],"cvss":{"score":7.8,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-20","name":"Improper Input Validation"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Executable hyperlink targets executed unconditionally on activation","id":"CVE-2019-9847","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"libreoffice:libreoffice","products":["libreoffice:libreoffice"],"type":"code_injection","year":"2019"},"n_packages":0,"n_references":1,"next":{"headline":"Code injection in LibreOffice","id":"CVE-2019-9848"},"packages":[],"prev":{"headline":"SQL injection in n/a","id":"CVE-2019-9846"},"products":["LibreOffice"],"published":"2019-05-09","related":[{"cvss_score":10,"headline":"TLS certificate are not properly verified when utilizing LibreOfficeKit","id":"CVE-2024-5261","kev_date_added":null,"published":"2024-06-25"},{"cvss_score":9.8,"headline":"Windows 8.3 path equivalence handling flaw allows LibreLogo script execution","id":"CVE-2019-9855","kev_date_added":null,"published":"2019-09-06"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2018-14939","kev_date_added":null,"published":"2018-08-05"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2017-8358","kev_date_added":null,"published":"2017-04-30"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2017-7882","kev_date_added":null,"published":"2017-04-15"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2016-10327","kev_date_added":null,"published":"2017-04-14"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2017-7856","kev_date_added":null,"published":"2017-04-14"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-09-16","vendors":["Document Foundation"]},"summary":"Attackers can execute arbitrary code by tricking users into clicking hyperlinks pointing to local executables in LibreOffice documents.","url":"https://insights.sbomify.com/CVE-2019-9847/"}