Skip to content
Fencer Vulns
low 2.6

CVE-2024-1949 json

Mattermost race condition

published 2024-02-29 2 y ago modified 2026-09-10 1 mo ago also BIT-mattermost-2024-1949 , EUVD-2024-0484 , GHSA-3g35-v53r-gpxc , GO-2024-2588

cvss
2.6
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 18%
public exploits
0
none known

Summary

A race condition in Mattermost versions 8.1.x before 8.1.9, and 9.4.x before 9.4.2 allows an authenticated attacker to gain unauthorized access to individual posts' contents via carefully timed post creation while another user deletes posts.

Patch / fix

  • go github.com/mattermost/mattermost/server/v8 8.1.9, 9.4.2
  • bitnami mattermost 8.1.9, 9.4.2
  • go github.com/mattermost/mattermost-server 9.4.2+incompatible
  • Mattermost Mattermost 8.1.9, 9.4.2, 9.5

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
2 y ago

Exploit prediction

0.27% chance of exploitation in the next 30 days, higher than 18% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

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

Affected packages

ecosystem package affected fixed in
go github.com/mattermost/mattermost/server/v8
>=9.0.0, <9.4.2
<8.1.9
all versions
9.4.2
8.1.9
bitnami mattermost
>=8.1.0, <8.1.9
>=9.4.0, <9.4.2
8.1.9
9.4.2
go github.com/mattermost/mattermost-server
>=9.0.0+incompatible, <9.4.2+incompatible
9.4.2+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-200 Exposure of Sensitive Information to an Unauthorized Actor
  • CWE-362 Concurrent Execution using Shared Resource with Improper Synchronization

References

Sources

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.