# CVE-2023-4218: XXE in eclipse.platform / Eclipse IDE > Attackers can exploit XML External Entity vulnerabilities in Eclipse IDE by tricking users into opening malicious projects, leading to data exposure or code execution. - **Severity:** Medium 5.0 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:N/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Local or same network only - **Victim action needed:** A user has to click or open something - **Fix available:** Yes - **Published:** 9 Nov 2023 - **Updated:** 3 Sep 2024 - **Also known as:** GHSA-j24h-xcpc-9jw8, SUSE-SU-2024:1304-1, UBUNTU-CVE-2023-4218, openSUSE-SU-2024:13786-1, openSUSE-SU-2024:13787-1 ## What is CVE-2023-4218? CVE-2023-4218 is a medium-severity vulnerability in Eclipse IDE, published on 9 Nov 2023. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link. ### Official 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). Weakness: CWE-611 (Improper Restriction of XML External Entity Reference) ## Which versions are affected by CVE-2023-4218? 16 open source packages ship an affected version, including org.eclipse.platform:org.eclipse.ui.ide, org.eclipse.jdt:org.eclipse.jdt.ui and org.eclipse.platform:org.eclipse.core.runtime. It affects 3 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `org.eclipse.platform:org.eclipse.ui.ide` | Maven | All versions | 3.21.100 | | `org.eclipse.platform:org.eclipse.ui.ide` | Maven | All versions | 3.21.100 | | `org.eclipse.jdt:org.eclipse.jdt.ui` | Maven | All versions | 3.30.0 | | `org.eclipse.jdt:org.eclipse.jdt.ui` | Maven | All versions | 3.30.0 | | `org.eclipse.platform:org.eclipse.core.runtime` | Maven | All versions | 3.29.0 | | `org.eclipse.platform:org.eclipse.core.runtime` | Maven | All versions | 3.29.0 | | `org.eclipse.platform:org.eclipse.jface` | Maven | All versions | 3.31.0 | | `org.eclipse.platform:org.eclipse.jface` | Maven | All versions | 3.31.0 | | `org.eclipse.platform:org.eclipse.platform` | Maven | All versions | 4.29.0 | | `org.eclipse.platform:org.eclipse.platform` | Maven | All versions | 4.29.0 | | `org.eclipse.platform:org.eclipse.ui.forms` | Maven | All versions | 3.13.0 | | `org.eclipse.platform:org.eclipse.ui.forms` | Maven | All versions | 3.13.0 | | `org.eclipse.platform:org.eclipse.ui.workbench` | Maven | All versions | 3.130.0 | | `org.eclipse.platform:org.eclipse.ui.workbench` | Maven | All versions | 3.130.0 | | `org.eclipse.platform:org.eclipse.urischeme` | Maven | All versions | 1.3.100 | | `org.eclipse.platform:org.eclipse.urischeme` | Maven | All versions | 1.3.100 | | `maven-surefire` | SUSE:Enterprise Storage 7.1 | All versions | 2.22.2-150200.3.9.9.1 | | `maven-surefire-plugins` | SUSE:Enterprise Storage 7.1 | All versions | 2.22.2-150200.3.9.9.1 | | `maven-surefire` | SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSS | All versions | 2.22.2-150200.3.9.9.1 | | `maven-surefire-plugins` | SUSE:Linux Enterprise High Performance Computing 15 SP2-LTSS | All versions | 2.22.2-150200.3.9.9.1 | | `maven-surefire` | SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSS | All versions | 2.22.2-150200.3.9.9.1 | | `maven-surefire-plugins` | SUSE:Linux Enterprise High Performance Computing 15 SP3-LTSS | All versions | 2.22.2-150200.3.9.9.1 | | `maven-surefire` | SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS | All versions | 2.22.2-150200.3.9.9.1 | | `maven-surefire-plugins` | SUSE:Linux Enterprise High Performance Computing 15 SP4-ESPOS | All versions | 2.22.2-150200.3.9.9.1 | | `maven-surefire` | SUSE:Linux Enterprise High Performance Computing 15 SP4-LTSS | All versions | 2.22.2-150200.3.9.9.1 | | `maven-surefire-plugins` | SUSE:Linux Enterprise High Performance Computing 15 SP4-LTSS | All versions | 2.22.2-150200.3.9.9.1 | | `maven-surefire` | SUSE:Linux Enterprise Module for Development Tools 15 SP5 | All versions | 2.22.2-150200.3.9.9.1 | | `maven-surefire-plugins` | SUSE:Linux Enterprise Module for Development Tools 15 SP5 | All versions | 2.22.2-150200.3.9.9.1 | | `eclipse` | SUSE:Linux Enterprise Module for Package Hub 15 SP5 | All versions | 4.15-150200.4.16.4 | | `eclipse-bootstrap` | SUSE:Linux Enterprise Module for Package Hub 15 SP5 | All versions | 4.15-150200.4.16.5 | | `eclipse-emf` | SUSE:Linux Enterprise Module for Package Hub 15 SP5 | All versions | 2.22.0-150200.4.9.3 | | `eclipse-emf-bootstrap` | SUSE:Linux Enterprise Module for Package Hub 15 SP5 | All versions | 2.22.0-150200.4.9.3 | | `maven-surefire` | SUSE:Linux Enterprise Server 15 SP2-LTSS | All versions | 2.22.2-150200.3.9.9.1 | | `maven-surefire-plugins` | SUSE:Linux Enterprise Server 15 SP2-LTSS | All versions | 2.22.2-150200.3.9.9.1 | | `maven-surefire` | SUSE:Linux Enterprise Server 15 SP3-LTSS | All versions | 2.22.2-150200.3.9.9.1 | | `maven-surefire-plugins` | SUSE:Linux Enterprise Server 15 SP3-LTSS | All versions | 2.22.2-150200.3.9.9.1 | | `maven-surefire` | SUSE:Linux Enterprise Server 15 SP4-LTSS | All versions | 2.22.2-150200.3.9.9.1 | | `maven-surefire-plugins` | SUSE:Linux Enterprise Server 15 SP4-LTSS | All versions | 2.22.2-150200.3.9.9.1 | | `maven-surefire` | SUSE:Linux Enterprise Server for SAP Applications 15 SP2 | All versions | 2.22.2-150200.3.9.9.1 | | `maven-surefire-plugins` | SUSE:Linux Enterprise Server for SAP Applications 15 SP2 | All versions | 2.22.2-150200.3.9.9.1 | Products: Eclipse Eclipse Ide, Eclipse Org.eclipse.core.runtime, Eclipse Pde. ## How do I fix CVE-2023-4218? Upgrade org.eclipse.platform:org.eclipse.ui.ide to 3.21.100 or later. ## Is CVE-2023-4218 being exploited? It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-4218 exists. ## Other vulnerabilities in Eclipse IDE - [CVE-2008-7271](https://insights.sbomify.com/CVE-2008-7271/): Cross-site scripting in n/a (medium 4.3) - [CVE-2010-4647](https://insights.sbomify.com/CVE-2010-4647/): Cross-site scripting in n/a (medium 4.3) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2023-4218 and fix it if it is affected. What it is: CVE-2023-4218 is a medium-severity vulnerability in Eclipse IDE, published on 9 Nov 2023. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link. Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-4218 exists. Affected packages and fixed versions: - org.eclipse.platform:org.eclipse.ui.ide (Maven): affected all versions; fixed in 3.21.100 - org.eclipse.platform:org.eclipse.ui.ide (Maven): affected all versions; fixed in 3.21.100 - org.eclipse.jdt:org.eclipse.jdt.ui (Maven): affected all versions; fixed in 3.30.0 - org.eclipse.jdt:org.eclipse.jdt.ui (Maven): affected all versions; fixed in 3.30.0 - org.eclipse.platform:org.eclipse.core.runtime (Maven): affected all versions; fixed in 3.29.0 - org.eclipse.platform:org.eclipse.core.runtime (Maven): affected all versions; fixed in 3.29.0 - org.eclipse.platform:org.eclipse.jface (Maven): affected all versions; fixed in 3.31.0 - org.eclipse.platform:org.eclipse.jface (Maven): affected all versions; fixed in 3.31.0 - org.eclipse.platform:org.eclipse.platform (Maven): affected all versions; fixed in 4.29.0 - org.eclipse.platform:org.eclipse.platform (Maven): affected all versions; fixed in 4.29.0 - org.eclipse.platform:org.eclipse.ui.forms (Maven): affected all versions; fixed in 3.13.0 - org.eclipse.platform:org.eclipse.ui.forms (Maven): affected all versions; fixed in 3.13.0 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2023-4218/ (Markdown: https://insights.sbomify.com/CVE-2023-4218/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2023-4218 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-4218 - OSV: https://osv.dev/vulnerability/CVE-2023-4218 --- From sbomify Insights: https://insights.sbomify.com/CVE-2023-4218/ Summaries are generated and may contain mistakes; the official description above is the record.