Mattermost Server up to 9.6.0 User Preferences resource consumption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.0 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Mattermost Server up to 8.1.10/9.3.2/9.4.3/9.5.1/9.6.0. It has been classified as problematic. This affects an unknown part of the component User Preferences Handler. The manipulation leads to resource consumption. This vulnerability is documented as CVE-2024-28949. The attack can be initiated remotely. There is not any exploit available. Upgrading the affected component is recommended.
Details
A vulnerability, which was classified as problematic, has been found in Mattermost Server up to 8.1.10/9.3.2/9.4.3/9.5.1/9.6.0. This issue affects an unknown code block of the component User Preferences Handler. 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 Server versions 9.5.x before 9.5.2, 9.4.x before 9.4.4, 9.3.x before 9.3.3, 8.1.x before 8.1.11 don't limit the number of user preferences which allows an attacker to send a large number of user preferences potentially causing denial of service.
The weakness was released by Vultza. The advisory is shared at mattermost.com. The identification of this vulnerability is CVE-2024-28949 since 04/03/2024. The exploitation is known to be easy. The attack may be initiated remotely. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1499 for this issue.
Upgrading to version 8.1.11, 9.3.3, 9.4.4, 9.5.2 or 9.6.0 eliminates this vulnerability.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Vendor
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
- 9.0
- 9.1
- 9.2
- 9.3
- 9.3.0
- 9.3.1
- 9.3.2
- 9.4
- 9.4.0
- 9.4.1
- 9.4.2
- 9.4.3
- 9.5
- 9.5.0
- 9.5.1
- 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: Server 8.1.11/9.3.3/9.4.4/9.5.2/9.6.0
Timeline
04/03/2024 🔍04/05/2024 🔍
04/05/2024 🔍
12/13/2024 🔍
Sources
Advisory: mattermost.comResearcher: Vultza
Status: Confirmed
CVE: CVE-2024-28949 (🔍)
GCVE (CVE): GCVE-0-2024-28949
GCVE (VulDB): GCVE-100-259481
Entry
Created: 04/05/2024 10:52Updated: 12/13/2024 06:24
Changes: 04/05/2024 10:52 (64), 05/10/2024 03:02 (1), 12/13/2024 06:24 (14)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.