LiveActive security incident?Get immediate response
CVE Record

CVE-2021-41037: In Eclipse p2, installable units are able to alter the Eclipse Platform installation and the local machine...

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.

CriticalCVSS 10Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

Eclipse p2 can install units that change how the Eclipse Platform starts or behaves. The sources say p2 verifies artifact signatures, but not the metadata that defines installation touchpoints. A malicious unit from an untrusted source could run code during installation without a clear warning.

Executive priority

Prioritize review where Eclipse-based tooling or platforms install extensions from external repositories. The CVSS score is critical, but urgency depends on whether untrusted p2 content can be installed in your environment.

Technical view

CVE-2021-41037 is a CWE-829 trust-of-remote-resource issue in Eclipse Equinox p2. Installable-unit metadata can configure touchpoints that modify the platform installation or local machine, including startup command-line settings. The supplied record lists CVSS 3.1 score 10.0.

Likely exposure

Exposure is most likely where Eclipse Equinox p2 installs units from untrusted or weakly governed update sources. The bundle only names Eclipse Equinox p2 version 1.0.0, so broader version impact should be confirmed with Eclipse guidance.

Exploitation context

The provided sources do not show CISA KEV listing or active exploitation evidence. Risk comes from installing a malicious p2 unit whose metadata triggers unsafe installation behavior without the user receiving a warning.

Researcher notes

Evidence is limited to the CVE description, Eclipse bug reference, and GitHub issue marked patch. The bundle does not provide a fixed version, proof of exploitation, or full affected-version range, so avoid over-scoping without vendor confirmation.

Mitigation direction

  • Restrict p2 installations to trusted, governed repositories.
  • Review Eclipse bug 577029 and p2 issue 235 for vendor guidance.
  • Apply any Eclipse-provided fixed p2 version when identified.
  • Avoid installing units from unknown or untrusted sources.
  • Treat p2 metadata and touchpoints as privileged change inputs.

Validation and detection

  • Inventory systems and products using Eclipse Equinox p2.
  • Check configured p2 update sites and repository trust controls.
  • Confirm installed p2 versions against Eclipse guidance.
  • Review recent p2 installations for unexpected startup or configuration changes.
  • Verify whether issue 235 patch guidance is applied.
Prepared
Confidence
medium
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-829: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2021-41037 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
10 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
10CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H3.96Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

10Critical
CVSS 3.1 vector shape for CVE-2021-41037Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
The Eclipse FoundationEclipse Equinox p21.0.0unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.