Slack import bypasses email verification for team access controls
Mattermost
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/mattermost/mattermost/server/v8 Go |
|
|
| github.com/mattermost/mattermost-server Go |
|
Mattermost
| Product | Affected | Fixed in |
|---|---|---|
| github.com/mattermost/mattermost/server/v8 Go |
|
|
| github.com/mattermost/mattermost-server Go |
|
≥ 10.11.0 · < 10.11.3≥ 10.5.0+incompatible · < 10.5.11+incompatible≥ 10.10.0+incompatible · < 10.10.3+incompatible≥ 10.11.0+incompatible · < 10.11.3+incompatible
|
| github.com/mattermost/mattermost-server/v5 Go |
| No fix yet |
| github.com/mattermost/mattermost-server/v6 Go |
| No fix yet |
Mattermost versions 10.10.x <= 10.10.2, 10.5.x <= 10.5.10, 10.11.x <= 10.11.2 fail to validate email ownership during Slack import process which allows attackers to create verified user accounts with arbitrary email domains via malicious Slack import data to bypass email-based team access restrictions
From the CVE record · Mattermost
Affected Mattermost versions fail to validate email ownership during Slack import. An attacker can use malicious Slack import data to create verified accounts with arbitrary email domains, bypassing email-based team access restrictions. The input does not specify whether the attacker needs authentication or another user's interaction.
Teams running Mattermost 10.5.x through 10.5.10, 10.10.x through 10.10.2, or 10.11.x through 10.11.2, or using the listed affected Go packages, should check their deployments.