{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-22735 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-22735 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-22735 is a medium-severity cross-site scripting vulnerability in zulip, published on 7 Feb 2023. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2023-22735 and fix it if it is affected.\n\nWhat it is: CVE-2023-22735 is a medium-severity cross-site scripting vulnerability in zulip, published on 7 Feb 2023. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2023-22735 in the wild and no public exploit code.\n\nAffected product: zulip. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2023-22735/ (Markdown: https://insights.sbomify.com/CVE-2023-22735/index.md)","id":"CVE-2023-22735","markdown":"https://insights.sbomify.com/CVE-2023-22735/index.md","name":"CVE-2023-22735","record":{"aliases":["GHSA-wm83-3764-5wqh"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution","account_takeover"],"network_reachable":"yes","non_default_config":true,"product_category":"Zulip team collaboration","requires_auth":"low_privilege","summary":"Attackers can execute arbitrary JavaScript in the context of Zulip by uploading files with malicious content types, enabling session theft.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"zulip_server","vendor":"zulip"}],"cvss":{"score":4.4,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-436","name":"Interpretation Conflict"}],"description":"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Cross-site scripting in zulip","id":"CVE-2023-22735","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2023"},"n_packages":0,"n_references":4,"next":{"headline":"argo-cd Controller reconciles apps outside configured namespaces when sharding is enabled","id":"CVE-2023-22736"},"packages":[],"prev":{"headline":"Improper Input Newsletter subscription option validation in shopware","id":"CVE-2023-22734"},"products":["zulip"],"published":"2023-02-07","related":[{"cvss_score":9.8,"headline":"Information disclosure in n/a","id":"CVE-2019-18933","kev_date_added":null,"published":"2019-11-21"},{"cvss_score":8.8,"headline":"Code injection in n/a","id":"CVE-2020-15070","kev_date_added":null,"published":"2020-08-21"},{"cvss_score":8.8,"headline":"Missing authorization in Zulip Server","id":"CVE-2017-0910","kev_date_added":null,"published":"2017-11-27"},{"cvss_score":8.2,"headline":"Zulip Authentication Backend Configuration Bypass","id":"CVE-2025-31478","kev_date_added":null,"published":"2025-04-16"},{"cvss_score":8.2,"headline":"Cross-site scripting vulnerability in Zulip Server development branch via topic tooltip","id":"CVE-2023-33186","kev_date_added":null,"published":"2023-05-30"},{"cvss_score":7.5,"headline":"Denial of service in n/a","id":"CVE-2024-36612","kev_date_added":null,"published":"2024-11-29"},{"cvss_score":7.5,"headline":"Privilege escalation in n/a","id":"CVE-2020-14215","kev_date_added":null,"published":"2020-08-21"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-03-10","vendors":["zulip"]},"summary":"Attackers can execute arbitrary JavaScript in the context of Zulip by uploading files with malicious content types, enabling session theft.","url":"https://insights.sbomify.com/CVE-2023-22735/"}