CVE-2025-62420

Unknown Unknown - Not Provided

BaseFortify

Publication date: 2025-10-17

Last updated on: 2025-10-24

Assigner: GitHub, Inc.

Description

DataEase is a data visualization and analytics platform. In DataEase versions through 2.10.13, a JDBC driver bypass vulnerability exists in the H2 database connection handler. The getJdbc function in H2.java checks if the jdbcUrl starts with jdbc:h2 but returns a separate jdbc field as the actual connection URL. An attacker can provide a jdbcUrl that starts with jdbc:h2 while supplying a different jdbc field with an arbitrary JDBC driver and connection string. This allows an authenticated attacker to trigger arbitrary JDBC connections with malicious drivers, potentially leading to remote code execution. The vulnerability is fixed in version 2.10.14. No known workarounds exist.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2025-10-17

Last Modified

2025-10-24

Generated

2026-07-06

AI Q&A

2025-10-17

EPSS Evaluated

2026-07-05

NVD

CVE-2025-62420

EUVD

EUVD-2025-34918

Affected Vendors & Products

Vendor	Product	Version / Range
dataease	dataease	to 2.10.14 (exc)

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-502	The product deserializes untrusted data without sufficiently ensuring that the resulting data will be valid.

Attack-Flow Graph

Executive Summary

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.

Impact Analysis

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.

Mitigation Strategies

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.

Hi! I’m here to help you understand CVE-2025-62420. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70