dbcve.org
Mattermost ServerApplication · Mattermost

CVE-2024-54083

MEDIUM · 6.5 CVSS v3.1 Published 2024-12-16
Fix available
A fix is available. Upgrade to 9.5.13 / 9.11.5 or later.
See remediation →
71/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 10.1.x <= 10.1.2, 10.0.x <= 10.0.2, 9.11.x <= 9.11.4, 9.5.x <= 9.5.12 fail to properly validate the type of callProps which allows a user to cause a client side (webapp and mobile) DoS to users of particular channels, by sending a specially crafted post.

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 properly validate the type of callProps in posts, allowing authenticated users to send specially crafted posts that cause a client-side denial of service (crash) for users viewing those channels in both the webapp and mobile clients.

MitigationUpgrade Mattermost to versions 10.1.3+, 10.0.3+, 9.11.5+, or 9.5.13+ to receive the patch for proper callProps type validation.

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:>= 9.5.0, < 9.5.13>= 9.11.0, < 9.11.5>= 10.0.0, < 10.0.3>= 10.1.0, < 10.1.3

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
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/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. Check Mattermost Server version
    Run 'sudo mattermost version' or look in the system console under About > Mattermost to find the exact Server version number
    Affected if The installed version falls within any of these ranges: 9.5.0-9.5.12, 9.11.0-9.11.4, 10.0.0-10.0.2, or 10.1.0-10.1.2
  2. Verify call handling feature is enabled
    Navigate to System Console > Product > Calls, or check the config.json file for 'PluginSettings > Plugins > com.mattermost.calls' configuration section
    Affected if The Calls plugin is enabled and users can post calls-related content in channels
  3. Confirm user authentication is possible
    Verify that authenticated users can create or edit posts in channels (standard user permissions)
    Affected if Regular authenticated users have posting permissions in any channel

If the installed Mattermost Server version is within any of the affected ranges AND the Calls feature is enabled, users in the environment are potentially vulnerable to this issue.

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 9.5.13 / 9.11.5 / 10.0.3 or later
Fixed in 9.5.139.11.510.0.3
Interim mitigation

Upgrade Mattermost to versions 10.1.3+, 10.0.3+, 9.11.5+, or 9.5.13+ to receive the patch for proper callProps type validation.

Recommended fix High confidence

9.5.13, 9.11.5, 10.0.3, or 10.1.3 (depending on your current major version branch)

  1. 1. Identify the currently installed Mattermost Server version by checking the system console or running 'mmctl version'
  2. 2. Based on the current version, upgrade to the fixed release: for 9.5.x upgrade to 9.5.13, for 9.11.x upgrade to 9.11.5, for 10.0.x upgrade to 10.0.3, or for 10.1.x upgrade to 10.1.3
  3. 3. Follow Mattermost upgrade documentation to backup the database and config file before upgrading
  4. 4. Install the appropriate patched version using the standard upgrade process for your deployment method (docker, tar archive, or mattermost RPM/DEB package)
  5. 5. Verify the upgrade was successful by checking the server version in the system console
  6. 6. Test that posts with callProps render correctly to confirm the vulnerability is remediated
Caveat Standard Mattermost patch upgrades typically maintain backward compatibility; review release notes for any noted breaking changes in the specific minor version

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-54083 — 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-54083 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