dbcve.org
DataeaseApplication

CVE-2025-64164

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, DataEase did not properly filter when establishing JDBC connections to Oracle, resulting in a risk of JNDI injection (Java Naming and Directory Interface injection). 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 contain a JNDI injection vulnerability in the Oracle JDBC connection handling. The application fails to properly validate/filter input when constructing JDBC connection strings to Oracle databases, allowing attackers to manipulate connection parameters to trigger malicious JNDI lookups against attacker-controlled LDAP or RMI servers, potentially achieving remote code execution.

MitigationUpgrade DataEase to version 2.10.15 or later to obtain the fix for proper JDBC connection input filtering. Given the critical CVSS score of 9.8, prioritize this patching in production environments.

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. Check DataEase installed version
    Locate the DataEase installation directory and check the version file or application metadata. Common locations include version.properties, about page in the UI, or docker image tags if containerized.
    Affected if Installed version is 2.10.14 or below (less than 2.10.15)
  2. Identify Oracle JDBC datasource configuration
    Search for Oracle JDBC connection configuration files in the DataEase deployment. Look for files containing oracle, jdbc, datasource, or connection in XML, YAML, or properties configuration files.
    Affected if Oracle JDBC datasource is configured and in use
  3. Inspect Oracle connection string parameters
    Examine the Oracle JDBC connection configuration for the datasource. Look for connection string construction that may include user-controlled parameters, particularly in connection properties or URL parameters.
    Affected if Connection parameters can be manipulated or include unsanitized user input
  4. Review datasource creation endpoints
    Check API endpoints or UI forms used to create new Oracle database connections. Examine how connection string parameters are handled and whether input validation exists before constructing the JDBC connection URL.
    Affected if User-supplied values in connection parameters are not validated/sanitized before JDBC URL construction

A system is affected if it runs DataEase version 2.10.14 or below AND has Oracle JDBC database connections configured or creatable.

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 DataEase to version 2.10.15 or later to obtain the fix for proper JDBC connection input filtering. Given the critical CVSS score of 9.8, prioritize this patching in production environments.

Recommended fix High confidence

2.10.15

  1. Backup your existing Dataease installation and database
  2. Pull or download the fixed version 2.10.15 from the official Dataease repository or release channel
  3. Stop the currently running Dataease service
  4. Deploy version 2.10.15 to your environment
  5. Start the Dataease service and verify it is running correctly
  6. Test JDBC connectivity to Oracle databases to confirm the fix is applied
Caveat Review the 2.10.15 release notes for any configuration or feature changes before upgrading

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

Fix this in Dataease Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-64164 — 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-64164 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