CVE-2024-2450
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 · uneditedMattermost versions 8.1.x before 8.1.10, 9.2.x before 9.2.6, 9.3.x before 9.3.2, and 9.4.x before 9.4.3 fail to correctly verify account ownership when switching from email to SAML authentication, allowing an authenticated attacker to take over other user accounts via a crafted switch request under specific conditions.
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 confidenceMattermost fails to properly verify account ownership during email-to-SAML authentication switching, allowing an authenticated attacker to craft malicious switch requests that hijack other user accounts. This is a broken access control vulnerability in the authentication flow that requires specific conditions to exploit.
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>= 8.1.0, < 8.1.10>= 9.2.0, < 9.2.6>= 9.3.0, < 9.3.2>= 9.4.0, < 9.4.3= 9.5.0CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/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 checksWork through these to decide whether this CVE applies to you.
-
Determine Mattermost Server versionRun 'mattermost version' or check the System Console under About > Mattermost, or inspect the version file in the Mattermost installation directoryAffected if The installed version falls within any of these ranges: >= 8.1.0 and < 8.1.10; >= 9.2.0 and < 9.2.6; >= 9.3.0 and < 9.3.2; >= 9.4.0 and < 9.4.3; or equals 9.5.0
-
Verify SAML authentication is enabledCheck the Mattermost config.json file for 'Saml' settings under 'PluginSettings', or navigate to Authentication > SAML in the System Console to confirm SAML is configured and enabledAffected if SAML authentication is enabled and configured in the Mattermost instance
-
Confirm email-to-SAML switching is allowedCheck the SAML plugin configuration for settings that allow users to switch from email/password to SAML authentication, or review the 'EnableEmailToSAML' setting in the SAML plugin configurationAffected if The email-to-SAML account switching feature is enabled in the SAML configuration
-
Review authentication logs for account hijacking attemptsSearch the Mattermost logs (typically in /var/log/mattermost or via the System Console logs) for entries containing 'SAML' and 'switch' or 'link' actions, especially targeting accounts other than the authenticated user's own accountAffected if Log entries show SAML authentication switching attempts targeting accounts that do not belong to the requesting user
-
Audit recent account modifications linked to SAMLQuery the database or user admin logs to identify accounts where the SignupMethod was changed to SAML, particularly those changed by a user other than the account ownerAffected if Recent account signup method changes to SAML exist that were initiated by different users than the account owners
A user is affected if their Mattermost Server version is within the affected ranges AND SAML authentication with email-to-SAML switching is enabled, and there is evidence of unauthorized account ownership changes in authentication logs or account records.
Generated from the published advisory. Verify against your own configuration.
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 · scoped8.1.109.2.69.3.2
Upgrade Mattermost to versions 8.1.10, 9.2.6, 9.3.2, 9.4.3 or later. Review SAML configuration and monitor for unauthorized account access attempts.
Upgrade to 8.1.10, 9.2.6, 9.3.2, or 9.4.3 (depending on your current major/minor version)
- 1. Determine your current Mattermost Server version from the system console
- 2. Identify which version range you fall into (8.1.x, 9.2.x, 9.3.x, or 9.4.x)
- 3. Backup your Mattermost database and configuration files before proceeding
- 4. Download the appropriate fixed version: 8.1.10, 9.2.6, 9.3.2, or 9.4.3
- 5. Stop the Mattermost Server service
- 6. Install the fixed version using your deployment method (e.g., apt/yum upgrade, Docker, or manual upgrade)
- 7. Verify the upgrade completed successfully and service restarted
- 8. Test SAML authentication flows to confirm the fix is working
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,648.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-2450 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-2450 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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