DoS via custom post type for sysconsole plugin readers
Mattermost
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/mattermost/mattermost/server/v8 Go |
|
|
Mattermost
| Product | Affected | Fixed in |
|---|---|---|
| github.com/mattermost/mattermost/server/v8 Go |
|
|
10.2.18.0.0-20250102081831-64c566a8280b| 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.2.0, 9.11.x <= 9.11.5, 10.0.x <= 10.0.3, 10.1.x <= 10.1.3 fail to properly validate post types, which allows attackers to deny service to users with the sysconsole_read_plugins permission via creating a post with the custom_pl_notification type and specific props.
From the CVE record · Mattermost
Mattermost does not properly validate post types. An attacker who can create a post with the custom_pl_notification type and specific properties can deny service to users with the sysconsole_read_plugins permission. The input does not specify whether authentication or user interaction is required.
Operators of Mattermost and users of the affected Go packages should check the listed affected versions, including all versions of mattermost-server/v5 and /v6.