Critical

MySQL JDBC deserialization vulnerability

Disclosed: 18.10.2022
Updated: 11.10.2026 11:21

Impact

In Dataease, the Mysql data source in the data source function can customize the JDBC connection parameters and the Mysql server target to be connected. 6fc8d5c539807157ee471464b184ab66

In backend/src/main/java/io/dataease/provider/datasource/JdbcProvider.java, MysqlConfiguration class don't filter any parameters, directly concat user input.

java

@Getter
@Setter
public class MysqlConfiguration extends JdbcConfiguration {

    private String driver = "com.mysql.jdbc.Driver";
    private String extraParams = "characterEncoding=UTF-8&connectTimeout=5000&useSSL=false&allowPublicKeyRetrieval=true&zeroDateTimeBehavior=convertToNull";

    public String getJdbc() {
        if(StringUtils.isEmpty(extraParams.trim())){
            return "jdbc:mysql://HOSTNAME:PORT/DATABASE"
                    .replace("HOSTNAME", getHost().trim())
                    .replace("PORT", getPort().toString().trim())
                    .replace("DATABASE", getDataBase().trim());
        }else {
            return "jdbc:mysql://HOSTNAME:PORT/DATABASE?EXTRA_PARAMS"
                    .replace("HOSTNAME", getHost().trim())
                    .replace("PORT", getPort().toString().trim())
                    .replace("DATABASE", getDataBase().trim())
                    .replace("EXTRA_PARAMS", getExtraParams().trim());
        }
    }
}

So, if the attack add some parameters in JDBC url, and connect to evil mysql server, he can trigger the mysql jdbc deserialization vulnerability, and eventually the attacker can execute through the deserialization vulnerability system commands and obtain server privileges.

Affected versions: < 1.15.2

Patches

The vulnerability has been fixed in v1.15.2. https://github.com/dataease/dataease/blob/6c3a011955c5c753ffd616d030bea5db4793c51c/backend/src/main/java/io/dataease/dto/datasource/MysqlConfiguration.java#L19 the MysqlConfiguration class use illegalParameters filter illegal parameters to fix this vulnerability.

@Getter
@Setter
public class MysqlConfiguration extends JdbcConfiguration {

    private String driver = "com.mysql.jdbc.Driver";
    private String extraParams = "characterEncoding=UTF-8&connectTimeout=5000&useSSL=false&allowPublicKeyRetrieval=true&zeroDateTimeBehavior=convertToNull";
    private List<String> illegalParameters = Arrays.asList("autoDeserialize", "queryInterceptors", "statementInterceptors", "detectCustomCollations");

    public String getJdbc() {
        if (StringUtils.isEmpty(extraParams.trim())) {
            return "jdbc:mysql://HOSTNAME:PORT/DATABASE"
                    .replace("HOSTNAME", getHost().trim())
                    .replace("PORT", getPort().toString().trim())
                    .replace("DATABASE", getDataBase().trim());
        } else {
            for (String illegalParameter : illegalParameters) {
                if (getExtraParams().contains(illegalParameter)) {
                    throw new RuntimeException("Illegal parameter: " + illegalParameter);
                }
            }

            return "jdbc:mysql://HOSTNAME:PORT/DATABASE?EXTRA_PARAMS"
                    .replace("HOSTNAME", getHost().trim())
                    .replace("PORT", getPort().toString().trim())
                    .replace("DATABASE", getDataBase().trim())
                    .replace("EXTRA_PARAMS", getExtraParams().trim());
        }
    }
}

Workarounds

It is recommended to upgrade the version to v1.15.2.

For more information

If you have any questions or comments about this advisory:

Open an issue in https://github.com/dataease/dataease
Email us at wei@fit2cloud.com

Affected software

Click a technology to see all vulnerabilities affecting it.

Platform	Package	Vulnerable versions	Fixed in
Java / Kotlin (Maven)	io.dataease:dataease-plugin-common	< 1.15.2	1.15.2

References

CVSS score 9.8/10

CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Weakness (CWE): CWE-20, CWE-502
Platform: Java / Kotlin (Maven)
Package: io.dataease:dataease-plugin-common
Disclosed: 18.10.2022
Updated: 11.10.2026 11:21

Sources and licenses

OSV / GitHub Advisory Database - GHSA-q4qq-jhjv-7rh2 - CC BY 4.0

Vulnerability history: io.dataease:dataease-plugin-common

All published vulnerabilities of this package (Java / Kotlin (Maven)), newest first. Shows whether this is a one-off slip or a package that needs watching.

Total entries: 7
First → latest: 07.2022 09.2023
Without a fix: 1
Exploited in attacks: 0

Severity breakdown

Critical 3
High 3
Medium 1

Disclosures per year

2022: 5
2023: 2
2024: 0
2025: 0
2026: 0

01.09.2023

DataEase vulnerable to SQL injection

High · 7.5 CVE-2023-40771 <= 1.18.9 no fix
02.06.2023

DataEase API interface has IDOR vulnerability

High · 8.1 CVE-2023-32310 < 1.18.7 1.18.7
18.10.2022

MySQL JDBC deserialization vulnerability this entry

Critical · 9.8 CVE-2022-39312 < 1.15.2 1.15.2
23.07.2022

Dataease before 1.11.2 allows arbitrary code execution via crafter plugin

Critical · 9.8 CVE-2022-34113 < 1.11.2 1.11.2
23.07.2022

Dataease v1.11.1 SQL Injection via parameter dataSourceId

Critical · 9.8 CVE-2022-34115 < 1.11.2 1.11.2
23.07.2022

SQL Injection found in Dataease

High · 8.8 CVE-2022-34114 < 1.11.2 1.11.2
23.07.2022

Dataease before 1.11.2 access control issue allows attackers to arbitrarily uninstall plugin

Medium · 6.5 CVE-2022-34112 < 1.11.2 1.11.2

Know which vulnerabilities affect your application

With the DockRay integration and software inventory enabled, DockRay checks reported component versions against known vulnerabilities and notifies you about confirmed matches. Coverage depends on the supported technology and available advisory data.

Connect your application