Mattermost DesktopApplication · Mattermost

CVE-2024-45835

MEDIUM · 6.5 CVSS v3.1 Published 2024-09-16
Fix available
A fix is available. Upgrade to 5.9.0 or later.
See remediation →
74/100
Remediation priority · Elevated
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
Mattermost Desktop App versions <=5.8.0 fail to sufficiently configure Electron Fuses which allows an attacker to gather Chromium cookies or abuse other misconfigurations via remote/local access.

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

Mattermost Desktop App versions 5.8.0 and earlier fail to properly configure Electron Fuses, which are security-related binary flags in Electron that control features like cookie access and other Chromium security settings. This misconfiguration allows an attacker with local or remote system access to extract Chromium cookies or exploit other security weaknesses.

MitigationUpgrade Mattermost Desktop App to a version newer than 5.8.0 where Electron Fuses are properly configured, or manually reconfigure the Electron Fuses using the @electron/fuses tool to disable cookie access and other vulnerable features.

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
Mattermost DesktopApplication
Affected:< 5.9.0

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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 Mattermost Desktop version
    Open the app, go to Help > About Mattermost, or check the application's properties in the file system. On Windows, right-click the executable and view version info. On macOS, right-click the app and select Get Info.
    Affected if The version displayed is 5.8.0 or earlier, or any version below 5.9.0
  2. Check executable file path
    Locate the Mattermost Desktop executable file. Typical paths: Windows: %LOCALAPPDATA%\Mattermost\Mattermost.exe, macOS: /Applications/Mattermost.app/Contents/MacOS/Mattermost, Linux: /opt/mattermost-desktop/ or /usr/share/mattermost-desktop/
    Affected if The executable exists and its version (when checked in step 1) is below 5.9.0
  3. Verify Electron Fuses configuration
    Inspect the Mattermost executable using the @electron/fuses tool or a hex editor to check the state of the RunAsNode and EnableCookieEncryption Electron fuses. These fuses control whether the app runs as a standard Node.js binary and whether cookie encryption is enforced.
    Affected if The Electron Fuses are not properly configured (RunAsNode is enabled or EnableCookieEncryption is disabled), which is the case for all versions below 5.9.0 by default

You are affected if Mattermost Desktop version is below 5.9.0, as the default Electron Fuses misconfiguration exists in these versions and allows cookie extraction or other Chromium security bypasses.

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

Upgrade Mattermost Desktop App to a version newer than 5.8.0 where Electron Fuses are properly configured, or manually reconfigure the Electron Fuses using the @electron/fuses tool to disable cookie access and other vulnerable features.

Recommended fix High confidence

Mattermost Desktop 5.9.0

  1. 1. Download Mattermost Desktop App version 5.9.0 or later from the official Mattermost website or releases page
  2. 2. Close any running instances of the Mattermost Desktop App
  3. 3. Install the updated version by running the downloaded installer
  4. 4. After installation, verify the version by checking Help > Version to confirm you are on 5.9.0 or later
  5. 5. Restart the application to ensure all components are updated

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

Fix this in Mattermost Desktop Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
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,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-45835 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