LiveActive security incident?Get immediate response
CVE Record

CVE-2021-41033: In all released versions of Eclipse Equinox, at least until version 4.21 (September 2021), installation can...

In all released versions of Eclipse Equinox, at least until version 4.21 (September 2021), installation can be vulnerable to man-in-the-middle attack if using p2 repos that are HTTP; that can then be exploited to serve incorrect p2 metadata and entirely alter the local installation, particularly by installing plug-ins that may then run malicious code.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

Eclipse Equinox installations that fetch p2 update repositories over HTTP can be tricked through a man-in-the-middle condition. An attacker who can tamper with that traffic could change update metadata and alter the local installation, including adding plug-ins that may run malicious code.

Executive priority

Prioritize if Equinox is used in build, development, or operational tooling that pulls updates over HTTP. Business urgency is lower where p2 repositories are already HTTPS-only and trusted.

Technical view

CVE-2021-41033 is a CWE-300 issue in Eclipse Equinox p2 installation flows using HTTP repositories. The source describes all released versions at least through 4.21 as vulnerable. Incorrect p2 metadata can be served during installation, potentially changing the installed plug-in set. No CVSS score is provided.

Likely exposure

Exposure is most likely where Eclipse Equinox installations or update workflows consume p2 repositories over plain HTTP. HTTPS-only p2 repositories are not described as affected in the provided source bundle.

Exploitation context

The source bundle does not show CISA KEV listing or cited active exploitation. Exploitation depends on an attacker being able to interfere with HTTP p2 repository traffic or repository metadata delivery.

Researcher notes

The public bundle is narrow: it identifies the attack class, affected product, and high-level impact, but does not provide CVSS, a named patch version, exploit evidence, or detailed remediation instructions.

Mitigation direction

  • Inventory Eclipse Equinox installations and p2 repository URLs.
  • Remove or replace HTTP p2 repositories with HTTPS sources.
  • Check Eclipse bug 575688 and vendor guidance for version-specific fixes.
  • Treat untrusted plug-ins installed through HTTP update paths as suspect.

Validation and detection

  • Review p2 repository configuration for plain HTTP URLs.
  • Confirm Equinox versions, especially deployments at or before 4.21.
  • Check installation history for unexpected plug-ins or repository changes.
  • Verify update workflows use trusted HTTPS repositories only.
Prepared
Confidence
medium
Sources
3

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-300: 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-41033 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
Unknown
CVSS
Not scored
Known Exploited
No
Published
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.

0CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
The Eclipse FoundationEclipse EquinoxunspecifiedListed
Weakness

CWE details

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

CWE-300 · source CWE mapping

Channel Accessible by Non-Endpoint

Channel Accessible by Non-Endpoint represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.