CVE-2024-3872
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 app versions 2.13.0 and earlier use a regular expression with polynomial complexity to parse certain deeplinks, which allows an unauthenticated remote attacker to freeze or crash the app via a long maliciously crafted link.
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 confidenceThe Mattermost Mobile app versions 2.13.0 and earlier contain a Regular Expression Denial of Service (ReDoS) vulnerability in deeplink parsing. The app uses a regex with polynomial complexity to parse certain deeplinks, which causes catastrophic backtracking when processing a long maliciously crafted link, resulting in app freeze or crash.
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.13.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
- Required
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 checksWork through these to decide whether this CVE applies to you.
-
Check Mattermost Mobile app versionOn iOS: Go to Settings > Mattermost > Version. On Android: Go to Settings > About Mattermost > Version. Alternatively, check the app version from the device's app store listing or installed apps list.Affected if Installed version is 2.13.0 or earlier.
-
Verify deeplink handling is enabledOn iOS: Go to Settings > Mattermost > deep linking and check if it is enabled. On Android: Go to Settings > Apps > Mattermost > Set as default > Opening links and check if Mattermost is configured to open links.Affected if Deeplink handling is enabled in the app settings.
-
Check if the app processes external deeplinksReview if the device has any apps configured to pass deeplinks to Mattermost (e.g., other apps, browsers, or messaging apps with deep linking enabled). Check browser or messaging app settings for any custom URL schemes or link handlers pointing to mattermost:Affected if Mattermost is set as a handler for deeplinks from third-party apps or browsers.
You are affected if the Mattermost Mobile app version is 2.13.0 or earlier AND deeplink handling is enabled on the device, allowing the app to process deeplinks from external sources.
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 · scopedUpgrade Mattermost Mobile app to a version newer than 2.13.0. Until the update is available, users should avoid clicking deeplinks from untrusted sources.
Version after 2.13.0 (any newer version)
- Open the app store on your mobile device (Apple App Store for iOS or Google Play Store for Android)
- Search for "Mattermost" or locate it in your installed apps
- Update the Mattermost Mobile app to the latest available version
- After updating, verify the app version in Settings > About > Version Information
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-3872 — 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-3872 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