CVE-2016-11064
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 · uneditedAn issue was discovered in Mattermost Desktop App before 3.4.0. Strings could be executed as code via injection.
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 confidenceCode injection vulnerability in Mattermost Desktop App before version 3.4.0 allowed arbitrary strings to be executed as code, likely through improper use of dynamic code execution functions like eval(). This is a critical severity issue enabling remote code execution.
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< 3.4.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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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.
-
Identify Mattermost Desktop App installationLocate the Mattermost Desktop application on the system. On Windows, check Program Files or the user's AppData folder. On macOS, check the Applications folder. On Linux, check standard installation directories or use package management tools.Affected if Mattermost Desktop App is installed on the system
-
Determine installed version numberOpen the Mattermost Desktop App and navigate to the About section (typically found under the application menu or Help > About). Alternatively, right-click the executable file and select Properties to view version information.Affected if The displayed version number is lower than 3.4.0 (e.g., 3.3.x, 3.2.x, earlier versions)
-
Verify code injection exposureThis vulnerability stems from improper use of dynamic code execution functions like eval() within the application. The vulnerability is present in all versions prior to 3.4.0 regardless of configuration settings.Affected if The installed version is below 3.4.0, meaning the application contains the vulnerable code execution logic
The system is affected if Mattermost Desktop App version is installed and the version is lower than 3.4.0.
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 · scoped3.4.0
Upgrade Mattermost Desktop App to version 3.4.0 or later to remediate the code injection vulnerability.
Mattermost Desktop 3.4.0
- 1. Back up your current Mattermost Desktop application data and configuration
- 2. Download Mattermost Desktop version 3.4.0 or later from the official Mattermost website (https://mattermost.com/download/)
- 3. Uninstall the current version of Mattermost Desktop from your system
- 4. Install the downloaded version 3.4.0 or later
- 5. Restart the application and verify it launches successfully
- 6. Reconnect to your Mattermost server and confirm functionality
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.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 $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-11064 — 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-2016-11064 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