dbcve.org
Rocket.chatApplication

CVE-2024-45621

MEDIUM · 5.4 CVSS v3.1 Published 2024-09-02
Fix available
A fix is available. Upgrade to after 6.3.4 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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
The Electron desktop application of Rocket.Chat through 6.3.4 allows stored XSS via links in an uploaded file, related to failure to use a separate browser upon encountering third-party external actions from PDF documents.

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 · moderate confidence

The Rocket.Chat Electron desktop application through version 6.3.4 contains a stored XSS vulnerability where malicious links embedded in uploaded PDF documents can execute arbitrary JavaScript. This occurs because the application fails to isolate PDF external actions in a separate browser context, allowing third-party external actions from PDFs to run in the application's main context.

MitigationUpdate the Rocket.Chat Electron desktop application to a version beyond 6.3.4 that includes the security patch. Until patched, consider disabling PDF preview functionality or restricting file uploads to trusted sources.

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:<= 6.3.4

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
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/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. Identify if Rocket.Chat Electron desktop app is installed
    Locate the Rocket.Chat Electron application on the system (common locations: Program Files on Windows, Applications folder on macOS, .local/share or /opt on Linux)
    Affected if The application is present on the system
  2. Determine the installed Rocket.Chat Electron version
    Open the application and navigate to its About/Version information, or use the application's --version command-line flag if available
    Affected if The installed version is 6.3.4 or lower
  3. Verify PDF preview functionality is accessible
    Check if the Rocket.Chat server or desktop application has PDF preview enabled - this is typically found in application settings, file handling preferences, or workspace administration settings
    Affected if PDF preview is enabled and users can view uploaded PDF files
  4. Confirm PDF upload capability exists
    Verify that file uploads are permitted in the Rocket.Chat workspace - check if users can attach and upload PDF documents to channels or direct messages
    Affected if Users can upload PDF files to the application

A user is affected if Rocket.Chat Electron version 6.3.4 or lower is installed AND PDF preview/upload functionality is enabled, allowing malicious PDFs with embedded external actions to execute JavaScript in the application's main context.

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 a release after 6.3.4
Interim mitigation

Update the Rocket.Chat Electron desktop application to a version beyond 6.3.4 that includes the security patch. Until patched, consider disabling PDF preview functionality or restricting file uploads to trusted sources.

Recommended fix Moderate confidence

Latest stable Rocket.Chat desktop client version (newer than 6.3.4)

  1. 1. Check the current installed version of Rocket.Chat desktop client by navigating to the app's 'About' section or checking in system settings
  2. 2. Download the latest version of Rocket.Chat desktop client from the official GitHub releases page (github.com/RocketChat/Rocket.Chat.Electron) or the official Rocket.Chat website
  3. 3. Close the current Rocket.Chat desktop application completely before updating
  4. 4. Install the latest version, which includes the security fix for the stored XSS vulnerability in PDF handling
  5. 5. After installation, verify the new version number in the 'About' section to confirm the update was applied
Caveat Desktop client updates typically do not affect server compatibility, but ensure your Rocket.Chat server version is also kept current for best compatibility

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

Fix this in Rocket.chat Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing5.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,790
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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