Skip to content
Fencer Intel
medium 6.5

CVE-2022-2401 json

Team members could access sensitive information of other users via an API call

published 4y ago modified 4mo ago also BIT-mattermost-2022-2401 , EUVD-2022-6283 , GHSA-7ggc-5r84-xf54 , GO-2022-0540

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

Summary

Unrestricted information disclosure of all users in Mattermost version 6.7.0 and earlier allows team members to access some sensitive information by directly accessing the APIs.

Patch / fix

  • go github.com/mattermost/mattermost-server/v6 6.3.9, 6.5.2, 6.6.2, 6.7.1
  • bitnami mattermost 6.3.9, 6.5.2
  • mattermost mattermost_server 6.3.9, 6.5.2

Is CVE-2022-2401 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.83% chance of exploitation in the next 30 days, higher than 57% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

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

Affected packages

ecosystem package affected fixed in
go github.com/mattermost/mattermost-server/v6
<6.3.9
>=6.4.0, <6.5.2
>=6.6.0, <6.6.2
>=6.7.0, <6.7.1
6.3.9
6.5.2
6.6.2
6.7.1
bitnami mattermost
<6.3.9
>=6.4.0, <6.5.2
>=6.6.0, <=6.6.0
>=6.6.1, <=6.6.1
>=6.7.0, <=6.7.0
6.3.9
6.5.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-200 Exposure of Sensitive Information to an Unauthorized Actor

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.