Zulip Content-Type interpretation conflict

Summaryinfo

A vulnerability was found in Zulip. It has been classified as problematic. This affects an unknown part of the component Content-Type Handler. Performing a manipulation results in interpretation conflict. This vulnerability is known as CVE-2023-22735. Remote exploitation of the attack is possible. No exploit is available. This product follows a rolling release approach for continuous delivery, so version details for affected or updated releases are not provided. Applying a patch is the recommended action to fix this issue.

Detailsinfo

A vulnerability classified as problematic has been found in Zulip (unknown version). This affects an unknown code block of the component Content-Type Handler. The manipulation with an unknown input leads to a interpretation conflict vulnerability. CWE is classifying the issue as CWE-436. Product A handles inputs or steps differently than Product B, which causes A to perform incorrect actions based on its perception of B's state. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

Zulip is an open-source team collaboration tool. In versions of zulip prior to commit `2f6c5a8` but after commit `04cf68b` users could upload files with arbitrary `Content-Type` which would be served from the Zulip hostname with `Content-Disposition: inline` and no `Content-Security-Policy` header, allowing them to trick other users into executing arbitrary Javascript in the context of the Zulip application. Among other things, this enables session theft. Only deployments which use the S3 storage (not the local-disk storage) are affected, and only deployments which deployed commit 04cf68b45ebb5c03247a0d6453e35ffc175d55da, which has only been in `main`, not any numbered release. Users affected should upgrade from main again to deploy this fix. Switching from S3 storage to the local-disk storage would nominally mitigate this, but is likely more involved than upgrading to the latest `main` which addresses the issue.

The weakness was published 02/07/2023 as GHSA-wm83-3764-5wqh. The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2023-22735 since 01/06/2023. It demands that the victim is doing some kind of user interaction. Neither technical details nor an exploit are publicly available.

Applying the patch 04cf68b45ebb5c03247a0d6453e35ffc175d55da is able to eliminate this problem. The bugfix is ready for download at github.com.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Name

• Zulip

License

• open-source

Website

• Product: https://github.com/zulip/zulip/

CPE 2.3info

• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion