dbcve.org
Rocket.chatApplication

CVE-2022-44567

CRITICAL · 9.8 CVSS v3.1 Published 2022-12-23
Fix available
A fix is available. Upgrade to 3.8.14 or later.
See remediation →
100/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
A command injection vulnerability exists in Rocket.Chat-Desktop <3.8.14 that could allow an attacker to pass a malicious url of openInternalVideoChatWindow to shell.openExternal(), which may lead to remote code execution (internalVideoChatWindow.ts#L17). To exploit the vulnerability, the internal video chat window must be disabled or a Mac App Store build must be used (internalVideoChatWindow.ts#L14). The vulnerability may be exploited by an XSS attack because the function openInternalVideoChatWindow is exposed in the Rocket.Chat-Desktop-API.

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

A command injection vulnerability in Rocket.Chat-Desktop <3.8.14 allows a malicious URL passed to shell.openExternal() through the openInternalVideoChatWindow function to execute arbitrary code. The function is exposed via the Rocket.Chat-Desktop-API, enabling exploitation through XSS attacks when the internal video chat window is disabled or on Mac App Store builds.

MitigationUpgrade Rocket.Chat-Desktop to version 3.8.14 or later. As a compensating control, ensure the internal video chat window is enabled (not disabled) until the patch is applied.

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
Rocket.chatApplication
Affected:< 3.8.14

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

CVSS:3.1/AV:N/AC:L/PR:N/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 checks

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

  1. Identify Rocket.Chat-Desktop installation
    Locate the Rocket.Chat-Desktop application on the system - check common installation directories for desktop applications (e.g., Program Files on Windows, Applications folder on macOS, or the user's home directory on Linux)
    Affected if Rocket.Chat-Desktop is installed on the system
  2. Determine installed version
    Open Rocket.Chat-Desktop and navigate to the application menu (Help > About or similar) to view the version number, or check the application metadata files in the installation directory
    Affected if The installed version is lower than 3.8.14
  3. Check if internal video chat window is disabled
    Access the Rocket.Chat-Desktop settings or configuration. Look for options related to video chat, internal video chat window, or communication settings. Determine if the internal video chat window feature is disabled or turned off
    Affected if The internal video chat window is disabled (not enabled) AND the version is below 3.8.14
  4. Verify if running Mac App Store build
    On macOS systems, check the application origin or package information to determine if the Rocket.Chat-Desktop installation came from the Mac App Store (typically indicated in the app metadata or receipt information)
    Affected if Running a Mac App Store build of Rocket.Chat-Desktop AND the version is below 3.8.14

A user is affected if Rocket.Chat-Desktop version is below 3.8.14 AND either the internal video chat window is disabled OR the application is a Mac App Store build.

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 3.8.14 or later
Fixed in 3.8.14
Interim mitigation

Upgrade Rocket.Chat-Desktop to version 3.8.14 or later. As a compensating control, ensure the internal video chat window is enabled (not disabled) until the patch is applied.

Recommended fix High confidence

Rocket.Chat-Desktop version 3.8.14 or later

  1. 1. Check current Rocket.Chat-Desktop version by going to Help > About or checking the application metadata
  2. 2. Download Rocket.Chat-Desktop version 3.8.14 or later from the official releases repository
  3. 3. Close the running Rocket.Chat-Desktop instance completely
  4. 4. Install the updated version by running the downloaded installer
  5. 5. After installation, verify the version shows 3.8.14 or higher in Help > About
  6. 6. Test that internal video chat functionality works as expected after the update

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

Fix this in Rocket.chat Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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