{"answers":{"affected":"4 open source packages ship an affected version, including org.eclipse.xtext:org.eclipse.xtext and org.eclipse.xtend:org.eclipse.xtend.core. It affects 2 products.","exploited":"There is no known exploitation of CVE-2019-10249 in the wild and no public exploit code.","fix":"Upgrade org.eclipse.xtext:org.eclipse.xtext to 2.18.0 or later.","what":"CVE-2019-10249 is a high-severity vulnerability in The Eclipse Foundation Eclipse Xtext, published on 6 May 2019. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2019-10249 and fix it if it is affected.\n\nWhat it is: CVE-2019-10249 is a high-severity vulnerability in The Eclipse Foundation Eclipse Xtext, published on 6 May 2019. 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-2019-10249 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.eclipse.xtext:org.eclipse.xtext (Maven): affected all versions; fixed in 2.18.0\n- org.eclipse.xtext:org.eclipse.xtext (Maven): affected all versions; fixed in 2.18.0\n- org.eclipse.xtend:org.eclipse.xtend.core (Maven): affected all versions; fixed in 2.18.0\n- org.eclipse.xtend:org.eclipse.xtend.core (Maven): affected all versions; fixed in 2.18.0\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-10249/ (Markdown: https://insights.sbomify.com/CVE-2019-10249/index.md)","id":"CVE-2019-10249","markdown":"https://insights.sbomify.com/CVE-2019-10249/index.md","name":"CVE-2019-10249","record":{"aliases":["GHSA-rfj2-4g26-7jw5"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Eclipse Xtext library","requires_auth":"none","summary":"Attackers could compromise Eclipse Xtext artifacts during HTTP-based builds, potentially leading to code execution in dependent applications.","user_interaction":"not_required","vuln_class":"supply_chain"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"eclipse","cpe":[{"product":"xtend","vendor":"eclipse"},{"product":"xtext","vendor":"eclipse"}],"cvss":{"score":8.1,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-116","name":"Improper Encoding or Escaping of Output"},{"id":"CWE-829","name":"Inclusion of Functionality from Untrusted Control Sphere"},{"id":"CWE-494","name":"Download of Code Without Integrity Check"}],"description":"All Xtext \u0026 Xtend versions prior to 2.18.0 were built using HTTP instead of HTTPS file transfer and thus the built artifacts may have been compromised.","ecosystems":["Maven"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Potentially compromised builds","id":"CVE-2019-10249","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"supply_chain","year":"2019"},"n_packages":4,"n_references":2,"next":{"headline":"Other in n/a","id":"CVE-2019-10250"},"packages":[{"ecosystem":"Maven","fixed":["2.18.0"],"introduced":["0"],"last_affected":[],"package":"org.eclipse.xtend:org.eclipse.xtend.core","purl":null,"source":"GHSA-rfj2-4g26-7jw5"},{"ecosystem":"Maven","fixed":["2.18.0"],"introduced":["0"],"last_affected":[],"package":"org.eclipse.xtend:org.eclipse.xtend.core","purl":"pkg:maven/org.eclipse.xtend/org.eclipse.xtend.core","source":"GHSA-rfj2-4g26-7jw5"},{"ecosystem":"Maven","fixed":["2.18.0"],"introduced":["0"],"last_affected":[],"package":"org.eclipse.xtext:org.eclipse.xtext","purl":null,"source":"GHSA-rfj2-4g26-7jw5"},{"ecosystem":"Maven","fixed":["2.18.0"],"introduced":["0"],"last_affected":[],"package":"org.eclipse.xtext:org.eclipse.xtext","purl":"pkg:maven/org.eclipse.xtext/org.eclipse.xtext","source":"GHSA-rfj2-4g26-7jw5"}],"prev":{"headline":"Eclipse Vorto resolved Maven build artifacts for the Xtext project over HTTP instead of HTTPS","id":"CVE-2019-10248"},"products":["Eclipse Xtext"],"published":"2019-05-06","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"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":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["The Eclipse Foundation"]},"summary":"Attackers could compromise Eclipse Xtext artifacts during HTTP-based builds, potentially leading to code execution in dependent applications.","url":"https://insights.sbomify.com/CVE-2019-10249/"}