Dataease up to 2.10.12 JDBC Connection rmi server-side request forgery

Summaryinfo

A vulnerability has been found in Dataease up to 2.10.12 and classified as critical. This affects an unknown part of the component JDBC Connection Handler. Performing a manipulation of the argument rmi results in server-side request forgery. This vulnerability is reported as CVE-2025-58045. The attack is possible to be carried out remotely. No exploit exists. The affected component should be upgraded.

Detailsinfo

A vulnerability classified as critical has been found in Dataease up to 2.10.12. This affects an unknown part of the component JDBC Connection Handler. The manipulation of the argument rmi with an unknown input leads to a server-side request forgery vulnerability. CWE is classifying the issue as CWE-918. The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

Dataease is an open source data analytics and visualization platform. In Dataease versions up to 2.10.12, the patch introduced to mitigate DB2 JDBC deserialization remote code execution attacks only blacklisted the rmi parameter. The ldap parameter in the DB2 JDBC connection string was not filtered, allowing attackers to exploit the DB2 JDBC connection string to trigger server-side request forgery (SSRF). In higher versions of Java, ldap deserialization (autoDeserialize) is disabled by default, preventing remote code execution, but SSRF remains exploitable. Versions up to 2.10.12 are affected. The issue is fixed in version 2.10.13. Updating to 2.10.13 or later is recommended. No known workarounds are documented aside from upgrading.

The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2025-58045 since 08/22/2025. The exploitability is told to be easy. It is possible to initiate the attack remotely. Technical details are known, but no exploit is available.

Upgrading to version 2.10.13 eliminates this vulnerability. Applying the patch 77078658715bd85af5867afbfd5f1fcc37cf03c8 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.

The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2025-29209). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Name

• Dataease

Version

• 2.10.0
• 2.10.1
• 2.10.2
• 2.10.3
• 2.10.4
• 2.10.5
• 2.10.6
• 2.10.7
• 2.10.8
• 2.10.9
• 2.10.10
• 2.10.11
• 2.10.12

License

• open-source

Website

• Product: https://github.com/dataease/dataease/

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion