FedoraOperating system · Fedoraproject

CVE-2020-12802

MEDIUM · 5.3 CVSS v3.1 Published 2020-06-08
Fix available
A fix is available. Upgrade to 6.4.4 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
LibreOffice has a 'stealth mode' in which only documents from locations deemed 'trusted' are allowed to retrieve remote resources. This mode is not the default mode, but can be enabled by users who want to disable LibreOffice's ability to include remote resources within a document. A flaw existed where remote graphic links loaded from docx documents were omitted from this protection prior to version 6.4.4. This issue affects: The Document Foundation LibreOffice versions prior to 6.4.4.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

LibreOffice includes a 'stealth mode' that restricts remote resource loading to only documents from trusted locations. A flaw existed in versions prior to 6.4.4 where remote graphic links embedded in DOCX documents were excluded from this stealth mode protection, allowing remote images to load even when the feature was enabled by security-conscious users.

MitigationUpgrade LibreOffice to version 6.4.4 or later to receive the patch that corrects the stealth mode protection for remote graphics in DOCX files.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
FedoraOperating system
Affected:= 31
LibreofficeApplication
Affected:< 6.4.4
LeapOperating system
Affected:= 15.1= 15.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm LibreOffice installation and version
    Run 'libreoffice --version' or open LibreOffice and navigate to Help > About to view the exact version number
    Affected if The installed version is earlier than 6.4.4 (for example, 6.4.3, 6.4.2, 6.3.x, or earlier)
  2. Identify if stealth mode is enabled
    In LibreOffice, go to Tools > Options > Security > Security Options and look for the 'stealth mode' or 'restrict remote content loading' setting, or check the relevant configuration file in the user profile
    Affected if Stealth mode is explicitly turned ON (the vulnerability only affects users who have enabled this feature expecting protection)
  3. Determine if you work with DOCX documents
    Review your workflow to see if you open or create Microsoft Word DOCX files that may contain embedded images
    Affected if You regularly open DOCX files from untrusted or external sources
  4. Check for remote image references in DOCX files
    Open a DOCX file in LibreOffice, right-click any embedded image, and check if the image source URL points to an external HTTP/HTTPS location rather than a local file path
    Affected if DOCX documents you open contain remote graphic links pointing to external URLs

You are affected if LibreOffice version is below 6.4.4, stealth mode is enabled, and you open DOCX documents containing remote image URLs

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to 6.4.4 or later
Fixed in 6.4.4
Interim mitigation

Upgrade LibreOffice to version 6.4.4 or later to receive the patch that corrects the stealth mode protection for remote graphics in DOCX files.

Fix this in Fedora Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,424.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-12802 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2020-12802 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data