CVE-2021-41037
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.
Does this matter?
High impact if exploited, but EPSS currently rates exploitation as unlikely (0.82%). Schedule it in the normal patch cycle and watch for a rise in EPSS or a public exploit.
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.
- CVSS 3.1
- 8.0 HIGHCVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H
- EPSS
- 0.82% probability · 55th percentile
- CISA KEV
- Not listed
- Weakness
- CWE-829
- Affected
- eclipse/equinox p2
- Source
- emo@eclipse.org
References
- https://bugs.eclipse.org/bugs/show_bug.cgi?id=577029Mailing List, Vendor Advisory
- https://github.com/eclipse-equinox/p2/issues/235
- https://bugs.eclipse.org/bugs/show_bug.cgi?id=577029Mailing List, Vendor Advisory
- https://github.com/eclipse-equinox/p2/issues/235
Source: NVD record, EPSS from FIRST.org, KEV from CISA. Refreshed daily.