CVE-2023-4218GHSA-J24H-XCPC-9JW8
XXE in eclipse.platform / Eclipse IDE
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 4.29, 2023-09, 3.29.0, 4.29.0, 3.31.0, and 5 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
CISA's decision points: whether it is exploited, whether attacks can be automated, and how much control an attacker gets. Assessed (SSVC 2.0.3).What do these mean? →
- Exploitation: poc
- Automatable: no
- Technical impact: total
Summary
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).
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: poc · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- Eclipse Foundation Eclipse IDE
fixed in 4.29
- Eclipse Foundation Eclipse IDE
fixed in 2023-09
- Eclipse Foundation org.eclipse.core.runtime
fixed in 3.29.0
- Eclipse Foundation org.eclipse.pde
through 3.13.2400
- org.eclipse.platform:org.eclipse.core.runtimeMaven
fixed in 3.29.0
- org.eclipse.platform:org.eclipse.platformMaven
fixed in 4.29.0
- org.eclipse.platform:org.eclipse.jfaceMaven
fixed in 3.31.0
- org.eclipse.platform:org.eclipse.ui.formsMaven
fixed in 3.13.0
- org.eclipse.platform:org.eclipse.ui.ideMaven
fixed in 3.21.100
- org.eclipse.platform:org.eclipse.ui.workbenchMaven
fixed in 3.130.0
- org.eclipse.platform:org.eclipse.urischemeMaven
fixed in 1.3.100
- org.eclipse.jdt:org.eclipse.jdt.uiMaven
fixed in 3.30.0