DataEase up to 1.18.24 JDBC Connection JdbcProvider.java deserialization

Summaryinfo

A vulnerability was found in DataEase up to 1.18.24. It has been rated as very critical. The affected element is an unknown function of the file backend/src/main/java/io/dataease/provider/datasource/JdbcProvider.java of the component JDBC Connection Handler. Performing a manipulation results in deserialization. This vulnerability is reported as CVE-2024-47074. The attack is possible to be carried out remotely. No exploit exists. Upgrading the affected component is advised.

Detailsinfo

A vulnerability was found in DataEase up to 1.18.24. It has been classified as very critical. This affects an unknown function of the file backend/src/main/java/io/dataease/provider/datasource/JdbcProvider.java of the component JDBC Connection Handler. The manipulation with an unknown input leads to a deserialization vulnerability. CWE is classifying the issue as CWE-502. The product deserializes untrusted data without sufficiently verifying that the resulting data will be valid. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

DataEase is an open source data visualization analysis tool. In Dataease, the PostgreSQL data source in the data source function can customize the JDBC connection parameters and the PG server target to be connected. In backend/src/main/java/io/dataease/provider/datasource/JdbcProvider.java, PgConfiguration class don't filter any parameters, directly concat user input. So, if the attacker adds some parameters in JDBC url, and connect to evil PG server, the attacker can trigger the PG jdbc deserialization vulnerability, and eventually the attacker can execute through the deserialization vulnerability system commands and obtain server privileges. The vulnerability has been fixed in v1.18.25.

The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2024-47074 since 09/17/2024. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details are known, but no exploit is available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 11/13/2024).

Upgrading to version 1.18.25 eliminates this vulnerability. Applying the patch 86eafc4d77f0bbc0eaa7fc58e5076a085257f259 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Name

• DataEase

Version

• 1.18.0
• 1.18.1
• 1.18.2
• 1.18.3
• 1.18.4
• 1.18.5
• 1.18.6
• 1.18.7
• 1.18.8
• 1.18.9
• 1.18.10
• 1.18.11
• 1.18.12
• 1.18.13
• 1.18.14
• 1.18.15
• 1.18.16
• 1.18.17
• 1.18.18
• 1.18.19
• 1.18.20
• 1.18.21
• 1.18.22
• 1.18.23
• 1.18.24

License

• open-source

Website

• Product: https://github.com/dataease/dataease/

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion