CVE-2016-11068
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 Server before 3.2.0. Attackers could read LDAP fields 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 · moderate confidenceAn LDAP injection vulnerability in Mattermost Server versions before 3.2.0 allows authenticated or unauthenticated attackers to inject LDAP queries and read sensitive LDAP fields from the directory service, resulting in information disclosure.
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.2.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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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.
-
Identify the installed Mattermost Server versionAccess the Mattermost System Console and navigate to About > Mattermost, or check the version using the CLI command: `mattermost version` or `cat /opt/mattermost/version.txt`. Alternatively, check the response headers on the login page or the server logs during startup.Affected if The version number displayed is lower than 3.2.0 (for example, 3.1.x, 3.0.x, 2.x, etc.)
-
Determine if LDAP authentication is configuredAccess the Mattermost System Console and navigate to Authentication > LDAP. Review whether LDAP sign-in is enabled and if LDAP settings are configured with a server address, base DN, and bind credentials.Affected if LDAP authentication is enabled and connected to an external LDAP/Active Directory server
-
Check LDAP attribute binding configurationNavigate to Authentication > LDAP in the System Console and inspect the LDAP Attribute Mapping settings. Look for fields such as ID Attribute, Username Attribute, Email Attribute, and First Name Attribute that map to LDAP directory fields.Affected if LDAP attribute mappings are configured and pointing to LDAP directory fields that could be manipulated through injection
You are affected if your Mattermost Server version is below 3.2.0 AND you have LDAP authentication enabled with configured attribute mappings, as this combination allows the LDAP injection to succeed.
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.
From vendor data3.2.0
Upgrade Mattermost Server to version 3.2.0 or later to patch the LDAP injection vulnerability. Additionally, restrict network access to the LDAP service and implement proper input validation on LDAP query parameters.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-11068 — 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-11068 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