CVE-2024-45833
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.18.0 fail to disable autocomplete during login while typing the password and visible password is selected, which allows the password to get saved in the dictionary when the user has Swiftkey as the default keyboard, the masking is off and the password contains a special character..
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 Mobile Apps versions 2.18.0 and below fail to disable the autocomplete attribute on the password input field during login. When the visible password option is enabled, masking is turned off, and the user has Swiftkey as their default keyboard, the password gets saved to the Swiftkey dictionary if it contains special characters.
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.19.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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 Mattermost Mobile App versionOpen the app store (Play Store or App Store), search for Mattermost, and view the installed version. On Android, go to Settings > Apps > Mattermost > Version. On iOS, go to Settings > Mattermost to view version.Affected if The installed version is 2.18.0 or below (any version less than 2.19.0)
-
Verify visible password settingIn the Mattermost Mobile App, go to Settings > Security > Visible Password. Check if this option is enabled/toggled on.Affected if The Visible Password option is turned ON (enabled)
-
Check default keyboard selectionOn the mobile device, go to Settings > General > Keyboard > Keyboards (iOS) or Settings > Language & Input > Default Keyboard (Android). Verify if Swiftkey is listed as the default or primary keyboard.Affected if Swiftkey is set as the default or primary keyboard on the device
All three conditions must be true: Mattermost Mobile version below 2.19.0, Visible Password option enabled, and Swiftkey set as the default keyboard - only then is the user affected by this CVE.
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.19.0
Upgrade Mattermost Mobile Apps to a version greater than 2.18.0, which should properly disable autocomplete on password fields. Until upgraded, users should avoid enabling visible password mode or ensure Swiftkey's learning features are disabled.
Mattermost Mobile 2.19.0
- Open the app store on your mobile device (Apple App Store for iOS or Google Play Store for Android)
- Search for 'Mattermost' mobile app
- Update the app to version 2.19.0 or later
- Alternatively, uninstall and reinstall the app to ensure you have the latest version
- After updating, verify the version number in the app settings
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation6.0 h
- Testing8.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,864.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-45833 — 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-45833 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