{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-23643 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-23643 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-23643 is a medium-severity vulnerability in sourcegraph, published on 15 Feb 2022. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-23643 and fix it if it is affected.\n\nWhat it is: CVE-2022-23643 is a medium-severity vulnerability in sourcegraph, published on 15 Feb 2022. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2022-23643 in the wild and no public exploit code.\n\nAffected product: sourcegraph. 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-23643/ (Markdown: https://insights.sbomify.com/CVE-2022-23643/index.md)","id":"CVE-2022-23643","markdown":"https://insights.sbomify.com/CVE-2022-23643/index.md","name":"CVE-2022-23643","record":{"aliases":[],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Sourcegraph code search","requires_auth":"low_privilege","summary":"Authenticated attackers can guess private source code strings, such as API keys, via a side-channel attack in the Code Monitoring feature.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"sourcegraph","vendor":"sourcegraph"}],"cvss":{"score":6.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/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":"Sourcegraph is a code search and navigation engine. Sourcegraph versions 3.35 and 3.36 reintroduced a previously fixed side-channel vulnerabilitity in the Code Monitoring feature where strings in private source code could be guessed by an authenticated but unauthorized actor. This issue affects only the Code Monitoring feature, whereas CVE-2021-43823 also affected saved searches. A successful attack would require an authenticated bad actor to create many Code Monitors to receive confirmation that a specific string exists. This could allow an attacker to guess formatted tokens in source code, such as API keys. This issue was patched in versions 3.35.2 and 3.36.3 of Sourcegraph. Those who are unable to upgrade may disable the Code Monitor feature in their installation.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Side-channel attack in Sourcegraph Code Monitors","id":"CVE-2022-23643","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":"Server-side request forgery in BookWyrm","id":"CVE-2022-23644"},"packages":[],"prev":{"headline":"Code Injection in Sourcegraph","id":"CVE-2022-23642"},"products":["sourcegraph"],"published":"2022-02-15","related":[{"cvss_score":9,"headline":"Incorrect default permissions found in Sourcegraph","id":"CVE-2022-41943","kev_date_added":null,"published":"2022-11-22"},{"cvss_score":8.8,"headline":"Code Injection in Sourcegraph","id":"CVE-2022-23642","kev_date_added":null,"published":"2022-02-18"},{"cvss_score":7.9,"headline":"Sourcegraph vulnerable to Comand Injection via gitserver","id":"CVE-2022-41942","kev_date_added":null,"published":"2022-11-22"},{"cvss_score":6.6,"headline":"Remote Code Execution in sourcegraph","id":"CVE-2022-29171","kev_date_added":null,"published":"2022-05-05"},{"cvss_score":6.5,"headline":"Side-channel attack in Sourcegraph","id":"CVE-2021-43823","kev_date_added":null,"published":"2021-12-13"},{"cvss_score":6.4,"headline":"Indirect Object Access in Sourcegraph Code Monitoring","id":"CVE-2022-31154","kev_date_added":null,"published":"2022-08-01"}],"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":["sourcegraph"]},"summary":"Authenticated attackers can guess private source code strings, such as API keys, via a side-channel attack in the Code Monitoring feature.","url":"https://insights.sbomify.com/CVE-2022-23643/"}