CVE-2022-39312: Dataease Mysql Data Source JDBC Connection Parameters Not Verified Leads to Deserialization Vulnerability
Dataease is an open source data visualization analysis tool. Dataease prior to 1.15.2 has a deserialization vulnerability. 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. In backend/src/main/java/io/dataease/provider/datasource/JdbcProvider.java, the MysqlConfiguration class does not filter any parameters. If an attacker adds some parameters to a JDBC url and connects to a malicious mysql server, the attacker can trigger the mysql jdbc deserialization vulnerability. Through the deserialization vulnerability, the attacker can execute system commands and obtain server privileges. Version 1.15.2 contains a patch for this issue.
Affected Software
Remediation
Patch Available
Event History
Frequently Asked Questions
What is CVE-2022-39312?
CVE-2022-39312 is a deserialization vulnerability in Dataease prior to version 1.15.2.
What is the severity of CVE-2022-39312?
CVE-2022-39312 has a severity level of 9.8, which is considered critical.
How can the Dataease vulnerability be exploited?
The Dataease vulnerability can be exploited by malicious actors using deserialization to execute arbitrary code.
Is there a fix available for CVE-2022-39312?
Yes, the fix for CVE-2022-39312 is available in Dataease version 1.15.2.
Where can I find more information about CVE-2022-39312?
More information about CVE-2022-39312 can be found in the references provided: [GitHub Commit](https://github.com/dataease/dataease/commit/956ee2d6c9e81349a60aef435efc046888e10a6d), [GitHub Pull Request](https://github.com/dataease/dataease/pull/3328), [Dataease Releases](https://github.com/dataease/dataease/releases/tag/v1.15.2).