CPE Details
Alerte pour un CPE
Stay informed of any changes for a specific CPE.
CPE Name: cpe:2.3:a:zulip:zulip_server:1.9.1:*:*:*:*:*:*:*
Informations
Vendor
zulipProduct
zulip_serverVersion
1.9.1Related CVE
| CVE ID | Published | Description | Score | Severity |
|---|---|---|---|---|
19h30 +00:00 |
Zulip is an open-source team collaboration tool. A vulnerability in version 8.0 is similar to CVE-2023-32677, but applies to multi-use invitations, not single-use invitation links as in the prior CVE. Specifically, it applies when the installation has configured non-admins to be able to invite users and create multi-use invitations, and has also configured only admins to be able to invite users to streams. As in CVE-2023-32677, this does not let users invite new users to arbitrary streams, only to streams that the inviter can already see. Version 8.1 fixes this issue. As a workaround, administrators can limit sending of invitations down to users who also have the permission to add users to streams. | 4.3 |
Medium |
|
21h41 +00:00 |
Zulip is an open-source team collaboration tool. It was discovered by the Zulip development team that active users who had previously been subscribed to a stream incorrectly continued being able to use the Zulip API to access metadata for that stream. As a result, users who had been removed from a stream, but still had an account in the organization, could still view metadata for that stream (including the stream name, description, settings, and an email address used to send emails into the stream via the incoming email integration). This potentially allowed users to see changes to a stream’s metadata after they had lost access to the stream. This vulnerability has been addressed in version 7.5 and all users are advised to upgrade. There are no known workarounds for this issue. | 4.3 |
Medium |
|
20h04 +00:00 |
Zulip is an open-source team collaboration tool with topic-based threading that combines email and chat. Users who used to be subscribed to a private stream and have been removed from it since retain the ability to edit messages/topics, move messages to other streams, and delete messages that they used to have access to, if other relevant organization permissions allow these actions. For example, a user may be able to edit or delete their old messages they posted in such a private stream. An administrator will be able to delete old messages (that they had access to) from the private stream. This issue was fixed in Zulip Server version 7.3. | 6.5 |
Medium |
|
21h48 +00:00 |
An issue was discovered in Zulip Server before 3.4. A bug in the implementation of the all_public_streams API feature resulted in guest users being able to receive message traffic to public streams that should have been only accessible to members of the organization. | 5.3 |
Medium |
|
21h47 +00:00 |
An issue was discovered in Zulip Server before 3.4. A bug in the implementation of the can_forge_sender permission (previously is_api_super_user) resulted in users with this permission being able to send messages appearing as if sent by a system bot, including to other organizations hosted by the same Zulip installation. | 4.3 |
Medium |
|
21h45 +00:00 |
An issue was discovered in Zulip Server before 3.4. A bug in the implementation of replies to messages sent by outgoing webhooks to private streams meant that an outgoing webhook bot could be used to send messages to private streams that the user was not intended to be able to send messages to. | 4.3 |
Medium |
|
02h39 +00:00 |
Zulip Server before 2.1.5 allows reflected XSS via the Dropbox webhook. | 6.1 |
Medium |
|
02h37 +00:00 |
Zulip Server before 2.1.5 allows reverse tabnapping via a topic header link. | 5.4 |
Medium |
|
02h34 +00:00 |
Zulip Server before 2.1.5 has Incorrect Access Control because 0198_preregistrationuser_invited_as adds the administrator role to invitations. | 7.5 |
High |
|
02h28 +00:00 |
Zulip Server 2.x before 2.1.7 allows eval injection if a privileged attacker were able to write directly to the postgres database, and chose to write a crafted custom profile field value. | 8.8 |
High |
|
17h51 +00:00 |
Zulip Server before 2.1.3 allows XSS via the modal_link feature in the Markdown functionality. | 6.1 |
Medium |
|
17h49 +00:00 |
Zulip Server before 2.1.3 allows reverse tabnabbing via the Markdown functionality. | 6.1 |
Medium |
|
17h47 +00:00 |
Zulip Server before 2.1.3 allows XSS via a Markdown link, with resultant account takeover. | 5.4 |
Medium |
|
02h27 +00:00 |
The image thumbnailing handler in Zulip Server versions 1.9.0 to before 2.0.8 allowed an open redirect that was visible to logged-in users. | 6.1 |
Medium |
|
21h45 +00:00 |
In Zulip Server versions from 1.7.0 to before 2.0.7, a bug in the new user signup process meant that users who registered their account using social authentication (e.g., GitHub or Google SSO) in an organization that also allows password authentication could have their personal API key stolen by an unprivileged attacker, allowing nearly full access to the user's account. | 9.8 |
Critical |
|
09h08 +00:00 |
Zulip server before 2.0.5 incompletely validated the MIME types of uploaded files. A user who is logged into the server could upload files of certain types to mount a stored cross-site scripting attack on other logged-in users. On a Zulip server using the default local uploads backend, the attack is only effective against browsers lacking support for Content-Security-Policy such as Internet Explorer 11. On a Zulip server using the S3 uploads backend, the attack is confined to the origin of the configured S3 uploads hostname and cannot reach the Zulip server itself. | 5.4 |
Medium |
|
09h07 +00:00 |
The Markdown parser in Zulip server before 2.0.5 used a regular expression vulnerable to exponential backtracking. A user who is logged into the server could send a crafted message causing the server to spend an effectively arbitrary amount of CPU time and stall the processing of future messages. | 6.5 |
Medium |
2025©
tesweb SA
