Skip to content

GO-2024-3227 CVE-2024-10214 GHSA-hm57-h27x-599c

Mattermost incorrectly issues two sessions when using desktop SSO in github.com/mattermost/mattermost-server

Low Go
Severity
0.0 / 10
Low · CVSS 4.0
Exploit chance (EPSS)
0.38%
Chance of exploitation in the next 30 days. Higher than 32.37% of scored vulnerabilities.
Known exploited
No
Not in CISA's catalog
Weakness
CWE-303 Incorrect Implementation of Authentication Algorithm
Fix
8.0.0-20240821220019-0d6b1070a26f
Upgrade github.com/mattermost/mattermost/server/v8 to this version or later

Description

Mattermost incorrectly issues two sessions when using desktop SSO in github.com/mattermost/mattermost-server

Affected versions

Go

PackageVulnerableFixed in
github.com/mattermost/mattermost-server
all versions
No fix yet
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
< 8.0.0-20240821220019-0d6b1070a26f
8.0.0-20240821220019-0d6b1070a26f

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/v8 Go → 8.0.0-20240821220019-0d6b1070a26f

go
go get github.com/mattermost/mattermost/server/v8@v8.0.0-20240821220019-0d6b1070a26f && go mod tidy

Severity breakdown

CVSS 4.0 0.0

CVSS:4.0/AV:A/AC:L/AT:N/PR:L/UI:P/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N

Attack vector
Adjacent
Attack complexity
Low
Attack requirements
None
Privileges required
Low
User interaction
Passive
Confidentiality (vulnerable system)
Low
Integrity (vulnerable system)
None
Availability (vulnerable system)
None
Confidentiality (subsequent systems)
None
Integrity (subsequent systems)
None
Availability (subsequent systems)
None

CVSS 3.1 3.5

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

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
Required
Scope
Unchanged
Confidentiality
Low
Integrity
None
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