Crítica

MySQL JDBC deserialization vulnerability

Publicada: 18.10.2022
Actualizado: 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

Software afectado

Haz clic en una tecnología para ver todas sus vulnerabilidades.

Plataforma	Paquete	Versiones vulnerables	Corregida en
Java / Kotlin (Maven)	io.dataease:dataease-plugin-common	< 1.15.2	1.15.2

Referencias

Puntuación CVSS 9.8/10

Vector CVSS: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Debilidad (CWE): CWE-20, CWE-502
Plataforma: Java / Kotlin (Maven)
Paquete: io.dataease:dataease-plugin-common
Publicada: 18.10.2022
Actualizado: 11.10.2026 11:21

Fuentes y licencias

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

Historial de vulnerabilidades: io.dataease:dataease-plugin-common

Todas las vulnerabilidades publicadas de este paquete (Java / Kotlin (Maven)), de la más reciente a la más antigua. Muestra si es un fallo aislado o un paquete que hay que vigilar.

Entradas en total: 7
Primera → última: 07.2022 09.2023
Sin corrección: 1
Explotada en ataques: 0

Distribución por gravedad

Crítica 3
Alta 3
Media 1

Divulgaciones por año

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

01.09.2023

DataEase vulnerable to SQL injection

Alta · 7.5 CVE-2023-40771 <= 1.18.9 sin corrección
02.06.2023

DataEase API interface has IDOR vulnerability

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

MySQL JDBC deserialization vulnerability esta entrada

Crítica · 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

Crítica · 9.8 CVE-2022-34113 < 1.11.2 1.11.2
23.07.2022

Dataease v1.11.1 SQL Injection via parameter dataSourceId

Crítica · 9.8 CVE-2022-34115 < 1.11.2 1.11.2
23.07.2022

SQL Injection found in Dataease

Alta · 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

Media · 6.5 CVE-2022-34112 < 1.11.2 1.11.2

Identifica las vulnerabilidades de tu aplicación

Con la integración de DockRay y el inventario de software activado, DockRay compara las versiones notificadas de los componentes con las vulnerabilidades conocidas y avisa de las coincidencias confirmadas. La cobertura depende de la tecnología compatible y de los avisos disponibles.

Conectar tu aplicación