Debian LinuxOperating system · Debian
CVE-2022-26307
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 · uneditedLibreOffice 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 master key was poorly encoded resulting in weakening its entropy from 128 to 43 bits making the stored passwords vulerable to a brute force attack if an attacker has access to the users stored config. This issue affects: The Document Foundation LibreOffice 7.2 versions prior to 7.2.7; 7.3 versions prior to 7.3.3.
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 confidenceLibreOffice stored web connection passwords encrypted with a user-provided master key that was poorly encoded, reducing cryptographic entropy from 128 bits to only 43 bits. This severe weakening enables offline brute-force attacks against the encrypted credentials if an attacker obtains access to the user's configuration database.
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
= 10.0>= 7.2.0, < 7.2.7>= 7.3.0, < 7.3.3CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Identify LibreOffice installationRun 'libreoffice --version' or check for LibreOffice in installed packagesAffected if LibreOffice is installed and version is >= 7.2.0 but < 7.2.7, or >= 7.3.0 but < 7.3.3
-
Check for stored web connection passwordsExamine the user's LibreOffice configuration directory for saved credentials related to web connections (such as stored passwords for online account or webdav connections)Affected if any web connection passwords have been saved using the Remember Password feature in LibreOffice
-
Verify configuration database accessibilityLocate the LibreOffice user profile directory containing the encrypted credential store (typically under user configuration folders)Affected if the configuration database file containing encrypted web passwords exists and is readable by the user account
You are affected if LibreOffice version 7.2.0-7.2.6 or 7.3.0-7.3.2 is installed AND you have stored web connection passwords in the configuration database, as the weak 43-bit encryption enables offline brute-force recovery of those credentials.
Generated from the published advisory. Verify against your own configuration.
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 · scoped7.2.77.3.3
Upgrade to LibreOffice 7.2.7, 7.3.3, or later versions; additionally restrict filesystem access to user configuration directories to prevent exposure of the encrypted credential store.
LibreOffice 7.2.7 or 7.3.3 or later; Debian 10.0 security updates
- For Debian 10.0 systems: Run 'apt update && apt install --only-upgrade libreoffice' to apply the patched version from Debian security repositories
- For other systems: Download and install LibreOffice version 7.2.7 or later, or version 7.3.3 or later from the official LibreOffice website
- After upgrading, verify the installed version matches or exceeds the fixed releases using ' libreoffice --version'
- Consider changing any stored web connection passwords after the upgrade as a precautionary measure
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Debian Linux
Scoped from the published advisory
- Consultation3.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,880.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-26307 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-26307 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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