Skip to content
Connect AISign inSign up free
CVE-2022-393129.8CriticalCWE-502

CVE-2022-39312: Dataease Mysql Data Source JDBC Connection Parameters Not Verified Leads to Deserialization Vulnerability

dataease

Affected: dataease · Exploitation: possible (1 to 10%)

Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.

2.0%probability of exploitation in the next 30 days
80th percentile
050100

Higher than 80% of scored CVEs

9.8CriticalCVSS 3.1
LowCrit.

DescriptionCVE.org

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 products1

From the CVE record. A product or version that is not listed is unknown, not unaffected.

  • dataease · dataease< 1.15.2

On the Atlas

Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.

Open the Atlas
Exploitation
Possible (1 to 10%). EPSS between 1% and 10%.
CISA KEV
Not listed
Public check
No public nuclei template
Vendor
dataease
Published
October 2022

CoverageNo articles yet

No CyberSIXT article names CVE-2022-39312 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.

References