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.009, 59.3th percentile (scored ); unchanged over 30 days. About EPSS.
Affected products
- Eclipse Equinox P2
- The Eclipse Foundation Equinox P2 — versions 1.0.0
Weakness classification (CWE)
Public exploits and proof-of-concept code
Also mentioned in 1 other repository (howlger/Eclipse-IDE-improvements-videos). These reference the CVE in a list, notes or a scanner and are not exploit code for it.
References
- bugs.eclipse.org/bugs/show_bug.cgi (Mailing List, Vendor Advisory)
- github.com/eclipse-equinox/p2/issues/235 (patch)