CVE-2023-4218 is a medium-severity (CVSS 5) XML External Entity (XXE) vulnerability in org.eclipse.platform:org.eclipse.core.runtime. 1 public exploit reference exists, so weaponization risk is real. A fix is available for org.eclipse.platform:org.eclipse.core.runtime — see the affected versions and patch details below.
XXE in eclipse.platform / Eclipse IDE
Exploitation Status
Proof-of-concept exploit code exists
- CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
- A successful exploit gives an attacker total control of the affected component, not partial access.
Exploitation and automatability from CISA’s SSVC triage for CVE-2023-4218.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
CVE-2023-4218 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 377,333 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
org.eclipse.platform:org.eclipse.core.runtime☕org.eclipse.platform:org.eclipse.platform☕org.eclipse.platform:org.eclipse.jface☕org.eclipse.platform:org.eclipse.ui.forms☕org.eclipse.platform:org.eclipse.ui.ide☕org.eclipse.platform:org.eclipse.ui.workbench☕org.eclipse.platform:org.eclipse.urischeme☕org.eclipse.jdt:org.eclipse.jdt.uiReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
In Eclipse IDE versions < 2023-09 (4.29) some files with xml content are parsed vulnerable against all sorts of XXE attacks. The user just needs to open any evil project or update an open project with a vulnerable file (for example for review a foreign repository or patch).
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.eclipse.platform:org.eclipse.core.runtime | all versions | 3.29.0org.eclipse.platform:org.eclipse.core.runtime:3.29.0 |
| ☕Maven | org.eclipse.platform:org.eclipse.platform | all versions | 4.29.0org.eclipse.platform:org.eclipse.platform:4.29.0 |
| ☕Maven | org.eclipse.platform:org.eclipse.jface | all versions | 3.31.0org.eclipse.platform:org.eclipse.jface:3.31.0 |
| ☕Maven | org.eclipse.platform:org.eclipse.ui.forms | all versions | 3.13.0org.eclipse.platform:org.eclipse.ui.forms:3.13.0 |
| ☕Maven | org.eclipse.platform:org.eclipse.ui.ide | all versions | 3.21.100org.eclipse.platform:org.eclipse.ui.ide:3.21.100 |
| ☕Maven | org.eclipse.platform:org.eclipse.ui.workbench | all versions | 3.130.0org.eclipse.platform:org.eclipse.ui.workbench:3.130.0 |
Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.eclipse.platform:org.eclipse.core.runtime, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.eclipse.platform:org.eclipse.core.runtime to 3.29.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-4218 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2023-4218 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2023-4218. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2023-4218 in your dependencies?
O3 Security finds CVE-2023-4218 across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.