Lack of Invalidation of Legacy Remote Cluster Invite Tokens After Confirmation
Mattermost
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/mattermost/mattermost Go |
|
|
Mattermost
| Product | Affected | Fixed in |
|---|---|---|
| github.com/mattermost/mattermost Go |
|
|
10.11.511.0.410.11.5+incompatible10.12.2+incompatible11.0.4+incompatible| github.com/mattermost/mattermost/server/v8 Go |
|
|
| github.com/mattermost/mattermost-server Go |
|
|
| github.com/mattermost/mattermost-server/v5 Go |
| No fix yet |
| github.com/mattermost/mattermost-server/v6 Go |
| No fix yet |
Mattermost versions 10.11.x <= 10.11.5, 11.0.x <= 11.0.4, 10.12.x <= 10.12.2 fail to invalidate remote cluster invite tokens when using the legacy (version 1) protocol or when the confirming party does not provide a refreshed token, which allows an attacker who has obtained an invite token to authenticate as the remote cluster and perform limited actions on shared channels even after the invitation has been legitimately confirmed.
From the CVE record · Mattermost
Mattermost may fail to invalidate a remote cluster invite token when the legacy version 1 protocol is used or the confirming party does not provide a refreshed token. An attacker who has obtained the token can authenticate as the remote cluster and perform limited actions on shared channels after the invitation has been confirmed.
Teams running affected Mattermost versions should check the listed Go packages, including mattermost-server/v5 and /v6, for which no fixed version is listed.