{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-41914 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-41914 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-41914 is a low-severity vulnerability in zulip, published on 16 Nov 2022. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-41914 and fix it if it is affected.\n\nWhat it is: CVE-2022-41914 is a low-severity vulnerability in zulip, published on 16 Nov 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2022-41914 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-41914/ (Markdown: https://insights.sbomify.com/CVE-2022-41914/index.md)","id":"CVE-2022-41914","markdown":"https://insights.sbomify.com/CVE-2022-41914/index.md","name":"CVE-2022-41914","record":{"aliases":["GHSA-q5gx-377v-w76f"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":true,"product_category":"Zulip team collaboration","requires_auth":"none","summary":"Attackers can infer SCIM bearer tokens via timing analysis to read and update user accounts in Zulip organizations with SCIM enabled.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"zulip_server","vendor":"zulip"}],"cvss":{"score":3.7,"severity":"low","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-203","name":"Observable Discrepancy"},{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"Zulip is an open-source team collaboration tool. For organizations with System for Cross-domain Identity Management(SCIM) account management enabled, Zulip Server 5.0 through 5.6 checked the SCIM bearer token using a comparator that did not run in constant time. Therefore, it might theoretically be possible for an attacker to infer the value of the token by performing a sophisticated timing analysis on a large number of failing requests. If successful, this would allow the attacker to impersonate the SCIM client for its abilities to read and update user accounts in the Zulip organization. Organizations where SCIM account management has not been enabled are not affected.","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":"Non-constant-time SCIM token comparison in Zulip Server","id":"CVE-2022-41914","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2022"},"n_packages":0,"n_references":2,"next":{"headline":"Netty vulnerable to HTTP Response splitting from assigning header value iterator","id":"CVE-2022-41915"},"packages":[],"prev":{"headline":"Discourse-calendar exposes members of hidden groups","id":"CVE-2022-41913"},"products":["zulip"],"published":"2022-11-16","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-04-23","vendors":["zulip"]},"summary":"Attackers can infer SCIM bearer tokens via timing analysis to read and update user accounts in Zulip organizations with SCIM enabled.","url":"https://insights.sbomify.com/CVE-2022-41914/"}