dbcve.org
JimureportApplication · Jeecg

CVE-2025-10771

CRITICAL · 9.8 CVSS v3.1 Published 2025-09-21
Fix available
A fix is available. Upgrade to after 2.1.2 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
A vulnerability was determined in jeecgboot JimuReport up to 2.1.2. Affected is an unknown function of the file /drag/onlDragDataSource/testConnection of the component DB2 JDBC Handler. Executing manipulation of the argument clientRerouteServerListJNDIName can lead to deserialization. The attack can be executed remotely. The exploit has been publicly disclosed and may be utilized.

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

The JimuReport component in jeecgboot contains a deserialization vulnerability in the DB2 JDBC Handler's testConnection endpoint (/drag/onlDragDataSource/testConnection). The clientRerouteServerListJNDIName parameter is not properly sanitized before deserialization, allowing remote attackers to execute arbitrary code via crafted serialized objects.

MitigationUpgrade JimuReport to a version beyond 2.1.2 that includes the patched DB2 JDBC Handler. If immediate patching is not feasible, disable or restrict network access to the affected /drag/onlDragDataSource/testConnection endpoint.

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
JimureportApplication
Affected:<= 2.1.2

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 if JeecgBoot or JimuReport is deployed
    Locate the Java web application WAR or exploded directory. Check for jeecg-boot or jimureport in file names, class paths, or libraries.
    Affected if The application is a JeecgBoot-based system using the JimuReport module.
  2. Determine the installed JimuReport version
    Search for version information in pom.xml, MANIFEST.MF, or version properties files within the deployed application. Look for files containing 'jimureport' or 'JimuReport' with version numbers.
    Affected if The version is 2.1.2 or lower.
  3. Verify the vulnerable endpoint exists
    Check if the REST endpoint /drag/onlDragDataSource/testConnection is present in the deployed application by examining the compiled classes or examining web.xml URL mappings. This endpoint handles onlDragDataSource connection testing.
    Affected if The endpoint is accessible in the running application.
  4. Check if DB2 JDBC datasource configuration is enabled
    Inspect application configuration files (application.yml, application.properties, or database config files) for DB2 datasource definitions. The vulnerability affects the clientRerouteServerListJNDIName parameter in DB2 JDBC handler configuration.
    Affected if DB2 JDBC datasource with clientRerouteServerListJNDIName parameter support is configured or available.
  5. Confirm network accessibility of the testConnection endpoint
    If the application is running, verify whether the /drag/onlDragDataSource/testConnection endpoint is reachable via HTTP/HTTPS from the network.
    Affected if The endpoint is exposed over the network without authentication or additional access controls.

You are affected if you are running JeecgBoot with JimuReport version 2.1.2 or lower and the /drag/onlDragDataSource/testConnection endpoint is accessible with DB2 JDBC handler configuration enabled.

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 a release after 2.1.2
Interim mitigation

Upgrade JimuReport to a version beyond 2.1.2 that includes the patched DB2 JDBC Handler. If immediate patching is not feasible, disable or restrict network access to the affected /drag/onlDragDataSource/testConnection endpoint.

Recommended fix Moderate confidence

latest version beyond 2.1.2 (check official jeecgboot releases)

  1. 1. Identify all deployments of JimuReport version 2.1.2 or earlier in your environment
  2. 2. Upgrade JimuReport to the latest available version from the official jeecgboot repository (https://github.com/jeecgboot/JimuReport)
  3. 3. After upgrading, verify the /drag/onlDragDataSource/testConnection endpoint is no longer vulnerable by testing with the clientRerouteServerListJNDIName parameter
  4. 4. If immediate upgrade is not possible, restrict network access to the affected endpoint using firewall rules or API gateway filtering
  5. 5. Disable or remove the DB2 JDBC Handler component if not required in your deployment
Caveat Review release notes for any breaking changes between 2.1.2 and the target version before upgrading in production

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

Fix this in Jimureport Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing5.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,790
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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