dbcve.org
Mattermost ServerApplication · Mattermost

CVE-2016-11067

MEDIUM · 5.3 CVSS v3.1 Published 2020-06-19
Fix available
A fix is available. Upgrade to 3.2.0 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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 · unedited
An issue was discovered in Mattermost Server before 3.2.0. It allowed crafted posts that could cause a web browser to hang.

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 confidence

Mattermost Server before version 3.2.0 contained a vulnerability where specially crafted posts could be submitted that would cause a connected web browser to hang or become unresponsive. This appears to be a client-side denial-of-service issue caused by improper handling or rendering of certain post content.

MitigationUpgrade Mattermost Server to version 3.2.0 or later to patch the vulnerability. As a temporary workaround, limit or moderate user posting capabilities until the upgrade can be performed.

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
Mattermost ServerApplication
Affected:< 3.2.0

CVSS 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
None
Integrity
None
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

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 checks

Work through these to decide whether this CVE applies to you.

  1. Determine installed Mattermost Server version
    Log into the Mattermost server and run 'grep -i version /path/to/mattermost/config/config.json' or check the system information page in the Mattermost admin console (typically at /admin_console>system>about)
    Affected if The version shown is earlier than 3.2.0 (e.g., 3.1.x, 3.0.x, 2.x, etc.)
  2. Check Mattermost service status
    Verify the Mattermost service is running by running 'systemctl status mattermost' or 'service mattermost status' depending on your init system
    Affected if The service is running and the version cannot be determined or is confirmed to be below 3.2.0
  3. Confirm web interface is accessible
    Access the Mattermost login page via a web browser at your server's URL to confirm the web client is available
    Affected if The web interface loads and the server version is below 3.2.0

You are affected if your running Mattermost Server version is any release earlier than 3.2.0, as the vulnerability exists in those versions and can be triggered by malicious post content processed by the server.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

From vendor data
Upgrade available Upgrade to 3.2.0 or later
Fixed in 3.2.0
Interim mitigation

Upgrade Mattermost Server to version 3.2.0 or later to patch the vulnerability. As a temporary workaround, limit or moderate user posting capabilities until the upgrade can be performed.

Fix this in Mattermost Server Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2016-11067 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2016-11067 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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