Insecure string comparison enables timing attacks
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+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.5.x <= 10.5.10, 10.11.x <= 10.11.2 fail to use constant-time comparison for sensitive string comparisons which allows attackers to exploit timing oracles to perform byte-by-byte brute force attacks via response time analysis on Cloud API keys and OAuth client secrets
From the CVE record · Mattermost
Affected Mattermost versions do not use constant-time comparison for sensitive strings. Attackers can analyze response times to perform byte-by-byte brute-force attacks against Cloud API keys and OAuth client secrets. The input does not specify whether authentication or user interaction is required.
Operators of Mattermost 10.5.x through 10.5.10 or 10.11.x through 10.11.2, and users of the listed affected Go packages, should check their versions.