CVE-2024-55953 Dataease Mysql JDBC Connection Parameters Not Verified Leads to Deserialization and Arbitrary File Read Vulnerability

High 8.6 Published 18 Dec 2024 Updated 18 Dec 2024

Authenticated attackers can exploit unfiltered JDBC parameters to deserialize arbitrary files, leading to data disclosure and potential code execution.

Exploited in the wild: Not known
Login needed: Any signed-in user
Attackable: Over the internet
Victim action needed: Not needed
Fix: None listed

What is CVE-2024-55953?

CVE-2024-55953 is a high-severity unsafe deserialization vulnerability in Dataease Dataease, published on 18 Dec 2024. Any signed-in user can exploit it over the network, with no action from the victim.

Official description

DataEase is an open source business analytics tool. Authenticated users can read and deserialize arbitrary files through the background JDBC connection. When constructing the jdbc connection string, the parameters are not filtered. This vulnerability has been fixed in v1.18.27. Users are advised to upgrade. There are no known workarounds for this vulnerability.

Weakness: CWE-89

Which versions are affected by CVE-2024-55953?

It affects 1 product.

Products include Dataease Dataease.

How do I fix CVE-2024-55953?

No fix has been published for CVE-2024-55953 yet. Limit exposure of the affected software until one is available.

Upgrade, and only deserialise data from trusted sources or with an allow-list of types. More about Unsafe deserialization.

Is CVE-2024-55953 being exploited?

There is no known exploitation of CVE-2024-55953 in the wild and no public exploit code.

All Dataease Dataease vulnerabilities

Sources

Also known as GHSA-mrf3-9q84-rcmf.