First published: Tue Oct 25 2022(Updated: )
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.
Credit: security-advisories@github.com
Affected Software | Affected Version | How to fix |
---|---|---|
Dataease | <1.15.2 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2022-39312 is a deserialization vulnerability in Dataease prior to version 1.15.2.
CVE-2022-39312 has a severity level of 9.8, which is considered critical.
The Dataease vulnerability can be exploited by malicious actors using deserialization to execute arbitrary code.
Yes, the fix for CVE-2022-39312 is available in Dataease version 1.15.2.
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).