Headline
CVE-2023-6194: XXE in Eclipse Memory Analyzer report definition files (#15) · Issues · Eclipse Projects Security / cve-assignement · GitLab
In Eclipse Memory Analyzer versions 0.7 to 1.14.0, report definition XML files are not filtered to prohibit document type definition (DTD) references to external entities. This means that if a user chooses to use a malicious report definition XML file containing an external entity reference to generate a report then Eclipse Memory Analyzer may access external files or URLs defined via a DTD in the report definition.
Skip to content
XXE in Eclipse Memory Analyzer report definition files
The Eclipse Foundation is a Common Vulnerabilities and Exposures (CVE) Numbering Authority. This issue it used to request and track the progress of the assignment of a CVE for a vulnerability in the project code for an Eclipse open source project.
Basic information
Project name: Eclipse Memory Analyzer
Project id: tools.mat
Request type: reservation
Versions affected: [0.7, 1.14.0]
Common Weakness Enumeration:
- CWE-611
Common Vulnerability Scoring System: 3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:L/I:N/A:L/E:U/RL:W/RC:C/CR:X/IR:X/AR:X/MAV:L/MAC:L/MPR:L/MUI:R/MS:U/MC:L/MI:N/MA:L
Summary:
In Eclipse Memory Analyzer versions 0.7 to 1.14.0, report definition XML files are not filtered to prohibit document type definition (DTD) references to external entities. This means that if a user chooses to use a malicious report definition XML file containing an external entity reference to generate a report then Eclipse Memory Analyzer may access external files or URLs defined via a DTD in the report definition.
Workaround:
A workaround for Eclipse Memory Analyzer 1.14.0 and earlier is to run MAT with the following system properties set in MemoryAnalyzer.ini
-Djavax.xml.accessExternalSchema=
-Djavax.xml.accessExternalDTD=
Links:
- https://bugs.eclipse.org/bugs/show_bug.cgi?id=582631
- vulnerability-reports#169 (closed)
Tracking
This section will completed by the project team.
- Reserve an entry only
- We’re ready for this issue to be reported to the central authority (i.e., make this public now)
Note that for those projects that host their repositories on GitHub, the use of GitHub Security Advisories is recommended but is not required.
This section will be completed by the EMO.
CVE: {cve}
- All required information is provided
- CVE Assigned
- Pushed to Mitre
Edited Dec 11, 2023 by Marta Rybczynska