CVE-2024-52295 DataEase has a forged JWT token vulnerability
Attackers can forge JWT tokens using hardcoded secrets to take over DataEase services and potentially execute code.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2024-52295?
CVE-2024-52295 is a critical vulnerability in Dataease Dataease, published on 13 Nov 2024. 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. Prior to 2.10.2, DataEase allows attackers to forge jwt and take over services. The JWT secret is hardcoded in the code, and the UID and OID are hardcoded. The vulnerability has been fixed in v2.10.2.
Weakness: CWE-798
Which versions are affected by CVE-2024-52295?
It affects 1 product.
Products include Dataease Dataease.
How do I fix CVE-2024-52295?
No fix has been published for CVE-2024-52295 yet. Limit exposure of the affected software until one is available.
Is CVE-2024-52295 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-52295 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-39312 Dataease Mysql Data Source JDBC Connection Parameters Not Verified Leads to Deserialization Vulnerability
Sources
Also known as GHSA-45v9-gfcv-xcq6.