MattermostApplication

CVE-2022-0708

MEDIUM · 6.5 CVSS v3.1 Published 2022-02-21
Fix available
A fix is available. Upgrade to after 6.3.0 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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
Mattermost 6.3.0 and earlier fails to protect email addresses of the creator of the team via one of the APIs, which allows authenticated team members to access this information resulting in sensitive & private information disclosure.

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 confidence

Mattermost versions 6.3.0 and earlier expose the email address of a team's creator through an API endpoint without proper authorization checks. Any authenticated team member can query this API and retrieve the team creator's private email address, resulting in sensitive information disclosure.

MitigationUpgrade Mattermost to version 6.3.1 or later, which contains the fix for this authorization bypass. Alternatively, if upgrading is not immediately feasible, review API access controls and consider restricting team membership to trusted users as a compensating control.

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
MattermostApplication
Affected:<= 6.3.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
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 checks

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

  1. Check Mattermost version
    Locate the installed Mattermost version through the system console, About section, or by querying the /api/v4/system/config endpoint with proper authentication. Compare the version number to the affected range: anything at or below 6.3.0 is vulnerable.
    Affected if Installed version is 6.3.0 or earlier
  2. Verify API endpoint accessibility
    Using an authenticated session for a standard team member (non-admin), attempt to query the API endpoint that returns team details. Without authorization checks, this endpoint should return the team creator's email address in the response payload.
    Affected if The API response for team information includes the email field of the team creator to non-admin users
  3. Confirm authorization gap
    Create or use an existing low-privilege team member account. Query the API to retrieve team metadata or member listings. Inspect whether the response contains the private email address of the team creator, which should not be visible to regular members.
    Affected if Standard team members can view the team creator's private email address through any API call

A user is affected if their Mattermost installation is version 6.3.0 or earlier AND any authenticated team member can retrieve the team creator's email address through the API.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 6.3.0
Interim mitigation

Upgrade Mattermost to version 6.3.1 or later, which contains the fix for this authorization bypass. Alternatively, if upgrading is not immediately feasible, review API access controls and consider restricting team membership to trusted users as a compensating control.

Recommended fix Moderate confidence

Any version greater than 6.3.0 (e.g., 6.3.1 or later stable release)

  1. Upgrade Mattermost server to a version higher than 6.3.0
  2. After upgrade, verify that the vulnerability is resolved by testing that API endpoints no longer return team creator email addresses to unauthorized users
  3. Confirm that all Mattermost servers in the environment are upgraded to the fixed version
Caveat Review Mattermost release notes for version 6.3.x for any breaking changes or configuration requirements before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Mattermost Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
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,328.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-0708 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-0708 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