{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-17633 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-17633 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-17633 is a high-severity vulnerability in The Eclipse Foundation Eclipse Che, published on 19 Dec 2019. 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-2019-17633 and fix it if it is affected.\n\nWhat it is: CVE-2019-17633 is a high-severity vulnerability in The Eclipse Foundation Eclipse Che, published on 19 Dec 2019. 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-2019-17633 in the wild and no public exploit code.\n\nAffected product: The Eclipse Foundation Eclipse Che. 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-2019-17633/ (Markdown: https://insights.sbomify.com/CVE-2019-17633/index.md)","id":"CVE-2019-17633","markdown":"https://insights.sbomify.com/CVE-2019-17633/index.md","name":"CVE-2019-17633","record":{"aliases":["GHSA-gf9v-jrhv-643g"],"analysis":{"component_type":"developer_tool","fix_type":"configuration_change","impacts":["code_execution"],"network_reachable":"yes","non_default_config":true,"product_category":"Eclipse Che IDE","requires_auth":"none","summary":"Attackers can trigger arbitrary workspace starts via CSRF if authentication and TLS are disabled, affecting local Eclipse Che installations.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"eclipse","cpe":[{"product":"che","vendor":"eclipse"}],"cvss":{"score":8.8,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"description":"For Eclipse Che versions 6.16 to 7.3.0, with both authentication and TLS disabled, visiting a malicious web site could trigger the start of an arbitrary Che workspace. Che with no authentication and no TLS is not usually deployed on a public network but is often used for local installations (e.g. on personal laptops). In that case, even if the Che API is not exposed externally, some javascript running in the local browser is able to send requests to it.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2019-12-19","github_poc":1,"max_poc_stars":10,"metasploit":0,"nuclei":0,"refs":[{"date":"2019-12-19T20:22:12Z","kind":"github_poc","ref":"https://github.com/mgrube/CVE-2019-17633","stars":10,"title":"Eclipse Che CSRF leading to RCE"}],"tier":"poc_unverified"},"has_fix":false,"headline":"Cross-site request forgery in Eclipse Che","id":"CVE-2019-17633","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"csrf","year":"2019"},"n_packages":0,"n_references":1,"next":{"headline":"Cross-site scripting in Eclipse Memory Analyzer","id":"CVE-2019-17634"},"packages":[],"prev":{"headline":"Unescaped exception messages in error responses in Jetty","id":"CVE-2019-17632"},"products":["Eclipse Che"],"published":"2019-12-19","related":[{"cvss_score":8.1,"headline":"Supply chain in Eclipse Che","id":"CVE-2021-41034","kev_date_added":null,"published":"2021-09-29"},{"cvss_score":7.1,"headline":"Cross-site request forgery in eclipse","id":"CVE-2020-14368","kev_date_added":null,"published":"2020-12-14"},{"cvss_score":6.4,"headline":"Missing Authorization in Eclipse Che","id":"CVE-2020-10689","kev_date_added":null,"published":"2020-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)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["The Eclipse Foundation"]},"summary":"Attackers can trigger arbitrary workspace starts via CSRF if authentication and TLS are disabled, affecting local Eclipse Che installations.","url":"https://insights.sbomify.com/CVE-2019-17633/"}