{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-39268 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-39268 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-39268 is a high-severity vulnerability in orchest, published on 30 Sep 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2022-39268 and fix it if it is affected.\n\nWhat it is: CVE-2022-39268 is a high-severity vulnerability in orchest, published on 30 Sep 2022. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2022-39268 in the wild and no public exploit code.\n\nAffected product: orchest. 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-39268/ (Markdown: https://insights.sbomify.com/CVE-2022-39268/index.md)","id":"CVE-2022-39268","markdown":"https://insights.sbomify.com/CVE-2022-39268/index.md","name":"CVE-2022-39268","record":{"aliases":["GHSA-q44f-8jpw-qv4j"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["account_takeover","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Orchest workflow platform","requires_auth":"none","summary":"Attackers can trick users into performing unintended actions on their Orchest instances, potentially leading to account takeover or data modification.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"orchest","vendor":"orchest"}],"cvss":{"score":8.1,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"description":"### Impact In a CSRF attack, an innocent end user is tricked by an attacker into submitting a web request that they did not intend. This may cause actions to be performed on the website that can include inadvertent client or server data leakage, change of session state, or manipulation of an end user's account. ### Patch Upgrade to v2022.09.10 to patch this vulnerability. ### Workarounds Rebuild and redeploy the Orchest `auth-server` with this commit: https://github.com/orchest/orchest/commit/c2587a963cca742c4a2503bce4cfb4161bf64c2d ### References https://en.wikipedia.org/wiki/Cross-site_request_forgery https://cwe.mitre.org/data/definitions/352.html ### For more information If you have any questions or comments about this advisory: * Open an issue in https://github.com/orchest/orchest * Email us at rick@orchest.io","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":"orchest vulnerable to cross-site request forgery that allows control of a user instance","id":"CVE-2022-39268","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"csrf","year":"2022"},"n_packages":0,"n_references":4,"next":{"headline":"Media transport downgrade from the secure version (SRTP) to non-secure (RTP) in pjsip","id":"CVE-2022-39269"},"packages":[],"prev":{"headline":"Brokercap Bifrost vulnerable to authentication bypass for admin and monitor user groups","id":"CVE-2022-39267"},"products":["orchest"],"published":"2022-09-30","related":[{"cvss_score":9.3,"headline":"Path traversal in n/a","id":"CVE-2022-31503","kev_date_added":null,"published":"2022-07-11"}],"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":"total"},"state":"PUBLISHED","updated":"2025-04-23","vendors":["orchest"]},"summary":"Attackers can trick users into performing unintended actions on their Orchest instances, potentially leading to account takeover or data modification.","url":"https://insights.sbomify.com/CVE-2022-39268/"}