Excessive resource consumption when sending long emoji names in user custom status
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 |
|
≥ 9.3.0+incompatible · < 9.3.1+incompatible
|
| github.com/mattermost/mattermost-server/v5 Go |
| No fix yet |
| github.com/mattermost/mattermost-server/v6 Go |
| No fix yet |
Mattermost fails to properly validate the length of the emoji value in the custom user status, allowing an attacker to send multiple times a very long string as an emoji value causing high resource consumption and possibly crashing the server.
From the CVE record · Mattermost
Mattermost does not properly validate the length of the emoji value in a custom user status. An attacker can repeatedly submit a very long value, causing high resource consumption and possibly crashing the server. The input does not specify authentication or user-interaction requirements.
Teams running Mattermost with the affected Go packages should check server/v8 versions listed as affected, mattermost-server versions from 9.2.0 up to but not including 9.2.5 or from 9.3.0 up to but not including 9.3.1, and all mattermost-server/v5 and /v6 versions.