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

Insufficient URL decoding flaw in categorizing macro location

LibreOffice documents can contain macros. The execution of those macros is controlled by the document security settings, typically execution of macros are blocked by default. A URL decoding flaw existed in how the urls to the macros within the document were processed and categorized, resulting in the possibility to construct a document where macro execution bypassed the security settings. The documents were correctly detected as containing macros, and prompted the user to their existence within the documents, but macros within the document were subsequently not controlled by the security settings allowing arbitrary macro execution This issue affects: LibreOffice 6.2 series versions prior to 6.2.7; LibreOffice 6.3 series versions prior to 6.3.1.

HighCVSS 7.8 · v3.1—No exploit Fix available
Published
Sep 27, 2019
Updated
Jun 16, 2026
EPSS
3.1% · 87th 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

32

Monitor

Low priority for now.

CVSS
31 / 40 · 7.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
1 / 30 · 3.1%

Affected systems

VendorProduct
libreofficelibreoffice

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.6
  • libreoffice libreoffice6.3.0 and later · before 6.3.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 series and later · before 6.2.7affected
    • 6.3 series 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
Debian:10libreofficebefore 1:6.1.5-3+deb10u31:6.1.5-3+deb10u3
Debian:12libreofficebefore 1:6.3.0-11:6.3.0-1
Debian:8libreofficebefore 1:4.3.3-2+deb8u131:4.3.3-2+deb8u13
Debian:9libreofficebefore 1:5.2.7-1+deb9u101:5.2.7-1+deb9u10
openSUSE:Leap 15.1cmis-clientbefore 0.5.2-lp151.3.3.10.5.2-lp151.3.3.1
openSUSE:Leap 15.1libixionbefore 0.15.0-lp151.4.6.10.15.0-lp151.4.6.1
openSUSE:Leap 15.1libmwawbefore 0.3.15-lp151.2.3.10.3.15-lp151.2.3.1
openSUSE:Leap 15.1liborcusbefore 0.15.3-lp151.3.6.10.15.3-lp151.3.6.1
openSUSE:Leap 15.1libreofficebefore 6.3.3.2-lp151.3.9.16.3.3.2-lp151.3.9.1
openSUSE:Leap 15.1mdds-1_5before 1.5.0-lp151.2.11.5.0-lp151.2.1
openSUSE:Leap 15.1myspell-dictionariesbefore 20191016-lp151.2.6.120191016-lp151.2.6.1
openSUSE:Leap 15.1spdlogbefore 0.16.3-lp151.3.3.10.16.3-lp151.3.3.1
openSUSE:Tumbleweedlibreofficebefore 7.1.5.2-3.137.1.5.2-3.13
Red Hat:enterprise_linux:7::clientautocorr-afbefore 1:5.3.6.1-24.el71:5.3.6.1-24.el7
Red Hat:enterprise_linux:7::clientautocorr-bgbefore 1:5.3.6.1-24.el71:5.3.6.1-24.el7
Red Hat:enterprise_linux:7::clientautocorr-cabefore 1:5.3.6.1-24.el71:5.3.6.1-24.el7
Red Hat:enterprise_linux:7::clientautocorr-csbefore 1:5.3.6.1-24.el71:5.3.6.1-24.el7
Red Hat:enterprise_linux:7::clientautocorr-dabefore 1:5.3.6.1-24.el71:5.3.6.1-24.el7
Red Hat:enterprise_linux:7::clientautocorr-debefore 1:5.3.6.1-24.el71:5.3.6.1-24.el7
Red Hat:enterprise_linux:7::clientautocorr-enbefore 1:5.3.6.1-24.el71:5.3.6.1-24.el7
Red Hat:enterprise_linux:7::clientautocorr-esbefore 1:5.3.6.1-24.el71:5.3.6.1-24.el7
Red Hat:enterprise_linux:7::clientautocorr-fabefore 1:5.3.6.1-24.el71:5.3.6.1-24.el7
Red Hat:enterprise_linux:7::clientautocorr-fibefore 1:5.3.6.1-24.el71:5.3.6.1-24.el7
Red Hat:enterprise_linux:7::clientautocorr-frbefore 1:5.3.6.1-24.el71:5.3.6.1-24.el7

