Mattermost ServerApplication · Mattermost

CVE-2022-1337

MEDIUM · 6.5 CVSS v3.1 Published 2022-04-13
Fix available
A fix is available. Upgrade to 5.37.9 / 6.2.5 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
The image proxy component in Mattermost version 6.4.1 and earlier allocates memory for multiple copies of a proxied image, which allows an authenticated attacker to crash the server via links to very large image files.

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

The image proxy component in Mattermost versions 6.4.1 and earlier allocates memory for multiple copies of a proxied image in memory, allowing an authenticated attacker to exhaust server memory and cause a denial of service by supplying links to very large image files.

MitigationUpgrade to Mattermost version 6.4.2 or later. As a workaround, consider implementing rate limiting on the image proxy endpoint or restricting image proxy access for untrusted users.

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.37.0, < 5.37.9>= 6.2.0, < 6.2.5>= 6.3.0, < 6.3.5>= 6.4.0, < 6.4.2

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. Check installed Mattermost Server version
    Run `mattermost version` or check the server diagnostics/logs for the version string. Alternatively, inspect the binary or package version on the server.
    Affected if The installed version falls within any of these ranges: 5.37.0 to 5.37.8, 6.2.0 to 6.2.4, 6.3.0 to 6.3.4, or 6.4.0 to 6.4.1.
  2. Verify if image proxy component is enabled
    Inspect the Mattermost configuration file (config.json) for the 'ImageProxy' setting, or check via the system console under 'Environment > Image Proxy'. Look for entries like 'enable' set to true.
    Affected if The image proxy is enabled (enable=true or a similar configuration option is turned on).
  3. Confirm image proxy is exposed to authenticated users
    Review user role permissions and the image proxy endpoint accessibility. Check if untrusted or standard users can access the image proxy functionality.
    Affected if Authenticated users (including non-admin users) have access to the image proxy endpoint without additional restrictions.

You are affected if your Mattermost Server version is in the vulnerable range AND the image proxy component is enabled and accessible to authenticated users.

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.9 / 6.2.5 / 6.3.5 or later
Fixed in 5.37.96.2.56.3.5
Interim mitigation

Upgrade to Mattermost version 6.4.2 or later. As a workaround, consider implementing rate limiting on the image proxy endpoint or restricting image proxy access for untrusted users.

Recommended fix High confidence

5.37.9, 6.2.5, 6.3.5, or 6.4.2 (or latest stable in respective major branch)

  1. Identify your current Mattermost Server version by checking the system console or running 'mattermost version'
  2. Review the upgrade path matrix to determine the appropriate target version based on your current major version
  3. Schedule a maintenance window as upgrades require server downtime
  4. Back up your Mattermost database and configuration files
  5. For version 5.37.x: Upgrade to 5.37.9 or later
  6. For version 6.2.x: Upgrade to 6.2.5 or later
  7. For version 6.3.x: Upgrade to 6.3.5 or later
  8. For version 6.4.x: Upgrade to 6.4.2 or later
Caveat Review Mattermost upgrade notes for your specific version jump as schema changes and configuration updates may require attention

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

Fix this in Mattermost Server Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,440
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,304.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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