{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-41037 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2021-41037 yet. Limit exposure of the affected software until one is available.","what":"CVE-2021-41037 is a critical code injection vulnerability in The Eclipse Foundation Eclipse Equinox p2, published on 8 Jul 2022. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2021-41037 and fix it if it is affected.\n\nWhat it is: CVE-2021-41037 is a critical code injection vulnerability in The Eclipse Foundation Eclipse Equinox p2, published on 8 Jul 2022. 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-2021-41037 in the wild and no public exploit code.\n\nAffected product: The Eclipse Foundation Eclipse Equinox p2. 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-2021-41037/ (Markdown: https://insights.sbomify.com/CVE-2021-41037/index.md)","id":"CVE-2021-41037","markdown":"https://insights.sbomify.com/CVE-2021-41037/index.md","name":"CVE-2021-41037","record":{"aliases":["GHSA-99r4-wvv3-fpr3"],"analysis":{"component_type":"developer_tool","fix_type":"patch","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Eclipse p2 installer","requires_auth":"none","summary":"Attackers can inject malicious code into Eclipse installations via unsigned metadata in p2 touchpoints, leading to arbitrary code execution during installation.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"eclipse","cpe":[{"product":"equinox_p2","vendor":"eclipse"}],"cvss":{"score":10,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-829","name":"Inclusion of Functionality from Untrusted Control Sphere"}],"description":"In Eclipse p2, installable units are able to alter the Eclipse Platform installation and the local machine via touchpoints during installation. Those touchpoints can, for example, alter the command-line used to start the application, injecting things like agent or other settings that usually require particular attention in term of security. Although p2 has built-in strategies to ensure artifacts are signed and then to help establish trust, there is no such strategy for the metadata part that does configure such touchpoints. As a result, it's possible to install a unit that will run malicious code during installation without user receiving any warning about this installation step being risky when coming from untrusted source.","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":"Code injection in Eclipse Equinox p2","id":"CVE-2021-41037","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"code_injection","year":"2021"},"n_packages":0,"n_references":2,"next":{"headline":"Improper Verification of Communication Channel in @theia/plugin-ext","id":"CVE-2021-41038"},"packages":[],"prev":{"headline":"Memory corruption in Eclipse Paho MQTT C Client","id":"CVE-2021-41036"},"products":["Eclipse Equinox p2"],"published":"2022-07-08","related":[],"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":"yes","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2024-08-04","vendors":["The Eclipse Foundation"]},"summary":"Attackers can inject malicious code into Eclipse installations via unsigned metadata in p2 touchpoints, leading to arbitrary code execution during installation.","url":"https://insights.sbomify.com/CVE-2021-41037/"}