CVE-2022-39312 Dataease Mysql Data Source JDBC Connection Parameters Not Verified Leads to Deserialization Vulnerability
Attackers can execute system commands and gain server privileges by exploiting a deserialization flaw in Dataease's MySQL JDBC connection parameters.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2022-39312?
CVE-2022-39312 is a critical unsafe deserialization vulnerability in Dataease Dataease, published on 25 Oct 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
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.
Which versions are affected by CVE-2022-39312?
2 open source packages ship an affected version, including io.dataease:dataease-plugin-common. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
io.dataease:dataease-plugin-common Maven | All versions | 1.15.2 |
io.dataease:dataease-plugin-common Maven | All versions | 1.15.2 |
Products include Dataease Dataease.
How do I fix CVE-2022-39312?
Upgrade io.dataease:dataease-plugin-common to 1.15.2 or later.
Upgrade, and only deserialise data from trusted sources or with an allow-list of types. More about Unsafe deserialization.
Is CVE-2022-39312 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-39312 exists.
Other vulnerabilities in Dataease Dataease
- CVE-2024-57707 Code injection in n/a
- CVE-2024-46997 DataEase's H2 datasource has a remote command execution risk
- CVE-2023-33963 DataEase data source has deserialization vulnerability
- CVE-2023-28437 SQL injection vulnerability due to the keyword blacklist for defending against SQL injection will be bypassed
- CVE-2022-34113 Dataease before 1.11.2 allows arbitrary code execution via crafter plugin
Sources
Also known as GHSA-q4qq-jhjv-7rh2.