CVE-2025-64163 DataEase's DB2 is vulnerable to SSRF
Attackers can exploit missing dns:// protocol filtering to perform Server-Side Request Forgery attacks against DataEase deployments.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2025-64163?
CVE-2025-64163 is a high-severity server-side request forgery vulnerability in Dataease Dataease, published on 5 Nov 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
DataEase is an open source data visualization analysis tool. In versions 2.10.14 and below, the vendor added a blacklist to filter ldap:// and ldaps://. However, omission of protection for the dns:// protocol results in an SSRF vulnerability. This issue is fixed in version 2.10.15.
Weakness: CWE-918
Which versions are affected by CVE-2025-64163?
It affects 1 product.
Products include Dataease Dataease.
How do I fix CVE-2025-64163?
No fix has been published for CVE-2025-64163 yet. Limit exposure of the affected software until one is available.
Upgrade, and send outbound requests through an allow-list that blocks internal addresses. More about Server-side request forgery.
Is CVE-2025-64163 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-64163 exists.
Other vulnerabilities in Dataease Dataease
- CVE-2024-57707 Code injection in n/a
- CVE-2024-46997 DataEase's H2 datasource has a remote command execution risk
- CVE-2023-33963 DataEase data source has deserialization vulnerability
- CVE-2023-28437 SQL injection vulnerability due to the keyword blacklist for defending against SQL injection will be bypassed
- CVE-2022-39312 Dataease Mysql Data Source JDBC Connection Parameters Not Verified Leads to Deserialization Vulnerability
Sources
Also known as GHSA-8397-v66p-539m.