CVE-2025-58045: Dataease server-side request forgery via unfiltered DB2 JDBC ldap parameter
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.
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2025-58045?
CVE-2025-58045 has been classified as a critical vulnerability due to its potential for remote code execution.
How do I fix CVE-2025-58045?
To fix CVE-2025-58045, upgrade Dataease to version 2.10.13 or later.
What versions of Dataease are affected by CVE-2025-58045?
Dataease versions up to and including 2.10.12 are affected by CVE-2025-58045.
What type of attack does CVE-2025-58045 allow?
CVE-2025-58045 allows remote code execution attacks through improperly handled DB2 JDBC connection strings.
Is there a patch available for CVE-2025-58045?
Yes, a patch is available with the release of Dataease version 2.10.13.