dbcve.org
Mattermost ServerApplication · Mattermost

CVE-2024-32045

MEDIUM · 5.9 CVSS v3.1 Published 2024-05-26
Fix available
A fix is available. Upgrade to 8.1.13 / 9.5.4 or later.
See remediation →
65/100
Remediation priority · Elevated
Remotely reachable 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 versions 9.5.x <= 9.5.3, 9.6.x <= 9.6.1, 8.1.x <= 8.1.12 fail to enforce proper access controls for channel and team membership when linking a playbook run to a channel which allows members to link their runs to private channels they were not members of.

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 fails to enforce proper access controls when linking playbook runs to channels, allowing authenticated members to link runs to private channels they are not members of. This is an authorization bypass in the playbook run linking functionality across multiple affected versions.

MitigationUpgrade Mattermost to versions 9.5.4, 9.6.2, 8.1.13 or later to resolve the access control vulnerability.

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 ServerApplication
Affected:>= 8.1.0, < 8.1.13>= 9.5.0, < 9.5.4>= 9.6.0, < 9.6.2

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
High
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:H/PR:L/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. Check Mattermost Server version
    Run `grep -i version /opt/mattermost/version.txt` or access Mattermost System Console > About to view the installed server version
    Affected if Version is >= 8.1.0 and < 8.1.13, OR >= 9.5.0 and < 9.5.4, OR >= 9.6.0 and < 9.6.2
  2. Verify Playbooks plugin is enabled
    Navigate to System Console > Plugins > Management, or check /api/v4/plugins/marketplace for the 'playbooks' plugin status
    Affected if Playbooks plugin is installed and enabled
  3. Confirm playbook run linking feature exists
    Access a Playbook > Runs > select a run > check for channel linking option in the run details
    Affected if The channel linking functionality is present and accessible to authenticated users
  4. Audit playbook runs linked to private channels
    Query the database: SELECT id, name, channel_id FROM IR_Incident WHERE channel_id IN (SELECT Id FROM Channels WHERE Type = 'P'); Compare channel membership tables to identify runs linked to channels where the user is not a member
    Affected if Any playbook runs are found linked to private channels where the linking user is not a channel member

The environment is affected if the installed Mattermost Server version falls within the affected ranges AND the Playbooks plugin is enabled, allowing unauthorized linking of runs to private channels.

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 8.1.13 / 9.5.4 / 9.6.2 or later
Fixed in 8.1.139.5.49.6.2
Interim mitigation

Upgrade Mattermost to versions 9.5.4, 9.6.2, 8.1.13 or later to resolve the access control vulnerability.

Recommended fix High confidence

Upgrade to 8.1.13 (for 8.1.x), 9.5.4 (for 9.5.x), or 9.6.2 (for 9.6.x) - choose the appropriate version based on your current branch

  1. 1. Back up your Mattermost Server database and configuration files
  2. 2. Ensure you have a snapshot or backup of your current instance
  3. 3. For Mattermost Server 8.1.x: Upgrade to version 8.1.13 or later
  4. 4. For Mattermost Server 9.5.x: Upgrade to version 9.5.4 or later
  5. 5. For Mattermost Server 9.6.x: Upgrade to version 9.6.2 or later
  6. 6. After upgrade, verify that the access control fix is working by testing that users cannot link playbook runs to private channels they are not members of
  7. 7. Restart the Mattermost services if required after the upgrade
Caveat Review Mattermost release notes for your target version to check for any breaking changes between your current version and the upgrade target

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

Fix this in Mattermost Server 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-2024-32045 — 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-32045 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