Denial of service in mattermost mobile apps and server via emoji reactions
Mattermost
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/mattermost/mattermost/server/v8 Go |
|
|
| github.com/mattermost/mattermost-server |
Mattermost
| Product | Affected | Fixed in |
|---|---|---|
| github.com/mattermost/mattermost/server/v8 Go |
|
|
| github.com/mattermost/mattermost-server |
|
|
| github.com/mattermost/mattermost-server/v5 Go |
| No fix yet |
| github.com/mattermost/mattermost-server/v6 Go |
| No fix yet |
Mattermost fails to check if a custom emoji reaction exists when sending it to a post and to limit the amount of custom emojis allowed to be added in a post, allowing an attacker sending a huge amount of non-existent custom emojis in a post to crash the mobile app of a user seeing the post and to crash the server due to overloading when clients attempt to retrive the aforementioned post.
From the CVE record · Mattermost
Mattermost does not verify that a custom emoji reaction exists or limit how many can be added to a post. An attacker can add a huge number of nonexistent custom emojis, crashing the mobile app when a user sees the post and potentially crashing the server when clients retrieve it. The input does not specify whether authentication is required.
Engineers running affected Mattermost Go packages should check versions of github.com/mattermost/mattermost/server/v8 and github.com/mattermost/mattermost-server, as well as all versions of github.com/mattermost/mattermost-server/v5 and /v6.