dbcve.org
DataeaseApplication

CVE-2025-53004

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

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 business intelligence and data visualization tool. Prior to version 2.10.11, there is a bypass vulnerability in Dataease's Redshift Data Source JDBC Connection Parameters. The sslfactory and sslfactoryarg parameters could trigger a bypass vulnerability. This issue has been patched in version 2.10.11.

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 · moderate confidence

A security bypass vulnerability in DataEase's Redshift data source JDBC connection parameters (sslfactory and sslfactoryarg) allows attackers to potentially circumvent SSL/TLS verification or authentication mechanisms through malicious connection string configurations.

MitigationUpgrade DataEase to version 2.10.11 or later. Until patched, restrict data source configuration permissions to trusted administrators and audit existing Redshift connections for suspicious parameters.

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

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 version
    Navigate to the DataEase admin panel or check the installation directory for the version file. The version is typically displayed in the UI footer or can be found in the application.properties or version manifest file.
    Affected if The installed version is lower than 2.10.11
  2. Identify configured Redshift data sources
    In the DataEase UI, go to Data Sources or Security Settings menu. Look for data sources configured with type Redshift or Amazon Redshift. Alternatively, query the application's database for records in the data_source table where type contains 'redshift'.
    Affected if Any Redshift data source is configured and active
  3. Inspect JDBC connection string parameters
    View the details of each Redshift data source configuration. Examine the JDBC connection string or additional parameters field for the presence of 'sslfactory' or 'sslfactoryarg' parameters.
    Affected if The connection parameters include sslfactory or sslfactoryarg with values that could disable SSL verification or point to custom trust stores

You are affected if running DataEase version below 2.10.11 AND have Redshift data sources configured with sslfactory or sslfactoryarg parameters in the JDBC connection configuration.

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.11 or later
Fixed in 2.10.11
Interim mitigation

Upgrade DataEase to version 2.10.11 or later. Until patched, restrict data source configuration permissions to trusted administrators and audit existing Redshift connections for suspicious parameters.

Recommended fix High confidence

2.10.11

  1. Backup your current DataEase installation and database before upgrading
  2. Download DataEase version 2.10.11 or later from the official GitHub repository or release channel
  3. Stop the running DataEase service
  4. Install the upgraded version following standard DataEase upgrade procedures
  5. Restart the DataEase service
  6. Verify the installation by logging into the DataEase admin interface
  7. Test that Redshift data source connections work properly with the updated version

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-53004 — 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-53004 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