dbcve.org
Debian LinuxOperating system · Debian

CVE-2022-26306

HIGH · 7.5 CVSS v3.1 Published 2022-07-25
Fix available
A fix is available. Upgrade to 7.2.7 / 7.3.3 or later.
See remediation →
84/100
Remediation priority · High
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 supports the storage of passwords for web connections in the user’s configuration database. The stored passwords are encrypted with a single master key provided by the user. A flaw in LibreOffice existed where the required initialization vector for encryption was always the same which weakens the security of the encryption making them vulnerable if an attacker has access to the user's configuration data. This issue affects: The Document Foundation LibreOffice 7.2 versions prior to 7.2.7; 7.3 versions prior to 7.3.1.

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 stored web connection passwords encrypted with a user-provided master key, but used a static initialization vector (IV) for all encryptions. This cryptographic weakness makes the encryption vulnerable to pattern analysis and exploitation if an attacker obtains access to the user's configuration database.

MitigationUpdate LibreOffice to version 7.2.7, 7.3.1, or later which implement proper unique initialization vectors for password encryption.

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:= 10.0
LibreofficeApplication
Affected:>= 7.2.0, < 7.2.7>= 7.3.0, < 7.3.3

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
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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. Check LibreOffice version
    Run 'libreoffice --version' or 'soffice --version' to get the installed version number
    Affected if Version is 7.2.0 through 7.2.6, or 7.3.0 through 7.3.2, or the system is Debian 10.0 with LibreOffice in the affected range
  2. Verify web connections feature is in use
    Inspect the user profile directory for LibreOffice connection data. On Linux this is typically in ~/.config/libreoffice/ - look for files in user/registry/data/org/openoffice/Office/Connections.xcu or similar connection configuration files
    Affected if Connection configuration files exist and contain stored web connection entries with encrypted passwords
  3. Confirm master password encryption is enabled
    Check if the master password feature has been set up for web connections. This can be verified by examining LibreOffice preferences for saved passwords, typically in the Tools > Options > Security > Master Password dialog or by inspecting the password encryption configuration in the user profile
    Affected if Master password protection is enabled for web connection passwords and passwords are stored in the configuration database

A user is affected if they run a vulnerable LibreOffice version AND have stored web connection passwords using the master password encryption feature, since the static IV only matters when passwords are actually stored.

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.2.7 / 7.3.3 or later
Fixed in 7.2.77.3.3
Interim mitigation

Update LibreOffice to version 7.2.7, 7.3.1, or later which implement proper unique initialization vectors for password encryption.

Recommended fix High confidence

LibreOffice 7.2.7+ or 7.3.3+ (latest stable 7.3.x recommended)

  1. 1. Identify the currently installed LibreOffice version by checking Help > About LibreOffice or running 'libreoffice --version' in terminal
  2. 2. For LibreOffice 7.2.x: Upgrade to version 7.2.7 or later (recommended: 7.2.7)
  3. 3. For LibreOffice 7.3.x: Upgrade to version 7.3.3 or later (recommended: 7.3.4 or latest stable 7.3.x)
  4. 4. Download the updated version from the official LibreOffice website (www.libreoffice.org) or use your system's package manager (e.g., 'apt update && apt upgrade libreoffice' for Debian)
  5. 5. After upgrading, verify the new version is installed correctly
Caveat Minor: Standard upgrade; ensure user preferences and extensions are compatible with the new version

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
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
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,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-26306 — 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-26306 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