CVE-2019-9855: Windows 8.3 path equivalence handling flaw allows LibreLogo script execution
Noroxi assessment
Priority: Plan (action score 40/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 2.9% (FIRST EPSS); higher than 87.4% of all records.
- 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.
- Fixed version: libreoffice (Alpine:v3.10) 6.2.7.1-r0; libreoffice (Alpine:v3.11) 6.3.1.2-r0; libreoffice (openSUSE:Leap 15.0) 6.2.7.1-lp150.2.19.1.
Add it to your regular patch cycle. Upgrade to libreoffice (Alpine:v3.10) 6.2.7.1-r0; libreoffice (Alpine:v3.11) 6.3.1.2-r0; libreoffice (openSUSE:Leap 15.0) 6.2.7.1-lp150.2.19.1 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Sep 6, 2019
- Updated
- Jun 16, 2026
- EPSS
- 2.9% · 87th percentile
- CWE
- CWE-417
Report tools
Action score
40
Add it to your regular patch cycle.
- CVSS
- 39 / 40 · 9.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 2.9%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| libreoffice | libreoffice | cpe:2.3:a:libreoffice:libreoffice |
| microsoft | windows | cpe:2.3:o:microsoft:windows |
| opensuse | leap | cpe:2.3:o:opensuse:leap |
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
Affected versions · NVD (4)
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
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Alpine:v3.10 | libreoffice | from 6.2.0 · before 6.2.7.1-r0 | 6.2.7.1-r0 |
| Alpine:v3.11 | libreoffice | from 6.2.0 · before 6.3.1.2-r0 | 6.3.1.2-r0 |
| openSUSE:Leap 15.0 | libreoffice | before 6.2.7.1-lp150.2.19.1 | 6.2.7.1-lp150.2.19.1 |
| openSUSE:Leap 15.1 | libreoffice | before 6.2.7.1-lp151.3.6.1 | 6.2.7.1-lp151.3.6.1 |
| SUSE:Linux Enterprise Desktop 12 SP4 | libreoffice | before 6.2.7.1-43.56.3 | 6.2.7.1-43.56.3 |
| SUSE:Linux Enterprise Workstation Extension 15 | libreoffice | before 6.2.7.1-3.24.4 | 6.2.7.1-3.24.4 |
| SUSE:Linux Enterprise Workstation Extension 15 SP1 | libreoffice | before 6.2.7.1-8.10.1 | 6.2.7.1-8.10.1 |
Same product
libreoffice: all recordsOther highest-scoring records for the same primary product.
- CVE-2019-9851LibreLogo global-event script execution62This 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…60This week
- CVE-2018-10583An information disclosure vulnerability occurs when LibreOffice 6.0.3 and Apache OpenOffice Writer 4.1.5 automatically process and initiate…60This week
Published before and after this one in the same product
- ← EarlierCVE-2019-9852Aug 15, 2019 · Insufficient URL encoding flaw in allowed script location check32Monitor
- ← EarlierCVE-2019-9854Sep 6, 2019 · Unsafe URL assembly flaw in allowed script location check32Monitor
- Later →CVE-2019-9853Sep 27, 2019 · Insufficient URL decoding flaw in categorizing macro location32Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| alpine:libreoffice | 6.2.7.1-r0 · Alpine:v3.10 | Package registry (OSV) |
| opensuse:libreoffice | 6.2.7.1-lp151.3.6.1 · openSUSE:Leap 15.1 | Package registry (OSV) |
| suse:libreoffice | 6.2.7.1-43.56.3 · SUSE:Linux Enterprise Desktop 12 SP4 | Package 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.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
Not on record for this CVE: EPSS history · patch commit or PR link · variant or chain candidate · public bounty program.
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
Weakness class (CWE)
CWE-417 · Communication Channel ErrorsCVSS 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.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.