dbcve.org
Debian LinuxOperating system · Debian

CVE-2022-3140

MEDIUM · 6.3 CVSS v3.1 Published 2022-10-11
Fix available
A fix is available. Upgrade to 7.3.6 or later.
See remediation →
70/100
Remediation priority · Elevated
Remotely reachable No privileges

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 supports Office URI Schemes to enable browser integration of LibreOffice with MS SharePoint server. An additional scheme 'vnd.libreoffice.command' specific to LibreOffice was added. In the affected versions of LibreOffice links using that scheme could be constructed to call internal macros with arbitrary arguments. Which when clicked on, or activated by document events, could result in arbitrary script execution without warning. This issue affects: The Document Foundation LibreOffice 7.4 versions prior to 7.4.1; 7.3 versions prior to 7.3.6.

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's 'vnd.libreoffice.command' URI scheme allows constructed links to invoke internal macros with arbitrary arguments. When users click these links or trigger them via document events, arbitrary script executes silently without any warning prompt.

MitigationUpgrade to LibreOffice 7.4.1+, 7.3.6+, or current supported version to patch the URI scheme handling. Restrict macro execution policies organization-wide as an additional defense-in-depth measure.

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
Debian LinuxOperating system
Affected:= 11.0
FedoraOperating system
Affected:= 35
LibreofficeApplication
Affected:>= 7.3.0, < 7.3.6= 7.4.0

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
Required
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

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

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 check installed packages: dpkg -l | grep libreoffice (Debian) or rpm -qa | grep libreoffice (Fedora)
    Affected if Version is 7.3.0 through 7.3.6 inclusive, or exactly 7.4.0
  2. Verify URI scheme handler registration
    Check if the vnd.libreoffice.command protocol handler is registered on the system. On Linux, examine /usr/share/applications or ~/.local/share/applications for .desktop files containing 'vnd.libreoffice.command' in the Protocol= field
    Affected if The URI scheme handler exists and is registered, allowing external links to trigger LibreOffice actions
  3. Check macro security settings
    Open LibreOffice > Tools > Options > Security > Macro Security. Note the macro security level setting (Low, Medium, High, Very High)
    Affected if Macro security is set to Low or Medium, permitting silent macro execution without warnings
  4. Inspect documents for embedded URI links
    Search document files (.odt, .ods, .odp) for the string 'vnd.libreoffice.command' using: grep -r 'vnd.libreoffice.command' /path/to/documents/
    Affected if Documents contain or reference the vnd.libreoffice.command URI scheme with macro arguments
  5. Review document event bindings
    Examine LibreOffice documents for event handlers. Open .odt/.ods files as ZIP archives and inspect content.xml for <script:event> elements with vnd.libreoffice.command: URIs
    Affected if Documents contain event bindings that execute macros via the vulnerable URI scheme

A user is affected if they have LibreOffice 7.3.0-7.3.6 or 7.4.0 installed AND have documents or are likely to click links that use the vnd.libreoffice.command URI scheme to trigger macros.

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.

dbcve · scoped
Upgrade available Upgrade to 7.3.6 or later
Fixed in 7.3.6
Interim mitigation

Upgrade to LibreOffice 7.4.1+, 7.3.6+, or current supported version to patch the URI scheme handling. Restrict macro execution policies organization-wide as an additional defense-in-depth measure.

Recommended fix High confidence

LibreOffice 7.4.1+ or LibreOffice 7.3.6+

  1. 1. Verify current LibreOffice version by opening LibreOffice and navigating to Help > About LibreOffice (or running 'libreoffice --version' in terminal)
  2. 2. For LibreOffice 7.4.x: Upgrade to version 7.4.1 or later
  3. 3. For LibreOffice 7.3.x: Upgrade to version 7.3.6 or later
  4. 4. On Debian 11 (bullseye): Run 'sudo apt update && sudo apt upgrade libreoffice' to obtain fixed packages
  5. 5. On Fedora 35: Run 'sudo dnf update libreoffice' to obtain fixed packages
  6. 6. After upgrade, verify the new version is installed: 'libreoffice --version'
  7. 7. Restart any running LibreOffice instances
Caveat Minor version upgrades typically have no breaking changes; however, some macro scripts or extensions may need re-validation after upgrade

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Debian Linux Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
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,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Get it on GitHub Scan in the browser

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-2022-3140 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