CVE-2025-24910: Hitachi Vantara Pentaho Business Analytics Server - Improper Restriction of XML External Entity Reference
Overview
XML documents optionally contain a Document Type Definition (DTD), which, among other features, enables the definition of XML entities. It is possible to define an entity by providing a substitution string in the form of a URI. Once the content of the URI is read, it is fed back into the application that is processing the XML. This application may echo back the data (e.g. in an error message), thereby exposing the file contents. (CWE-611)
Description
Hitachi Vantara Pentaho Business Analytics Server versions before 10.2.0.2, including 9.3.x and 8.3.x, do not correctly protect Pentaho Data Integration MessageSourceCrawler against out-of-band XML External Entity Reference.
Impact
By submitting an XML file that defines an external entity with a file:// URI, an attacker can cause the processing application to read the contents of a local file. Using URIs with other schemes such as http://, the attacker can force the application to make outgoing requests to servers that the attacker cannot reach directly, which can be used to bypass firewall restrictions or hide the source of attacks such as port scanning.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2025-24910?
CVE-2025-24910 has been classified with a significant severity rating due to its potential for exploiting XML External Entity (XXE) attacks.
How do I fix CVE-2025-24910?
To mitigate CVE-2025-24910, upgrade your Hitachi Vantara Pentaho Business Analytics Server to version 10.2.0.2 or later.
Which versions of Hitachi Vantara Pentaho are affected by CVE-2025-24910?
CVE-2025-24910 affects Hitachi Vantara Pentaho Business Analytics Server versions prior to 10.2.0.2, including 9.3.x and 8.3.x.
What kind of attack does CVE-2025-24910 facilitate?
CVE-2025-24910 allows for XML External Entity (XXE) attacks, which can lead to unauthorized data exposure.
Is there a workaround for CVE-2025-24910?
There are no recommended workarounds for CVE-2025-24910, and upgrading to a patched version is the only secure solution.