# CVE-2024-56511: DataEase - Authentication Bypass

> Live exploitation tracking for CVE-2024-56511 by the CrowdSec Live Exploit Tracker, built from real-world attack data crowdsourced from CrowdSec's global network.

Page: https://tracker.crowdsec.net/cves/CVE-2024-56511

## Key facts

- **Exploitation phase:** Limited Exploitation. The vulnerability is known but shows very limited attacker interest or exploitation activity.
- **CVSS score:** 9.3
- **Public exploit available:** Yes
- **Affected products:** DataEase
- **Weaknesses:** CWE-289 (Authentication Bypass by Alternate Name)
- **Tags:** web_application, java

## Description

DataEase is an open source data visualization analysis tool. Prior to 2.10.4, there is a flaw in the authentication in the io.dataease.auth.filter.TokenFilter class, which can be bypassed and cause the risk of unauthorized access. In the io.dataease.auth.filter.TokenFilter class, ”request.getRequestURI“ is used to obtain the request URL, and it is passed to the "WhitelistUtils.match" method to determine whether the URL request is an interface that does not require authentication. The "match" method filters semicolons, but this is not enough. When users set "server.servlet.context-path" when deploying products, there is still a risk of being bypassed, which can be bypassed by any whitelist prefix /geo/../context-path/. The vulnerability has been fixed in v2.10.4.

## CrowdSec analysis

[CVE-2024-56511](https://euvd.enisa.europa.eu/vulnerability/CVE-2024-56511) is a critical authentication bypass vulnerability in DataEase versions before 2.10.4. Attackers can exploit URL path manipulation involving configured context paths to evade whitelist-based authentication checks and access protected interfaces without credentials, potentially leading to unauthorized data access, modification, or full application compromise.

CrowdSec has been tracking this vulnerability and its exploits since 3rd of August 2026.

CrowdSec network observations suggest that most exploitation of CVE-2024-56511 involves focused reconnaissance to identify viable targets. Attackers typically tailor their campaigns based on system exposure and configuration. It is unlikely that a given attack is accidental.
CrowdSec network telemetry also shows that exploitation of CVE-2024-56511 has significantly declined over the past week. Attack volumes are well below the long-term average, suggesting attackers are rapidly losing interest. The vulnerability appears to be falling out of active use across most threat landscapes.

Attackers exploit the authentication bypass by requesting protected DataEase endpoints with a whitelisted prefix followed by `../`, such as `/geo/../de2api/datasource/types`. Detection should focus on traversal patterns targeting `/de2api/`, particularly datasource, user-management, dashboard, and export endpoints, alongside unexpected unauthenticated JSON responses.

## Timeline

- 2025-01-10: CVE Published. CVE-2024-56511 is published to NVD.
- 2026-08-03: Rule Released. CrowdSec releases a rule to detect CVE-2024-56511 exploitation attempts against the CrowdSec Network.
- 2026-08-19: CrowdSec First Seen. CrowdSec observes in-the-wild exploitation of CVE-2024-56511 for the first time.

## References

- https://github.com/dataease/dataease/security/advisories/GHSA-9f69-p73j-m73x
- https://github.com/projectdiscovery/nuclei-templates/blob/main/http/cves/2024/CVE-2024-56511.yaml

## Live exploitation data

The [Live Exploit Tracker page](https://tracker.crowdsec.net/cves/CVE-2024-56511) follows observed exploitation activity for CVE-2024-56511. [Request an API key](https://tracker.crowdsec.net/request-api-key) for full access to its exploitation timeline, attacking IP addresses and blocklists.