cve.bz

CVE-2021-41033 eclipse equinox: Channel Accessible by Non-Endpoint

8.1 highEPSS 1.1%

High (8.1) in eclipse equinox. EPSS 1.1% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 3.1

8.1 high
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS
1.1% (unchanged from 1.1% a week ago; 1.1% 30 days ago) estimated probability of exploitation activity in the next 30 days; 67th percentile. Scored 2026-11-22. A forecast for this CVE across the internet, not for your own systems.
CWE
CWE-300 Channel Accessible by Non-Endpoint
OWASP Top 10
A07:2025 Authentication Failures
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2021-41033 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2021-41033?via=ask-ai-copy and https://cve.bz/cve/CVE-2021-41033?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2021-41033 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
eclipse:equinoxbefore 4.21
eclipse:equinox4.21

Attack patterns (CAPEC)

  • CAPEC-57 Utilizing REST's Trust in the System Resource to Obtain Sensitive Data Likelihood: Medium · Severity: Very High
  • CAPEC-94 Adversary in the Middle (AiTM) Likelihood: High · Severity: Very High
  • CAPEC-466 Leveraging Active Adversary in the Middle Attacks to Bypass Same Origin Policy Severity: Medium
  • CAPEC-589 DNS Blocking
  • CAPEC-590 IP Address Blocking Likelihood: Low · Severity: High
  • CAPEC-612 WiFi MAC Address Tracking Severity: Low
  • CAPEC-613 WiFi SSID Tracking Severity: Low
  • CAPEC-615 Evil Twin Wi-Fi Attack Severity: Low
  • CAPEC-662 Adversary in the Browser (AiTB) Likelihood: High · Severity: Very High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON