GHSA-85jj-c9jr-9jhx CVE-2023-6202
Mattermost Improper Access Control vulnerability
- Severity
- 4.3 / 10
- Medium · CVSS 3.1
- Exploit chance (EPSS)
- 0.44%
- Chance of exploitation in the next 30 days. Higher than 38.53% of scored vulnerabilities.
- Known exploited
- No
- Not in CISA's catalog
- Weakness
- CWE-284 Improper Access Control
- Fix
- Available
- 2 packages have a fixed version
Description
Mattermost fails to perform proper authorization in the /plugins/focalboard/api/v2/users endpoint allowing an attacker who is a guest user and knows the ID of another user to get their information (e.g. name, surname, nickname) via Mattermost Boards.
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 4.3
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
Weakness
CWE-284: Improper Access Control
The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.
How to prevent it
- Architecture and Design, Operation: Very carefully manage the setting, management, and handling of privileges. Explicitly manage trust zones in the software.
- Architecture and Design: Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area. Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.
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