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.
Fix
Patch, vendor advisory and mitigation references on NVD 3
- https://github.com/dataease/dataease/commit/77078658715bd85af5867afbfd5f1fcc37cf03c8 Patch
- https://github.com/dataease/dataease/security/advisories/GHSA-fmq3-6xhc-r845 Exploit, Vendor Advisory
- https://github.com/dataease/dataease/security/advisories/GHSA-fmq3-6xhc-r845 Exploit, Vendor Advisory
Every line above is quoted from NVD, CISA, Microsoft, the vendor's own advisory or DISA; nothing is generated.
Change history 1
- First seenCVSS 7.1 · dataeaseNVD modified 2026-10-19 17:10
Affected (CPE criteria) 1
cpe:2.3:a:dataease:dataease:*:*:*:*:*:*:*:*