dbcve.org
DataeaseApplication

CVE-2025-58045

CRITICAL · 9.8 CVSS v3.1 Published 2025-09-15
Fix available
A fix is available. Upgrade to 2.10.13 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 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.

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 up to 2.10.12 had incomplete filtering of DB2 JDBC connection string parameters. While a prior patch blacklisted the 'rmi' parameter to mitigate deserialization RCE, the 'ldap' parameter was not filtered, allowing attackers to inject ldap:// URLs in the connection string to trigger SSRF. In newer Java versions, ldap autoDeserialize is disabled by default, preventing RCE but leaving SSRF exploitable.

MitigationUpgrade Dataease to version 2.10.13 or later to receive the complete fix that filters the ldap parameter in DB2 JDBC connection strings.

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.13

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
    Access the Dataease administration panel or check the deployment manifest to find the exact version number running in your environment.
    Affected if The version is below 2.10.13 (any version from earlier releases up to 2.10.12 is affected).
  2. Locate DB2 data source configurations
    Review Dataease data source configuration files or database connection settings in the administration interface to identify any configured DB2 connections.
    Affected if A DB2 JDBC data source is configured and active in the Dataease instance.
  3. Inspect DB2 JDBC connection string parameters
    Examine the DB2 JDBC connection string in the data source configuration. Look for the connection URL used for the DB2 connector, typically found in the data source YAML or properties configuration.
    Affected if The connection string contains any ldap:// parameter injection or if the connection string can be influenced by user-supplied input.
  4. Verify LDAP URL injection capability
    Test whether the DB2 connection string accepts the 'ldap' parameter by attempting to add 'ldap://' to the connection string in a test or staging environment.
    Affected if The system accepts and processes ldap:// URLs in the DB2 JDBC connection string, indicating the ldap parameter is not being filtered.

You are affected if running any Dataease version below 2.10.13 and you have an active DB2 data source that accepts ldap:// parameters in its connection string.

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.13 or later
Fixed in 2.10.13
Vendor patch github.com →
Interim mitigation

Upgrade Dataease to version 2.10.13 or later to receive the complete fix that filters the ldap parameter in DB2 JDBC connection strings.

Recommended fix High confidence

2.10.13

  1. Upgrade Dataease to version 2.10.13 or later to address the SSRF vulnerability in the DB2 JDBC connection string ldap parameter

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

Fix this in Dataease Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,190
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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