Mattermost up to 8.1.11/9.4.4/9.5.2/9.6.0 API getSessions resource consumption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.0 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as problematic, has been found in Mattermost up to 8.1.11/9.4.4/9.5.2/9.6.0. Affected by this issue is the function getSessions of the component API. The manipulation leads to resource consumption.
This vulnerability is traded as CVE-2024-4183. It is possible to initiate the attack remotely. There is no exploit available.
It is advisable to upgrade the affected component.
Details
A vulnerability, which was classified as problematic, has been found in Mattermost up to 8.1.11/9.4.4/9.5.2/9.6.0. This issue affects the function getSessions of the component API. The manipulation with an unknown input leads to a resource consumption vulnerability. Using CWE to declare the problem leads to CWE-400. The product does not properly control the allocation and maintenance of a limited resource, thereby enabling an actor to influence the amount of resources consumed, eventually leading to the exhaustion of available resources. Impacted is availability. The summary by CVE is:
Mattermost versions 8.1.x before 8.1.12, 9.6.x before 9.6.1, 9.5.x before 9.5.3, 9.4.x before 9.4.5 fail to limit the number of active sessions, which allows an authenticated attacker to crash the server via repeated requests to the getSessions API after flooding the sessions table.
The weakness was shared by Vultza. The advisory is shared at mattermost.com. The identification of this vulnerability is CVE-2024-4183 since 04/25/2024. The exploitation is known to be easy. The attack may be initiated remotely. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1499 for this issue.
Upgrading to version 8.1.12, 9.4.5, 9.5.3 or 9.6.1 eliminates this vulnerability.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2024-1321). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Type
Name
Version
- 8.1.0
- 8.1.1
- 8.1.2
- 8.1.3
- 8.1.4
- 8.1.5
- 8.1.6
- 8.1.7
- 8.1.8
- 8.1.9
- 8.1.10
- 8.1.11
- 9.0
- 9.1
- 9.2
- 9.3
- 9.4
- 9.4.0
- 9.4.1
- 9.4.2
- 9.4.3
- 9.4.4
- 9.5
- 9.5.0
- 9.5.1
- 9.5.2
- 9.6.0
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.0VulDB Meta Temp Score: 5.0
VulDB Base Score: 4.3
VulDB Temp Score: 4.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 6.5
NVD Vector: 🔍
CNA Base Score: 4.3
CNA Vector (Mattermost, Inc.): 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: Resource consumptionCWE: CWE-400 / CWE-404
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Mattermost 8.1.12/9.4.5/9.5.3/9.6.1
Timeline
04/25/2024 🔍04/26/2024 🔍
04/26/2024 🔍
05/13/2025 🔍
Sources
Advisory: mattermost.comResearcher: Vultza
Status: Confirmed
CVE: CVE-2024-4183 (🔍)
GCVE (CVE): GCVE-0-2024-4183
GCVE (VulDB): GCVE-100-262109
EUVD: 🔍
Entry
Created: 04/26/2024 10:50Updated: 05/13/2025 03:00
Changes: 04/26/2024 10:50 (64), 05/30/2024 08:56 (1), 05/12/2025 15:53 (14), 05/13/2025 03:00 (1)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.