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.
References
Link | Resource |
---|---|
https://bugs.eclipse.org/bugs/show_bug.cgi?id=577029 | Mailing List Vendor Advisory |
https://github.com/eclipse-equinox/p2/issues/235 |
Configurations
History
12 Jul 2024, 14:15
Type | Values Removed | Values Added |
---|---|---|
References |
|
Information
Published : 2022-07-08 04:15
Updated : 2024-07-12 14:15
NVD link : CVE-2021-41037
Mitre link : CVE-2021-41037
CVE.ORG link : CVE-2021-41037
JSON object : View
Products Affected
eclipse
- equinox_p2
CWE
CWE-829
Inclusion of Functionality from Untrusted Control Sphere