dbcve.org
Mattermost ServerApplication · Mattermost

CVE-2022-0904

MEDIUM · 6.5 CVSS v3.1 Published 2022-03-10
Fix available
A fix is available. Upgrade to 5.37.8 / 6.1.3 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
A stack overflow bug in the document extractor in Mattermost Server in versions up to and including 6.3.2 allows an attacker to crash the server via submitting a maliciously crafted Apple Pages document.

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

A stack overflow vulnerability exists in the document extractor component of Mattermost Server versions 6.3.2 and below. By submitting a maliciously crafted Apple Pages document, an authenticated or unauthenticated attacker can trigger excessive stack allocation, causing the server to crash and resulting in denial of service.

MitigationUpgrade Mattermost Server to version 6.3.3 or later to obtain the patch. Until then, consider restricting or blocking Apple Pages file uploads through the platform and implementing rate limiting on document processing endpoints.

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:>= 5.0.0, < 5.37.8>= 6.0.0, < 6.1.3>= 6.2.0, < 6.2.3>= 6.3.0, < 6.3.3

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
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/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 checks

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

  1. Identify Mattermost Server installation
    Check for running Mattermost Server processes using 'ps aux | grep mattermost' or check for Mattermost service via 'systemctl status mattermost'
    Affected if Mattermost Server is not running - no action needed
  2. Determine installed Mattermost Server version
    Run 'mattermost version' or check the version file typically found at /opt/mattermost/version.txt, or check the About section in the System Console
    Affected if Version falls within any of these ranges: >= 5.0.0 and < 5.37.8, OR >= 6.0.0 and < 6.1.3, OR >= 6.2.0 and < 6.2.3, OR >= 6.3.0 and < 6.3.3
  3. Verify document extractor plugin or feature status
    Check System Console > Plugins > Document Extractor or review mattermost config.json for 'DocumentExtraction' plugin settings
    Affected if Document extractor plugin is installed and enabled - the vulnerability requires this component to be active
  4. Check Apple Pages file upload allowance
    Inspect System Console > Posts > Message > Allow uploads that match these file types, or review config.json 'FileSettings' > 'AllowedFileTypes' for '.pages' extension
    Affected if Apple Pages (.pages) files are permitted in the allowed file types configuration

A user is affected if Mattermost Server version is within any of the four vulnerable ranges AND the document extractor feature is enabled AND Apple Pages file uploads are allowed.

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 5.37.8 / 6.1.3 / 6.2.3 or later
Fixed in 5.37.86.1.36.2.3
Interim mitigation

Upgrade Mattermost Server to version 6.3.3 or later to obtain the patch. Until then, consider restricting or blocking Apple Pages file uploads through the platform and implementing rate limiting on document processing endpoints.

Recommended fix High confidence

Upgrade to 5.37.8, 6.1.3, 6.2.3, or 6.3.3 (or latest stable in your major version branch). For best results, upgrade to the latest stable 6.3.x release.

  1. Backup your Mattermost Server data and configuration
  2. Stop the Mattermost service
  3. Upgrade Mattermost Server to version 5.37.8 or later (for 5.x), 6.1.3 or later (for 6.0.x), 6.2.3 or later (for 6.2.x), or 6.3.3 or later (for 6.3.x)
  4. Start the Mattermost service
  5. Verify the server is running and the document extractor is functioning correctly
Caveat Review Mattermost release notes for breaking changes between your current version and target version before upgrading.

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

Fix this in Mattermost Server Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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