dbcve.org
MattermostApplication

CVE-2024-42411

MEDIUM · 5.3 CVSS v3.1 Published 2024-08-22
Fix available
A fix is available. Upgrade to 9.5.8 / 9.8.3 or later.
See remediation →
62/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 versions 9.9.x <= 9.9.1, 9.5.x <= 9.5.7, 9.10.x <= 9.10.0, 9.8.x <= 9.8.2 fail to restrict the input in POST /api/v4/users which allows a user to manipulate the creation date in POST /api/v4/users tricking the admin into believing their account is much older.

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 validate or restrict the creation_date parameter in the POST /api/v4/users endpoint, allowing authenticated users to manipulate their account's creation timestamp. This causes the account to appear older than its actual creation time in admin views.

MitigationUpgrade Mattermost to version 9.9.2, 9.5.8, 9.10.1, or 9.8.3 or later. As a temporary mitigation, monitor API logs for anomalous user creation requests with unexpected creation_date values.

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
MattermostApplication
Affected:>= 9.5.0, < 9.5.8>= 9.8.0, < 9.8.3>= 9.9.0, < 9.9.2>= 9.10.0, < 9.10.1

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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 installed Mattermost version
    Run 'mattermost version' or check the System Console > About page for the exact version number
    Affected if The installed version falls within these ranges: >= 9.5.0 and < 9.5.8, >= 9.8.0 and < 9.8.3, >= 9.9.0 and < 9.9.2, or >= 9.10.0 and < 9.10.1
  2. Verify if user creation API is accessible
    Confirm that authenticated users (non-admin) can access POST /api/v4/users by reviewing API permissions or testing with a test account
    Affected if Non-admin users have permission to call the user creation endpoint
  3. Review API access logs for anomalous creation_date values
    Search server logs for POST requests to /api/v4/users where the request body contains a creation_date field with values significantly different from the request timestamp
    Affected if Logs show user creation requests with manipulated creation_date values that do not match the actual creation time
  4. Check user account ages in admin view
    Compare the actual account creation time (from account activity or audit logs) against the displayed creation timestamp in the admin User list view
    Affected if Displayed creation dates do not match actual account creation times for any users

You are affected if your Mattermost version is 9.5.0-9.5.7, 9.8.0-9.8.2, 9.9.0-9.9.1, or 9.10.0 and non-admin users can access the user creation API.

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.8 / 9.8.3 / 9.9.2 or later
Fixed in 9.5.89.8.39.9.2
Interim mitigation

Upgrade Mattermost to version 9.9.2, 9.5.8, 9.10.1, or 9.8.3 or later. As a temporary mitigation, monitor API logs for anomalous user creation requests with unexpected creation_date values.

Recommended fix High confidence

Upgrade to 9.5.8, 9.8.3, 9.9.2, or 9.10.1 depending on your current branch (minimum fixed version)

  1. Identify the currently running Mattermost version from the affected list (9.5.0-9.5.7, 9.8.0-9.8.2, 9.9.0-9.9.1, or 9.10.0-9.10.0)
  2. Download the appropriate fixed version for your branch: 9.5.8 (for 9.5.x), 9.8.3 (for 9.8.x), 9.9.2 (for 9.9.x), or 9.10.1 (for 9.10.x)
  3. Follow Mattermost upgrade documentation to apply the upgrade
  4. Verify the upgrade was successful and the version matches the expected fixed release
Caveat Standard minor version upgrade; review Mattermost changelog for any configuration or feature changes specific to your version

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

Fix this in Mattermost Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,780
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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