CVE-2024-42497 json
Insufficient permissions checks on teams
published 2024-08-22 2 y ago modified 2026-06-17 4 mo ago also BIT-mattermost-2024-42497 , EUVD-2024-2580 , GHSA-fxq9-6946-34q7 , GO-2024-3091
- cvss
- 6.0
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 27%
- public exploits
- 0
- none known
Summary
Mattermost versions 9.9.x <= 9.9.1, 9.5.x <= 9.5.7, 9.10.x <= 9.10.0, 9.8.x <= 9.8.2 fail to properly enforce permissions which allows a user with systems manager role with read-only access to teams to perform write operations on teams.
Patch / fix
- go github.com/mattermost/mattermost/server/v8 9.5.8, 9.8.3, 9.9.2, 9.10.1
- bitnami mattermost 9.5.8, 9.8.3, 9.9.2
- go github.com/mattermost/mattermost-server 9.5.8+incompatible, 9.8.3+incompatible, 9.9.2+incompatible, 9.10.1+incompatible
- Mattermost Mattermost 9.5.8, 9.8.3, 9.9.2, 9.10.1, 9.11.0
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2024-42497 updated cvss 4.9
mattermost: permission enforcing failure allows a user with systems manager role with read-only access to teams to perform write operations on teams
-
Red Hat Advanced Cluster Management for Kubernetes 2 rhacm2/acm-grafana-rhel8 Red Hat Advanced Cluster Security 4 advanced-cluster-security/rhacs-main-rhel8, advanced-cluster-security/rhacs-roxctl-rhel8, advanced-cluster-security/rhacs-rhel8-operator, advanced-cluster-security/rhacs-central-db-rhel8, advanced-cluster-security/rhacs-scanner-v4-rhel8, advanced-cluster-security/rhacs-scanner-v4-db-rhel8 Red Hat Ceph Storage 5 rhceph/rhceph-5-dashboard-rhel8 Red Hat Ceph Storage 6 rhceph/rhceph-6-dashboard-rhel9 Red Hat Ceph Storage 7 rhceph/grafana-rhel9 Red Hat OpenShift GitOps openshift-gitops-1/dex-rhel8affected: no fix available “Fix deferred”
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- 2 y ago
Exploit prediction
0.34% chance of exploitation in the next 30 days, higher than 27% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 6.0 | CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:L/A:L |
| GitHub | 3.1 | 6.0 | CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:L/A:L |
| NVD | 3.1 | 4.9 | CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:N |
| OSV | 3.1 | 4.9 | CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| go | github.com/mattermost/mattermost/server/v8 | >=9.5.0, <9.5.8 >=9.10.0, <9.10.1 >=9.9.0, <9.9.2 >=9.8.0, <9.8.3 all versions |
9.5.8 9.10.1 9.9.2 9.8.3 |
| bitnami | mattermost | >=9.5.0, <9.5.8 >=9.8.0, <9.8.3 >=9.9.0, <9.9.2 >=9.10.0, <=9.10.0 |
9.5.8 9.8.3 9.9.2 |
| go | github.com/mattermost/mattermost-server | >=9.5.0+incompatible, <9.5.8+incompatible >=9.8.0+incompatible, <9.8.3+incompatible >=9.9.0+incompatible, <9.9.2+incompatible >=9.10.0+incompatible, <9.10.1+incompatible |
9.5.8+incompatible 9.8.3+incompatible 9.9.2+incompatible 9.10.1+incompatible |
| go | github.com/mattermost/mattermost-server/v5 | all versions |
no fix listed |
| go | github.com/mattermost/mattermost-server/v6 | all versions |
no fix listed |
Affected products
- Mattermost Mattermost
Classification
- Weakness
-
- CWE-284 Improper Access Control
References
-
mattermost.com
/security-updates
web, vendor-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2024-42497
advisory, web
-
github.com
/mattermost/mattermost
package
-
github.com
/advisories/GHSA-fxq9-6946-34q7
advisory
Sources
- CVE List CVE-2024-42497
- GitHub Advisory GHSA-fxq9-6946-34q7
- NVD CVE-2024-42497
- OSV BIT-mattermost-2024-42497
- OSV GO-2024-3091
Fencer Vulns 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.