GHSA-3487-3j7c-7gwj CVE-2023-48369
Mattermost Uncontrolled Resource Consumption vulnerability
Medium
Go
- Severity
- 5.3 / 10
- Medium · CVSS 3.1
- Exploit chance (EPSS)
- 0.63%
- Chance of exploitation in the next 30 days. Higher than 50.31% of scored vulnerabilities.
- Known exploited
- No
- Not in CISA's catalog
- Weakness
- CWE-400 Uncontrolled Resource Consumption
- Fix
- Available
- 2 packages have a fixed version
Description
Mattermost fails to limit the log size of server logs allowing an attacker sending specially crafted requests to different endpoints to potentially overflow the log.
Affected versions
Go
| Package | Vulnerable | Fixed in |
|---|---|---|
| github.com/mattermost/mattermost-server/v6 | < 7.8.13 |
7.8.13 |
| github.com/mattermost/mattermost/server/v8 | >= 9.1.0, < 9.1.1 |
9.1.1 |
| github.com/mattermost/mattermost/server/v8 | >= 9.0.0, < 9.0.2 |
9.0.2 |
| github.com/mattermost/mattermost/server/v8 | < 8.1.4 |
8.1.4 |
How to fix
Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.
github.com/mattermost/mattermost-server/v6 Go → 7.8.13
- go
go get github.com/mattermost/mattermost-server/v6@v7.8.13 && go mod tidy
github.com/mattermost/mattermost/server/v8 Go → 9.1.1
- go
go get github.com/mattermost/mattermost/server/v8@v9.1.1 && go mod tidy
Severity breakdown
CVSS 3.1 5.3
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- Low
Weakness
CWE-400: Uncontrolled Resource Consumption
The product does not properly control the allocation and maintenance of a limited resource.
How to prevent it
- Architecture and Design: Design throttling mechanisms into the system architecture. The best protection is to limit the amount of resources that an unauthorized user can cause to be expended. A strong authentication and access control model will help prevent such attacks from occurring in the first place. The login application should be protected against DoS attacks as much as possible. Limiting the database access, perhaps by caching result sets, can help minimize the resources expended. To further limit the potential for a DoS attack, consider tracking the rate of requests received from users and blocking requests that exceed a defined rate threshold.
- Architecture and Design: Mitigation of resource exhaustion attacks requires that the target system either: recognizes the attack and denies that user further access for a given amount of time, or uniformly throttles all requests in order to make it more difficult to consume resources more quickly than they can again be freed. The first of these solutions is an issue in itself though, since it may allow attackers to prevent the use of the system by a particular valid user. If the attacker impersonates the valid user, they may be able to prevent the user from accessing the server in question. The second solution is simply difficult to effectively institute -- and even when properly done, it does not provide a full solution. It simply makes the attack require more resources on the part of the attacker.
- Architecture and Design: Ensure that protocols have specific limits of scale placed on them.
- Implementation: Ensure that all failures in resource allocation place the system into a safe posture.
References
Advisories
Packages
Other links
Timeline
- Published
- Last updated by the source
- Latest EPSS score
Related advisories
| Advisory | Severity | Why it's related |
|---|---|---|
| GHSA-xmfh-3ccg-c9fx Mattermost has an Incorrect Authorization issue | Low | Also affects github.com/mattermost/mattermost-server/v6 |
| GHSA-6hxm-w4hv-vgvw Mattermost doesn't require role-management authorization when setting the scheme_admin flag on group syncable link and patch endpoints | High | Also affects github.com/mattermost/mattermost-server/v6 |
| GHSA-9p44-r552-4wp9 Mattermost doesn't sanitize the Remote Cluster API response on PATCH operations | Medium | Also affects github.com/mattermost/mattermost-server/v6 |
| GHSA-8qq9-cqj8-82w4 Mattermost doesn't sanitize FileInfo.Name received from federated peers during shared channel file sync | High | Also affects github.com/mattermost/mattermost-server/v6 |
| GHSA-m2w9-h2mm-79qr Mattermost doesn't require system-level permission when patching protected default system roles | High | Also affects github.com/mattermost/mattermost-server/v6 |
| GHSA-c28q-m4gf-vg4q Mattermost doesn't enforce PermissionInviteUser when setting AllowOpenInvite or AllowedDomains during team creation | Medium | Also affects github.com/mattermost/mattermost-server/v6 |
| GHSA-3vmp-whvv-5v9v Mattermost doesn't validate that a username returned during bot registration belongs to a bot account | Medium | Also affects github.com/mattermost/mattermost-server/v6 |
| GHSA-rp4v-qc77-phm4 Mattermost doesn't restrict role_updated websocket event broadcasts to members of the affected team or channel | Medium | Also affects github.com/mattermost/mattermost-server/v6 |
MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.
Check your repos with MergeHarbor