dbcve.org
DataeaseApplication

CVE-2025-64163

CRITICAL · 9.8 CVSS v3.1 Published 2025-11-06
Fix available
A fix is available. Upgrade to 2.10.15 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

DataEase versions 2.10.14 and below have an SSRF vulnerability due to an incomplete protocol blacklist. While ldap:// and ldaps:// protocols were blocked, the dns:// protocol was not included, allowing attackers to make the server perform arbitrary DNS queries to internal resources or exfiltrate data via DNS tunnels.

MitigationUpgrade to DataEase version 2.10.15 or later, which includes dns:// in the protocol blacklist. Alternatively, implement network-level filtering to block dns:// protocol requests.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
DataeaseApplication
Affected:< 2.10.15

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed DataEase version
    Locate the DataEase application version through the admin UI (typically in Settings > About) or check the version file in the installation directory if accessible via shell
    Affected if version displayed is 2.10.14 or below, or the version cannot be confirmed as 2.10.15 or later
  2. Locate protocol validation code
    Search the DataEase codebase for references to allowed protocols (ldap, ldaps) or blacklist validation logic, typically found in request handling or input validation modules
    Affected if code contains protocol blacklist that includes ldap:// and ldaps:// but lacks dns://
  3. Identify endpoints accepting URL input
    Review DataEase configuration or API endpoints that accept URLs as input parameters, particularly those involved in integration or external resource connections
    Affected if the system accepts user-supplied URLs in any parameter and the version is below 2.10.15
  4. Verify dns:// protocol handling
    If you have access to testing capabilities, send a test request containing a dns:// URL to identified endpoints and observe if DNS resolution is triggered (do not use this step if it could cause unintended side effects)
    Affected if DNS queries are performed in response to dns:// protocol URLs

You are affected if DataEase version is below 2.10.15 and the system accepts external URL input that could trigger the unblocked dns:// protocol.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.10.15 or later
Fixed in 2.10.15
Vendor patch github.com →
Interim mitigation

Upgrade to DataEase version 2.10.15 or later, which includes dns:// in the protocol blacklist. Alternatively, implement network-level filtering to block dns:// protocol requests.

Recommended fix High confidence

2.10.15

  1. 1. Backup your current Dataease installation and database
  2. 2. Download Dataease version 2.10.15 from the official release repository
  3. 3. Stop the running Dataease service
  4. 4. Upgrade to version 2.10.15 following the standard upgrade documentation
  5. 5. Verify the upgrade was successful by checking the Dataease version
  6. 6. Restart the Dataease service
  7. 7. Test that the dns:// protocol is now properly blocked and LDAP filtering still works
Caveat Standard upgrade risks apply - test in staging environment before production deployment

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Dataease Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,920
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,072.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-64163 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-64163 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data