Vulnerability in Eclipse Equinox P2
CVE-2021-41037
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.
Published · last modified .
CVSS v3 metric
CVSS v3 base score 10.0 (Critical). Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H.
EPSS exploit prediction
EPSS: 0.008 (56.4th percentile), scored .
Very low probability of exploitation in the next 30 days; routine patching cadence is appropriate. 56th percentile — 56.4% of CVEs in the catalogue have a lower EPSS than this one. How to read EPSS.
EPSS over last 30 days · oldest: 0.008 · newest: 0.008 · change: +0.000
Affected products
- Eclipse Equinox P2
- The Eclipse Foundation Equinox P2 — versions 1.0.0
Weakness classification (CWE)
Public proof-of-concept exploits
References
- bugs.eclipse.org/bugs/show_bug.cgi (Mailing List, Vendor Advisory)
- github.com/eclipse-equinox/p2/issues/235 (patch)
Frequently asked questions
- What is CVE-2021-41037?
- CVE-2021-41037 is a critical-severity vulnerability in Eclipse Equinox P2, classified under Inclusion of Functionality from Untrusted Control Sphere. CVSS score: 10.0/10. Published 2022-07-08.
- How severe is CVE-2021-41037?
- Critical severity. CVSS v3 base score is 10.0 out of 10.
- Is CVE-2021-41037 known to be exploited?
- 1 public proof-of-concept repositories are indexed. Not currently listed in the CISA KEV catalog.