Skip to content

GO-2025-3729 CVE-2025-2571 GHSA-8cgx-9ccj-3gwr

Mattermost fails to clear Google OAuth credentials in github.com/mattermost/mattermost-server

Medium Go
Severity
4.2 / 10
Medium · CVSS 3.1
Exploit chance (EPSS)
0.21%
Chance of exploitation in the next 30 days. Higher than 11.74% of scored vulnerabilities.
Known exploited
No
Not in CISA's catalog
Weakness
CWE-303 Incorrect Implementation of Authentication Algorithm
Fix
Available
2 packages have a fixed version

Description

Mattermost fails to clear Google OAuth credentials in github.com/mattermost/mattermost-server

Affected versions

Go

PackageVulnerableFixed in
github.com/mattermost/mattermost-server
>= 9.0.0-rc1+incompatible, < 9.11.13+incompatible
>= 10.0.0-rc1+incompatible, < 10.5.4+incompatible
>= 10.6.0-rc1+incompatible, < 10.6.3+incompatible
>= 10.7.0-rc1+incompatible, < 10.7.1+incompatible
9.11.13+incompatible
10.5.4+incompatible
10.6.3+incompatible
10.7.1+incompatible
github.com/mattermost/mattermost-server/v5
all versions
No fix yet
github.com/mattermost/mattermost-server/v6
all versions
No fix yet
github.com/mattermost/mattermost/server/v8
>= 10.7.0-rc1, < 10.7.1
10.7.1
github.com/mattermost/mattermost/server/v8
>= 10.0.0-rc1, < 10.5.4
10.5.4
github.com/mattermost/mattermost/server/v8
>= 9.0.0-rc1, < 9.11.13
9.11.13
github.com/mattermost/mattermost/server/v8
< 8.0.0-20250414095146-04676582cdd2
8.0.0-20250414095146-04676582cdd2
github.com/mattermost/mattermost/server/v8
>= 10.6.0-rc1, < 10.6.3
10.6.3

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 Go → 10.7.1+incompatible

go
go get github.com/mattermost/mattermost-server@v10.7.1+incompatible && go mod tidy

github.com/mattermost/mattermost/server/v8 Go → 10.7.1

go
go get github.com/mattermost/mattermost/server/v8@v10.7.1 && go mod tidy

Severity breakdown

CVSS 3.1 4.2

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

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

Weakness

CWE-303: Incorrect Implementation of Authentication Algorithm

The requirements for the product dictate the use of an established authentication algorithm, but the implementation of the algorithm is incorrect.

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
GHSA-h998-hxxj-8q83
Mattermost doesn't invalidate cached authentication state for active WebSocket connections during global session revocation
Medium Also affects github.com/mattermost/mattermost-server
GHSA-g5vr-6pgg-74qv
Mattermost doesn't enforce bot-specific permission checks on the user active status endpoint
Low Also affects github.com/mattermost/mattermost-server
GHSA-jqgv-39mg-7c2r
Mattermost doesn't authenticate Atlassian Connect installed callbacks, allowing a remote unauthenticated attacker to inject a rogue sharedSecret
Medium Also affects github.com/mattermost/mattermost-server
GHSA-mxq2-5jpg-7474
Mattermost doesn't validate channel ownership of an existing subscription before applying edits
Medium Also affects github.com/mattermost/mattermost-server
GHSA-2g8v-grq3-hq2g
Mattermost doesn't enforce administrator authorization on the {{setDefaultInstance}} call within the {{/gitlab connect}} command handler
Medium Also affects github.com/mattermost/mattermost-server
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
GHSA-9p44-r552-4wp9
Mattermost doesn't sanitize the Remote Cluster API response on PATCH operations
Medium Also affects github.com/mattermost/mattermost-server
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