# 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.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Nov 2024
- **Updated:** 21 Nov 2024
- **Also known as:** GHSA-45v9-gfcv-xcq6

## 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 (Use of Hard-coded Credentials)

## Which versions are affected by CVE-2024-52295?

It affects 1 product.


Products: 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](https://insights.sbomify.com/CVE-2024-57707/): Code injection in n/a (critical 9.8)
- [CVE-2024-46997](https://insights.sbomify.com/CVE-2024-46997/): DataEase's H2 datasource has a remote command execution risk (critical 9.8)
- [CVE-2023-33963](https://insights.sbomify.com/CVE-2023-33963/): DataEase data source has deserialization vulnerability (critical 9.8)
- [CVE-2023-28437](https://insights.sbomify.com/CVE-2023-28437/): SQL injection vulnerability due to the keyword blacklist for defending against SQL injection will be bypassed (critical 9.8)
- [CVE-2022-39312](https://insights.sbomify.com/CVE-2022-39312/): Dataease Mysql Data Source JDBC Connection Parameters Not Verified Leads to Deserialization Vulnerability (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-52295 and fix it if it is affected.

What it is: 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.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-52295 exists.

Affected product: Dataease Dataease. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-52295/ (Markdown: https://insights.sbomify.com/CVE-2024-52295/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-52295
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-52295
- OSV: https://osv.dev/vulnerability/CVE-2024-52295

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-52295/
Summaries are generated and may contain mistakes; the official description above is the record.