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.
problem types: CWE-829
affected:
{
product: Eclipse Equinox p2
vendor: The Eclipse Foundation
versions:
lessThan: unspecified, status: affected, version: 1.0.0, versionType: custom
}
metrics:
cvssV3_1: [
attackComplexity: LOW
attackVector: NETWORK
availabilityImpact: LOW
availabilityRequirement: MEDIUM
baseScore: 5.5
baseSeverity: MEDIUM
confidentialityImpact: LOW
confidentialityRequirement: MEDIUM
environmentalScore: 5.7
environmentalSeverity: MEDIUM
exploitCodeMaturity: PROOF_OF_CONCEPT
integrityImpact: LOW
integrityRequirement: MEDIUM
modifiedAttackComplexity: LOW
modifiedAttackVector: NETWORK
modifiedAvailabilityImpact: LOW
modifiedConfidentialityImpact: LOW
modifiedIntegrityImpact: LOW
modifiedPrivilegesRequired: NONE
modifiedScope: UNCHANGED
modifiedUserInteraction: REQUIRED
privilegesRequired: LOW
remediationLevel: UNAVAILABLE
reportConfidence: REASONABLE
scope: UNCHANGED
temporalScore: 5
temporalSeverity: MEDIUM
userInteraction: REQUIRED
vectorString: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:L/A:L/E:P/RL:U/RC:R/CR:M/IR:M/AR:M/MAV:N/MAC:L/MPR:N/MUI:R/MS:U/MC:L/MI:L/MA:L
version: 3.1
]