Skip to content
Noroxi
CVE-2019-9855· NVD / CVE Program· CNA Document Fdn.

Windows 8.3 path equivalence handling flaw allows LibreLogo script execution

LibreOffice is typically bundled with LibreLogo, a programmable turtle vector graphics script, which can execute arbitrary python commands contained with the document it is launched from. LibreOffice also has a feature where documents can specify that pre-installed scripts can be executed on various document script events such as mouse-over, etc. Protection was added to block calling LibreLogo from script event handers. However a Windows 8.3 path equivalence handling flaw left LibreOffice vulnerable under Windows that a document could trigger executing LibreLogo via a Windows filename pseudonym. This issue affects: Document Foundation LibreOffice 6.2 versions prior to 6.2.7; 6.3 versions prior to 6.3.1.

CriticalCVSS 9.8 · v3.1—No exploit Fix available
Published
Sep 6, 2019
Updated
Jun 16, 2026
EPSS
2.6% · 85th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

40

Plan

Add it to your regular patch cycle.

CVSS
39 / 40 · 9.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
1 / 30 · 2.6%

Affected systems

VendorProduct
libreofficelibreoffice
microsoftwindows
opensuseleap

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • libreoffice libreoffice6.2.0 and later · before 6.2.7
  • libreoffice libreoffice6.3.0 and later · before 6.3.1
  • opensuse leap15.0
  • opensuse leap15.1

Versions reported by the vendor

Affected version ranges reported by the assigning authority (Document Fdn.). Independent of NVD's CPE analysis and usually ahead of it.

  • Document Foundation LibreOffice

    • 6.2 and later · before 6.2.7affected
    • 6.3 and later · before 6.3.1affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
openSUSE:Leap 15.0libreofficebefore 6.2.7.1-lp150.2.19.16.2.7.1-lp150.2.19.1
openSUSE:Leap 15.1libreofficebefore 6.2.7.1-lp151.3.6.16.2.7.1-lp151.3.6.1
SUSE:Linux Enterprise Desktop 12 SP4libreofficebefore 6.2.7.1-43.56.36.2.7.1-43.56.3
SUSE:Linux Enterprise Workstation Extension 15libreofficebefore 6.2.7.1-3.24.46.2.7.1-3.24.4
SUSE:Linux Enterprise Workstation Extension 15 SP1libreofficebefore 6.2.7.1-8.10.16.2.7.1-8.10.1

Other highest-scoring records for the same primary product.

  • CVE-2019-9851LibreLogo global-event script execution
    62This week
  • CVE-2018-16858It was found that libreoffice before versions 6.0.7 and 6.1.3 was vulnerable to a directory traversal attack which could be used to execute
    59Plan
  • CVE-2018-10583An information disclosure vulnerability occurs when LibreOffice 6.0.3 and Apache OpenOffice Writer 4.1.5 automatically process and initiate
    54Plan
  • CVE-2019-9848LibreOffice has a feature where documents can specify that pre-installed scripts can be executed on various document events such as mouse-ov
    48Plan
  • CVE-2018-6871LibreOffice before 5.4.5 and 6.x before 6.0.1 allows remote attackers to read arbitrary files via =WEBSERVICE calls in a document, which use
    46Plan
  • CVE-2023-1183Arbitrary file write
    41Plan

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
opensuse:libreoffice6.2.7.1-lp151.3.6.1 · openSUSE:Leap 15.1Package registry (OSV)
suse:libreoffice6.2.7.1-43.56.3 · SUSE:Linux Enterprise Desktop 12 SP4Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records