{"answers":{"affected":"2 open source packages ship an affected version, including org.eclipse.vorto:org.eclipse.vorto.core. It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-10248 in the wild and no public exploit code.","fix":"Upgrade org.eclipse.vorto:org.eclipse.vorto.core to 0.11.0 or later.","what":"CVE-2019-10248 is a high-severity vulnerability in The Eclipse Foundation Eclipse Vorto, published on 22 Apr 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-10248 and fix it if it is affected.\n\nWhat it is: CVE-2019-10248 is a high-severity vulnerability in The Eclipse Foundation Eclipse Vorto, published on 22 Apr 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-10248 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.eclipse.vorto:org.eclipse.vorto.core (Maven): affected all versions; fixed in 0.11.0\n- org.eclipse.vorto:org.eclipse.vorto.core (Maven): affected all versions; fixed in 0.11.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-10248/ (Markdown: https://insights.sbomify.com/CVE-2019-10248/index.md)","id":"CVE-2019-10248","markdown":"https://insights.sbomify.com/CVE-2019-10248/index.md","name":"CVE-2019-10248","record":{"aliases":["GHSA-fg2q-v428-2gph"],"analysis":{"component_type":"developer_tool","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Eclipse Vorto","requires_auth":"none","summary":"Attackers can compromise build artifacts via MITM during Maven dependency resolution, leading to infected software builds.","user_interaction":"not_required","vuln_class":"supply_chain"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"eclipse","cpe":[{"product":"vorto","vendor":"eclipse"}],"cvss":{"score":8.1,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.0"},"cwes":[{"id":"CWE-669","name":"Incorrect Resource Transfer Between Spheres"},{"id":"CWE-829","name":"Inclusion of Functionality from Untrusted Control Sphere"},{"id":"CWE-494","name":"Download of Code Without Integrity Check"}],"description":"Eclipse Vorto versions prior to 0.11 resolved Maven build artifacts for the Xtext project over HTTP instead of HTTPS. Any of these dependent artifacts could have been maliciously compromised by a MITM attack. Hence produced build artifacts of Vorto might be infected.","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":"Eclipse Vorto resolved Maven build artifacts for the Xtext project over HTTP instead of HTTPS","id":"CVE-2019-10248","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"supply_chain","year":"2019"},"n_packages":2,"n_references":1,"next":{"headline":"Potentially compromised builds","id":"CVE-2019-10249"},"packages":[{"ecosystem":"Maven","fixed":["0.11.0"],"introduced":["0"],"last_affected":[],"package":"org.eclipse.vorto:org.eclipse.vorto.core","purl":null,"source":"GHSA-fg2q-v428-2gph"},{"ecosystem":"Maven","fixed":["0.11.0"],"introduced":["0"],"last_affected":[],"package":"org.eclipse.vorto:org.eclipse.vorto.core","purl":"pkg:maven/org.eclipse.vorto/org.eclipse.vorto.core","source":"GHSA-fg2q-v428-2gph"}],"prev":{"headline":"Installation information leak in Eclipse Jetty","id":"CVE-2019-10247"},"products":["Eclipse Vorto"],"published":"2019-04-22","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 can compromise build artifacts via MITM during Maven dependency resolution, leading to infected software builds.","url":"https://insights.sbomify.com/CVE-2019-10248/"}