CVE-2024-29221: Invite ID available to team admins even without the "Add Members" permission

Published Apr 5, 2024
·
Updated

Improper Access Control in Mattermost Server versions 9.5.x before 9.5.2, 9.4.x before 9.4.4, 9.3.x before 9.3.3, 8.1.x before 8.1.11 lacked proper access control in the /api/v4/users/me/teams endpoint allowing a team admin to get the invite ID of their team, thus allowing them to invite users, even if the "Add Members" permission was explicitly removed from team admins.

Affected Software

8 affected componentsFixes available
go/github.com/mattermost/mattermost/server/v8>=9.3.0<9.3.3
9.3.3
go/github.com/mattermost/mattermost/server/v8>=9.4.0<9.4.4
9.4.4
go/github.com/mattermost/mattermost/server/v8>=9.5.0<9.5.2
9.5.2
go/github.com/mattermost/mattermost/server/v8>=8.1.0<8.1.11
8.1.11
Mattermost Mattermost Server>=8.1.0<8.1.11
Mattermost Mattermost Server>=9.3.0<9.3.3
Mattermost Mattermost Server>=9.4.0<9.4.4
Mattermost Mattermost Server>=9.5.0<9.5.2

Remediation

Information

Update Mattermost Server to versions 9.6.0, 9.5.2, 9.4.4, 9.3.3, 8.1.11 or higher.

Event History

Apr 5, 2024
CVE Published
via MITRE·08:15 AM
Data Sourced
via MITRE·08:15 AM
RemedyDescriptionSeverityWeakness
Advisory Published
via GitHub·09:30 AM

Frequently Asked Questions

1

What is the severity of CVE-2024-29221?

CVE-2024-29221 has been classified as a high severity vulnerability due to improper access control allowing unauthorized access to sensitive team information.

2

How do I fix CVE-2024-29221?

To mitigate CVE-2024-29221, upgrade Mattermost Server to versions 9.5.2, 9.4.4, 9.3.3, or 8.1.11 or later.

3

What versions of Mattermost are affected by CVE-2024-29221?

CVE-2024-29221 affects Mattermost Server versions 9.5.x prior to 9.5.2, 9.4.x prior to 9.4.4, 9.3.x prior to 9.3.3, and 8.1.x prior to 8.1.11.

4

What specific access control issue does CVE-2024-29221 involve?

CVE-2024-29221 involves improper access control at the '/api/v4/users/me/teams' endpoint, enabling a team admin to retrieve invite IDs that should be restricted.

5

Is there any workaround for CVE-2024-29221 if I cannot upgrade immediately?

There is no specific workaround for CVE-2024-29221, so upgrading to a fixed version is essential to ensure security.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203