CVE-2021-41033

8.1 HIGH

📋 TL;DR

This vulnerability allows man-in-the-middle attacks when Eclipse Equinox installations use HTTP repositories for p2 updates. Attackers can intercept and modify update metadata to install malicious plugins that execute arbitrary code. All Eclipse Equinox users who update via HTTP repositories are affected.

💻 Affected Systems

Products:
  • Eclipse Equinox
Versions: All versions up to and including 4.21 (September 2021)
Operating Systems: All platforms running Eclipse Equinox
Default Config Vulnerable: ⚠️ Yes
Notes: Only affects installations using HTTP p2 repositories for updates. HTTPS repositories are not vulnerable.

📦 What is this software?

⚠️ Risk & Real-World Impact

🔴

Worst Case

Complete compromise of the Eclipse installation with execution of arbitrary malicious code, potentially leading to system takeover, data theft, or lateral movement.

🟠

Likely Case

Installation of malicious plugins that could steal credentials, exfiltrate data, or provide persistent backdoor access.

🟢

If Mitigated

No impact if using HTTPS repositories or network controls prevent HTTP MITM attacks.

🌐 Internet-Facing: HIGH - HTTP repositories over internet connections are highly vulnerable to MITM attacks.
🏢 Internal Only: MEDIUM - Internal networks still vulnerable to internal attackers or compromised systems performing MITM.

🎯 Exploit Status

Public PoC: ✅ No
Weaponized: LIKELY
Unauthenticated Exploit: ⚠️ Yes
Complexity: LOW

Standard MITM techniques can be used. No authentication required to intercept HTTP traffic.

🛠️ Fix & Mitigation

✅ Official Fix

Patch Version: Versions after 4.21

Vendor Advisory: https://bugs.eclipse.org/bugs/show_bug.cgi?id=575688

Restart Required: Yes

Instructions:

1. Update Eclipse Equinox to version after 4.21. 2. Ensure all p2 repositories use HTTPS URLs. 3. Restart Eclipse/Equinox after update.

🔧 Temporary Workarounds

Force HTTPS repositories

all

Configure all p2 repositories to use HTTPS instead of HTTP

Edit Eclipse/Equinox configuration to replace 'http://' with 'https://' in all repository URLs

Network segmentation

all

Isolate Eclipse update traffic to trusted networks

Configure firewall rules to restrict HTTP traffic to trusted update servers only

🧯 If You Can't Patch

  • Use only HTTPS p2 repositories for all updates
  • Implement network monitoring for MITM attacks on HTTP update traffic

🔍 How to Verify

Check if Vulnerable:

Check if any p2 repository URLs in Eclipse/Equinox configuration start with 'http://' instead of 'https://'

Check Version:

Check Eclipse About dialog or equinox version file

Verify Fix Applied:

Verify all p2 repository URLs use HTTPS and Equinox version is >4.21

📡 Detection & Monitoring

Log Indicators:

  • Unexpected plugin installations
  • Update failures or warnings about repository security

Network Indicators:

  • HTTP traffic to p2 repositories
  • Unusual update patterns or sources

SIEM Query:

Search for HTTP requests to p2.eclipse.org or other p2 repositories

🔗 References

📤 Share & Export