+96

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
debian:libreoffice1:6.3.0-1 · Debian:12Package registry (OSV)
opensuse:cmis-client0.5.2-lp151.3.3.1 · openSUSE:Leap 15.1Package registry (OSV)
opensuse:libixion0.15.0-lp151.4.6.1 · openSUSE:Leap 15.1Package registry (OSV)
opensuse:libmwaw0.3.15-lp151.2.3.1 · openSUSE:Leap 15.1Package registry (OSV)
opensuse:liborcus0.15.3-lp151.3.6.1 · openSUSE:Leap 15.1Package registry (OSV)
opensuse:libreoffice6.3.3.2-lp151.3.9.1 · openSUSE:Leap 15.1Package registry (OSV)
opensuse:mdds-1_51.5.0-lp151.2.1 · openSUSE:Leap 15.1Package registry (OSV)
opensuse:myspell-dictionaries20191016-lp151.2.6.1 · openSUSE:Leap 15.1Package registry (OSV)
opensuse:spdlog0.16.3-lp151.3.3.1 · openSUSE:Leap 15.1Package registry (OSV)
red hat:autocorr-af1:5.3.6.1-24.el7 · Red Hat:enterprise_linux:7::clientPackage registry (OSV)
red hat:autocorr-bg1:5.3.6.1-24.el7 · Red Hat:enterprise_linux:7::clientPackage registry (OSV)
red hat:autocorr-ca1:5.3.6.1-24.el7 · Red Hat:enterprise_linux:7::clientPackage registry (OSV)
red hat:autocorr-cs1:5.3.6.1-24.el7 · Red Hat:enterprise_linux:7::clientPackage registry (OSV)
red hat:autocorr-da1:5.3.6.1-24.el7 · Red Hat:enterprise_linux:7::clientPackage registry (OSV)
red hat:autocorr-de1:5.3.6.1-24.el7 · Red Hat:enterprise_linux:7::clientPackage registry (OSV)
red hat:autocorr-en1:5.3.6.1-24.el7 · Red Hat:enterprise_linux:7::clientPackage registry (OSV)
red hat:autocorr-es1:5.3.6.1-24.el7 · Red Hat:enterprise_linux:7::clientPackage registry (OSV)
red hat:autocorr-fa1:5.3.6.1-24.el7 · Red Hat:enterprise_linux:7::clientPackage registry (OSV)
red hat:autocorr-fi1:5.3.6.1-24.el7 · Red Hat:enterprise_linux:7::clientPackage registry (OSV)
red hat:autocorr-fr1:5.3.6.1-24.el7 · Red Hat:enterprise_linux:7::clientPackage registry (OSV)
red hat:autocorr-ga1:5.3.6.1-24.el7 · Red Hat:enterprise_linux:7::clientPackage registry (OSV)
suse:bluez5.13-5.20.6 · SUSE:Linux Enterprise Software Development Kit 12 SP4Package registry (OSV)
suse:cmis-client0.5.2-9.3.1 · SUSE:Linux Enterprise Software Development Kit 12 SP4Package registry (OSV)
suse:gperf3.1-19.4.1 · SUSE:Linux Enterprise Software Development Kit 12 SP4Package registry (OSV)
suse:libixion0.15.0-13.12.1 · SUSE:Linux Enterprise Software Development Kit 12 SP4Package registry (OSV)
suse:libmwaw0.3.15-7.15.1 · SUSE:Linux Enterprise Software Development Kit 12 SP4Package registry (OSV)
suse:liborcus0.15.3-10.15.1 · SUSE:Linux Enterprise Software Development Kit 12 SP4Package registry (OSV)
suse:libreoffice6.3.3.2-8.13.1 · SUSE:Linux Enterprise Workstation Extension 15 SP1Package registry (OSV)
suse:myspell-dictionaries20191016-16.21.1 · SUSE:Linux Enterprise Workstation Extension 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.

  • Nils EmmerichERNW Research GmbH for discovering and reporting this issue

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

  • Someone with local access to the system can trigger it.
  • No account or password is required.
  • A user must open a link or visit a page.
  • 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
Local
Attack complexity
Low
Privileges required
None
User interaction
Required
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

CVSS vector

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/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.

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

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records