CVE-2025-62420
BaseFortify
Publication date: 2025-10-17
Last updated on: 2025-10-24
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| dataease | dataease | to 2.10.14 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-502 | The product deserializes untrusted data without sufficiently ensuring that the resulting data will be valid. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability exists in DataEase versions through 2.10.13 in the H2 database connection handler. The getJdbc function checks if the jdbcUrl starts with jdbc:h2 but then uses a separate jdbc field as the actual connection URL. An attacker who is authenticated can supply a jdbcUrl starting with jdbc:h2 but provide a different jdbc field with an arbitrary JDBC driver and connection string. This allows the attacker to trigger arbitrary JDBC connections using malicious drivers, potentially leading to remote code execution.
How can this vulnerability impact me? :
An authenticated attacker can exploit this vulnerability to execute arbitrary code remotely by supplying malicious JDBC drivers and connection strings. This could lead to unauthorized control over the system running DataEase, potentially compromising data integrity, confidentiality, and availability.
What immediate steps should I take to mitigate this vulnerability?
Upgrade DataEase to version 2.10.14 or later, as this version contains the fix for the JDBC driver bypass vulnerability. No known workarounds exist, so applying the update is the recommended immediate mitigation step.