Skip to content

GHSA-9rww-66w7-7vjx CVE-2023-4108

Mattermost fails to sanitize post metadata

High Go
Severity
4.5 / 10
High · CVSS 3.1
Exploit chance (EPSS)
0.60%
Chance of exploitation in the next 30 days. Higher than 48.85% of scored vulnerabilities.
Known exploited
No
Not in CISA's catalog
Weakness
CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
CWE-532 Insertion of Sensitive Information into Log File
Fix
7.8.8
Upgrade github.com/mattermost/mattermost-server/v6 to this version or later

Description

Mattermost fails to sanitize post metadata during audit logging, resulting in permalinks' contents being logged.

Affected versions

Go

PackageVulnerableFixed in
github.com/mattermost/mattermost-server/v6
< 7.8.8
7.8.8
github.com/mattermost/mattermost-server/v6
>= 7.9.0, < 7.9.6
7.9.6
github.com/mattermost/mattermost-server/v6
>= 7.10.0, < 7.10.4
7.10.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.8

go
go get github.com/mattermost/mattermost-server/v6@v7.8.8 && go mod tidy

Severity breakdown

CVSS 3.1 4.5

CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:H/I:N/A:N

Attack vector
Network
Attack complexity
Low
Privileges required
High
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

Weakness

CWE-200: Exposure of Sensitive Information to an Unauthorized Actor

The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.

How to prevent it
  • 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.

CWE-532: Insertion of Sensitive Information into Log File

The product writes sensitive information to a log file.

How to prevent it
  • Architecture and Design, Implementation: Consider seriously the sensitivity of the information written into log files. Do not write secrets into the log files.
  • Distribution: Remove debug log files before deploying the application into production.
  • Operation: Protect log files against unauthorized read/write.
  • Implementation: Adjust configurations appropriately when software is transitioned from a debug state to production.

References

Timeline

  1. Published
  2. Last updated by the source
  3. Latest EPSS score
AdvisorySeverityWhy 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
Is this in your code?

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