CVE-2024-39767
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 Mobile Apps versions <=2.16.0 fail to validate that the push notifications received for a server actually came from this serve that which allows a malicious server to send push notifications with another server’s diagnostic ID or server URL and have them show up in mobile apps as that server’s push notifications.
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 · moderate confidenceMattermost Mobile Apps versions 2.16.0 and earlier fail to validate the authenticity of push notification origin, allowing a malicious server to impersonate a legitimate server by sending notifications containing another server's diagnostic ID or server URL. The mobile app displays these spoofed notifications as if they came from the legitimate server.
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< 2.17.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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Check installed Mattermost Mobile versionOn iOS: Open App Store > Tap profile icon > Tap 'Apps' > Find Mattermost and view version. On Android: Open Play Store > Tap profile > Tap 'Manage apps & games' > Find Mattermost and view version.Affected if Installed version is 2.16.0 or earlier (any version below 2.17.0)
-
Verify push notifications are enabledOpen Mattermost Mobile app > Go to Settings (gear icon) > Notifications > Confirm 'Enable Notifications' toggle is turned ON.Affected if Push notifications are enabled - this is required for the vulnerability to be exploitable
-
Check server connection configurationIn Mattermost Mobile, go to Settings > About Mattermost > Server Version to confirm which server the app is connected to.Affected if Connected to any Mattermost server while using a vulnerable app version with notifications enabled
You are affected if the Mattermost Mobile app version is 2.16.0 or earlier AND push notifications are enabled on the device.
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 · scoped2.17.0
Update Mattermost Mobile Apps to a version newer than 2.16.0, which should include proper server validation for push notifications.
Mattermost Mobile App version 2.17.0
- Open the Mattermost Mobile App on your device
- Navigate to your device's app store (Google Play Store for Android or App Store for iOS)
- Search for "Mattermost" in the store
- Locate the Mattermost app and tap "Update" to install version 2.17.0 or later
- Alternatively, for managed devices, use your MDM solution to push the updated app version 2.17.0+ to all enrolled devices
- After updating, verify the app launches successfully and you can receive notifications
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation8.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 $4,480.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-39767 — 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-39767 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