Skip to content

Eclipse IDE XXE in eclipse.platform

Moderate severity GitHub Reviewed Published Nov 29, 2023 in eclipse-platform/eclipse.platform • Updated Mar 5, 2024

Package

maven org.eclipse.jdt:org.eclipse.jdt.ui (Maven)

Affected versions

< 3.30.0

Patched versions

3.30.0
maven org.eclipse.platform:org.eclipse.core.runtime (Maven)
< 3.29.0
3.29.0
maven org.eclipse.platform:org.eclipse.jface (Maven)
< 3.31.0
3.31.0
maven org.eclipse.platform:org.eclipse.platform (Maven)
< 4.29.0
4.29.0
maven org.eclipse.platform:org.eclipse.ui.forms (Maven)
< 3.13.0
3.13.0
maven org.eclipse.platform:org.eclipse.ui.ide (Maven)
< 3.21.100
3.21.100
maven org.eclipse.platform:org.eclipse.ui.workbench (Maven)
< 3.130.0
3.130.0
maven org.eclipse.platform:org.eclipse.urischeme (Maven)
< 1.3.100
1.3.100

Description

Impact

xml files like ".project" 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).

Vulnerablility was found by static code analysis (SonarLint).

Example .project file:

<?xml version="1.0" encoding="utf-8"?> 
<!DOCTYPE price [
<!ENTITY xxe SYSTEM "http://127.0.0.1:49416/evil">]>
<projectDescription>
	<name>p</name>
	<comment>&xxe;</comment>
</projectDescription>

Patches

Similar patches including junit test that shows the vulnerability have already applied to PDE (see eclipse-pde/eclipse.pde#667). A solution to platform should be the same: just reject parsing any XML that contains any DOCTYPE.

Workarounds

No known workaround. User can only avoid to get/open any foreign files with eclipse. Firewall rules against loss of data (but not against XML bomb).

References

https://cwe.mitre.org/data/definitions/611.html
https://rules.sonarsource.com/java/RSPEC-2755
https://gitlab.eclipse.org/security/vulnerability-reports/-/issues/8 (Report for multiple projects affected)

References

@mrybczyn mrybczyn published to eclipse-platform/eclipse.platform Nov 29, 2023
Published to the GitHub Advisory Database Nov 30, 2023
Reviewed Nov 30, 2023
Last updated Mar 5, 2024

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:N/A:N

EPSS score

0.046%
(18th percentile)

Weaknesses

No CWEs

CVE ID

CVE-2023-4218

GHSA ID

GHSA-j24h-xcpc-9jw8

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.