Dataease up to 1.18.14/2.2.x Mysql.java deserialization
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.4 | $0-$5k | 0.00 |
Summary
A vulnerability marked as critical has been reported in Dataease up to 1.18.14/2.2.x. This vulnerability affects unknown code of the file core/core-backend/src/main/java/io/dataease/datasource/type/Mysql.java. Performing a manipulation results in deserialization. This vulnerability is known as CVE-2024-23328. Remote exploitation of the attack is possible. No exploit is available. It is suggested to upgrade the affected component.
Details
A vulnerability classified as critical has been found in Dataease up to 1.18.14/2.2.x. This affects an unknown code of the file core/core-backend/src/main/java/io/dataease/datasource/type/Mysql.java. 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. A deserialization vulnerability exists in the DataEase datasource, which can be exploited to execute arbitrary code. The location of the vulnerability code is `core/core-backend/src/main/java/io/dataease/datasource/type/Mysql.java.` The blacklist of mysql jdbc attacks can be bypassed and attackers can further exploit it for deserialized execution or reading arbitrary files. This vulnerability is patched in 1.18.15 and 2.3.0.
The weakness was published 02/01/2024. The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2024-23328 since 01/15/2024. Technical details are known, but no exploit is available.
Upgrading to version 1.18.15 or 2.3.0 eliminates this vulnerability.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Name
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
- 2.0
- 2.1
- 2.2
License
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 8.5VulDB Meta Temp Score: 8.4
VulDB Base Score: 7.3
VulDB Temp Score: 7.0
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 9.1
NVD Vector: 🔍
CNA Base Score: 9.1
CNA Vector: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
Exploiting
Class: DeserializationCWE: CWE-502 / CWE-20
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: Dataease 1.18.15/2.3.0
Patch: github.com
Timeline
01/15/2024 🔍02/01/2024 🔍
02/01/2024 🔍
01/09/2025 🔍
Sources
Product: github.comAdvisory: 4128adf5fc4592b55fa1722a53b178967545d46a
Status: Confirmed
CVE: CVE-2024-23328 (🔍)
GCVE (CVE): GCVE-0-2024-23328
GCVE (VulDB): GCVE-100-252585
Entry
Created: 02/01/2024 17:36Updated: 01/09/2025 00:11
Changes: 02/01/2024 17:36 (47), 02/24/2024 09:27 (2), 01/09/2025 00:11 (27)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.