dbcve.org
DataeaseApplication

CVE-2025-57773

CRITICAL · 9.8 CVSS v3.1 Published 2025-08-25
Fix available
A fix is available. Upgrade to 2.10.12 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 business intelligence and data visualization tool. Prior to version 2.10.12, because DB2 parameters are not filtered, a JNDI injection attack can be directly launched. JNDI triggers an AspectJWeaver deserialization attack, writing to various files. This vulnerability requires commons-collections 4.x and aspectjweaver-1.9.22.jar. The vulnerability has been fixed in version 2.10.12.

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 prior to 2.10.12 contain a JNDI injection vulnerability in DB2 parameter handling. Attackers can exploit unfiltered DB2 parameters to trigger a JNDI lookup that cascades into an AspectJWeaver deserialization attack, enabling remote code execution through file writes. The exploit requires commons-collections 4.x and aspectjweaver-1.9.22.jar dependencies to be present in the classpath.

MitigationUpgrade DataEase to version 2.10.12 or later to remediate this vulnerability. If immediate upgrade is not possible, consider disabling or restricting DB2 datasource connections and monitoring for suspicious JNDI lookup patterns.

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

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. Determine DataEase installed version
    Check the version file or startup logs. Common locations: /opt/dataease/version, docker container labels, or look for version strings in dataease-backend.jar or conf/application.yml
    Affected if Installed version is earlier than 2.10.12 (e.g., 2.10.11, 2.10.10, older releases)
  2. Identify if DB2 datasource is configured
    Search configuration files for DB2 connection settings. Check dataease/conf/application.yml, dataease/conf/application-druid.yml, or database connection configuration files for jdbc DB2 driver entries or db2-related connection URLs
    Affected if A DB2 JDBC datasource is configured and enabled in the DataEase configuration
  3. Check for vulnerable JAR dependencies in classpath
    Examine the DataEase lib or lib/ext directories, or inspect the classpath from running process using 'jcmd <pid> VM.system_properties' or by listing files in the deployment. Look for commons-collections4*.jar and aspectjweaver-1.9.22.jar
    Affected if Both commons-collections4 (4.x) and aspectjweaver-1.9.22.jar are present in the classpath

The environment is affected if running DataEase version below 2.10.12 with DB2 datasource enabled and both commons-collections4 and aspectjweaver-1.9.22.jar present in the classpath, as all conditions are required for the full exploit chain.

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

Upgrade DataEase to version 2.10.12 or later to remediate this vulnerability. If immediate upgrade is not possible, consider disabling or restricting DB2 datasource connections and monitoring for suspicious JNDI lookup patterns.

Recommended fix High confidence

2.10.12

  1. Stop the Dataease service
  2. Backup the current Dataease installation and database
  3. Upgrade Dataease to version 2.10.12 or later
  4. Restart the Dataease service
  5. Verify the version after startup to confirm the patch is applied
  6. Test DB2 connections to ensure functionality is maintained

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

Fix this in Dataease Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,380
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,808.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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