dbcve.org
Improper Certificate ValidationWeakness · CWE-295

CVE-2024-37311

HIGH · 8.2 CVSS v3.1 Published 2024-08-23
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
91/100
Remediation priority · Urgent
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
Collabora Online is a collaborative online office suite based on LibreOffice. In affected versions of Collabora Online, https connections from coolwsd to other hosts may incompletely verify the remote host's certificate's against the full chain of trust. This vulnerability is fixed in Collabora Online 24.04.4.3, 23.05.14.1, and 22.05.23.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

Collabora Online's coolwsd component incompletely verifies SSL/TLS certificates when making HTTPS connections to remote hosts, failing to validate the full certificate chain of trust. This allows potential man-in-the-middle attacks where an attacker could intercept encrypted communications between coolwsd and external hosts.

MitigationUpgrade Collabora Online to version 24.04.4.3, 23.05.14.1, or 22.05.23.1 to obtain the fixed certificate chain validation. If immediate patching is not possible, avoid transmitting sensitive data over HTTPS connections from coolwsd to untrusted networks.

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

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
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/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 coolwsd is installed
    Check for the presence of the coolwsd process or binary on the system. On Linux systems, run 'ps aux | grep coolwsd' or check for the binary in common installation paths like /usr/bin/coolwsd, /opt/collaboraoffice*/program/coolwsd, or similar.
    Affected if coolwsd process or binary is found running or installed on the system
  2. Identify installed Collabora Online version
    Run the command to retrieve the Collabora Online version. Common methods include 'coolwsd --version', 'coolwsd -v', checking the package version (dpkg -l | grep coolwsd or rpm -qa | grep coolwsd), or inspecting the product version file in the installation directory.
    Affected if The installed version is 24.04.0 through 24.04.4.2, 23.05.0 through 23.05.14.0, or 22.05.0 through 22.05.23.0 (versions before the fixed releases)
  3. Check if coolwsd connects to remote HTTPS hosts
    Review the coolwsd configuration file (typically coolwsd.xml in /etc/coolwsd/ or the configuration directory) for settings that enable connections to external hosts over HTTPS, such as WOPI storage settings, external converter settings, or any remote URL configurations.
    Affected if The configuration contains HTTPS URLs pointing to remote hosts for storage, conversion, or other features
  4. Verify SSL certificate validation configuration
    Examine the coolwsd configuration for SSL-related settings. Check for options like <ssl_verification>, <verify>, or similar settings in the coolwsd.xml file that control certificate chain validation behavior.
    Affected if SSL verification is disabled, set to false, or explicitly configured to skip chain validation when connecting to remote HTTPS hosts

A system is affected if coolwsd is installed with a version in the 22.05.x, 23.05.x, or 24.04.x series before the fixed releases (22.05.23.1, 23.05.14.1, 24.04.4.3) AND coolwsd is configured to make HTTPS connections to remote hosts.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Collabora Online to version 24.04.4.3, 23.05.14.1, or 22.05.23.1 to obtain the fixed certificate chain validation. If immediate patching is not possible, avoid transmitting sensitive data over HTTPS connections from coolwsd to untrusted networks.

Recommended fix High confidence

Collabora Online 24.04.4.3 (or 23.05.14.1 for 23.x, or 22.05.23.1 for 22.x)

  1. Identify the currently installed Collabora Online version using your package manager or system inventory
  2. Back up the current Collabora Online configuration, including coolwsd.conf and any custom settings
  3. Upgrade to Collabora Online 24.04.4.3 if running a 24.x release, or to 23.05.14.1 if running a 23.x release, or to 22.05.23.1 if running a 22.x release
  4. Verify the upgrade completed successfully by checking the installed package version
  5. Restart the coolwsd service to apply the new version
  6. Confirm the service is running and accessible
Caveat Review release notes for the target version to check for any breaking changes or migration requirements

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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