Skip to content
Fencer Intel
medium 4.3

CVE-2022-1337 json

OOM DoS in Mattermost image proxy

published 4y ago modified 4mo ago also BIT-mattermost-2022-1337 , EUVD-2022-1715 , GHSA-f37q-q7p2-ccfc , GO-2022-0595

cvss
4.3
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.9%
EPSS 0.9% chance of exploitation in 30 days, percentile 60%
public exploits
0
none known

Summary

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.

Patch / fix

  • go github.com/mattermost/mattermost-server/v6 6.4.2
  • bitnami mattermost 5.37.9, 6.2.5, 6.3.5, 6.4.2
  • Mattermost Mattermost 5.37.9, 6.2.5, 6.3.5, 6.4.2

Is CVE-2022-1337 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
last yr.

Exploit prediction

0.92% chance of exploitation in the next 30 days, higher than 60% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.1 4.3 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L
GitHub 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
NVD 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H
NVD 2.0 4.0 AV:N/AC:L/Au:S/C:N/I:N/A:P
OSV 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

Affected packages

ecosystem package affected fixed in
go github.com/mattermost/mattermost-server/v6
<6.4.2
6.4.2
bitnami mattermost
>=5.37.0, <5.37.9
>=6.2.0, <6.2.5
>=6.3.0, <6.3.5
>=6.4.0, <6.4.2
5.37.9
6.2.5
6.3.5
6.4.2
go github.com/mattermost/mattermost-server
all versions
no fix listed
go github.com/mattermost/mattermost-server/v5
all versions
no fix listed

Affected products

  • Mattermost Mattermost

Classification

Weakness
  • CWE-400 Uncontrolled Resource Consumption
  • CWE-770 Allocation of Resources Without Limits or Throttling

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.