{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-31017 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-31017 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-31017 is a low-severity vulnerability in zulip, published on 25 Jun 2022. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2022-31017 and fix it if it is affected.\n\nWhat it is: CVE-2022-31017 is a low-severity vulnerability in zulip, published on 25 Jun 2022. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2022-31017 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-2022-31017/ (Markdown: https://insights.sbomify.com/CVE-2022-31017/index.md)","id":"CVE-2022-31017","markdown":"https://insights.sbomify.com/CVE-2022-31017/index.md","name":"CVE-2022-31017","record":{"aliases":["GHSA-m5j3-jp59-6f3q"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":true,"product_category":"Zulip Server","requires_auth":"high_privilege","summary":"Attackers can view private historical messages in protected streams by observing API events triggered by message edits.","user_interaction":"required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"zulip","vendor":"zulip"}],"cvss":{"score":2,"severity":"low","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-670","name":"Always-Incorrect Control Flow Implementation"},{"id":"CWE-571","name":"Expression is Always True"}],"description":"Zulip is an open-source team collaboration tool. Versions 2.1.0 through and including 5.2 are vulnerable to a logic error. A stream configured as private with protected history, where new subscribers should not be allowed to see messages sent before they were subscribed, when edited causes the server to incorrectly send an API event that includes the edited message to all of the stream’s current subscribers. This API event is ignored by official clients, but can be observed by using a modified client or the browser’s developer tools. This bug will be fixed in Zulip Server 5.3. There are no known workarounds.","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":"Expression Always True vulnerability in Zulip Server","id":"CVE-2022-31017","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2022"},"n_packages":0,"n_references":1,"next":{"headline":"Denial of service binding form from JSON in Play Framework","id":"CVE-2022-31018"},"packages":[],"prev":{"headline":"Argo CD vulnerable to Uncontrolled Memory Consumption","id":"CVE-2022-31016"},"products":["zulip"],"published":"2022-06-25","related":[{"cvss_score":8.6,"headline":"RabbitMQ exposes ports with weak default secrets in Zulip Server","id":"CVE-2021-43799","kev_date_added":null,"published":"2022-01-25"},{"cvss_score":8,"headline":"Crafted link in Zulip message can cause disclosure of credentials","id":"CVE-2022-35962","kev_date_added":null,"published":"2022-08-29"},{"cvss_score":7.5,"headline":"Auth bypass in zulip","id":"CVE-2016-4427","kev_date_added":null,"published":"2022-07-28"},{"cvss_score":6.8,"headline":"Cross-site Scripting (XSS) - Stored in zulip/zulip","id":"CVE-2021-3866","kev_date_added":null,"published":"2022-01-20"},{"cvss_score":6.5,"headline":"Unauthorized user can register an account in specific configurations in Zulip","id":"CVE-2023-28623","kev_date_added":null,"published":"2023-05-19"},{"cvss_score":6.5,"headline":"Ineffective expiration validation for invitation links in Zulip","id":"CVE-2021-43791","kev_date_added":null,"published":"2021-12-02"},{"cvss_score":6.1,"headline":"Zulip: Path Traversal in Import","id":"CVE-2026-26058","kev_date_added":null,"published":"2026-04-03"}],"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-04-23","vendors":["zulip"]},"summary":"Attackers can view private historical messages in protected streams by observing API events triggered by message edits.","url":"https://insights.sbomify.com/CVE-2022-31017/"}