Zulip is an open-source team collaboration tool with unique topic-based threading. In the event that 1: ZulipLDAPAuthBackend
and an external authentication backend (any aside of ZulipLDAPAuthBackend
and EmailAuthBackend
) are the only ones enabled in AUTHENTICATION_BACKENDS
in /etc/zulip/settings.py
and 2: The organization permissions dont require invitations to join. An attacker can create a new account in the organization with an arbitrary email address in their control thats not in the organizations LDAP directory. The impact is limited to installations which have this specific combination of authentication backends as described above in addition to having Invitations are required for joining this organization
organization permission disabled. This issue has been addressed in version 6.2. Users are advised to upgrade. Users unable to upgrade may enable the Invitations are required for joining this organization
organization permission to prevent this issue.
The product does not perform or incorrectly performs an authorization check when an actor attempts to access a resource or perform an action.
Name | Vendor | Start Version | End Version |
---|---|---|---|
Zulip | Zulip | * | 6.2 (excluding) |
Assuming a user with a given identity, authorization is the process of determining whether that user can access a given resource, based on the user’s privileges and any permissions or other access-control specifications that apply to the resource. When access control checks are not applied consistently - or not at all - users are able to access data or perform actions that they should not be allowed to perform. This can lead to a wide range of problems, including information exposures, denial of service, and arbitrary code execution.