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.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:HEclipse Equinox P2
APPEclipse≥ 1.0.0
Related vulnerabilities
A critical Remote Code Execution (RCE) vulnerability was identified in the server-side template rendering mech...
An authenticated Remote Code Execution (RCE) vulnerability was identified in GlassFish's Administration Consol...
Path Traversal w Eclipse OpenMQ umożliwia odczyt plików i potencjalny RCE
Eclipse OpenMQ — domyślne dane logowania umożliwiają przejęcie kontroli
Eclipse Theia Website: RCE w CI/CD przez podatny trigger GitHub Actions