CVE-2024-56511 Security Vulnerability & Exploit Details

CVE-2024-56511
Vulnerability Scoring

9.8

/10

Critical Risk

As a catastrophic security flaw, CVE-2024-56511 has severe implications, demanding immediate intervention.

Attack Complexity Details

Attack Complexity: Low
Exploits can be performed without significant complexity or special conditions.
Attack Vector: Network
Vulnerability is exploitable over a network without physical access.
Privileges Required: None
No privileges are required for exploitation.
Scope: Unchanged
Exploit remains within the originally vulnerable component.
User Interaction: None
No user interaction is necessary for exploitation.

CVE-2024-56511 Details

Status: Analyzed

Last updated: 🕓 20 Feb 2025, 16:26 UTC
Originally published on: 🕓 10 Jan 2025, 16:15 UTC

Time between publication and last update: 41 days

CVSS Release: version 3

CVSS3 Source

nvd@nist.gov

CVSS3 Type

Primary

CVSS3 Vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

CVE-2024-56511 Vulnerability Summary

CVE-2024-56511: 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.

Assessing the Risk of CVE-2024-56511

Access Complexity Graph

The exploitability of CVE-2024-56511 depends on two key factors: attack complexity (the level of effort required to execute an exploit) and privileges required (the access level an attacker needs).

Exploitability Analysis for CVE-2024-56511

With low attack complexity and no required privileges, CVE-2024-56511 is an easy target for cybercriminals. Organizations should prioritize immediate mitigation measures to prevent unauthorized access and data breaches.

Understanding AC and PR

A lower complexity and fewer privilege requirements make exploitation easier. Security teams should evaluate these aspects to determine the urgency of mitigation strategies, such as patch management and access control policies.

Attack Complexity (AC) measures the difficulty in executing an exploit. A high AC means that specific conditions must be met, making an attack more challenging, while a low AC means the vulnerability can be exploited with minimal effort.

Privileges Required (PR) determine the level of system access necessary for an attack. Vulnerabilities requiring no privileges are more accessible to attackers, whereas high privilege requirements limit exploitation to authorized users with elevated access.

CVSS Score Breakdown Chart

Above is the CVSS Sub-score Breakdown for CVE-2024-56511, illustrating how Base, Impact, and Exploitability factors combine to form the overall severity rating. A higher sub-score typically indicates a more severe or easier-to-exploit vulnerability.

CIA Impact Analysis

Below is the Impact Analysis for CVE-2024-56511, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.

Confidentiality: High
Exploiting CVE-2024-56511 can result in unauthorized access to sensitive data, severely compromising data privacy.
Integrity: High
CVE-2024-56511 could allow unauthorized modifications to data, potentially affecting system reliability and trust.
Availability: High
CVE-2024-56511 can disrupt system operations, potentially causing complete denial of service (DoS).

Exploit Prediction Scoring System (EPSS)

The EPSS score estimates the probability that this vulnerability will be exploited in the near future.

EPSS Score: 0.106% (probability of exploit)

EPSS Percentile: 45.11% (lower percentile = lower relative risk)
This vulnerability is less risky than approximately 54.89% of others.

CVE-2024-56511 References

External References

https://github.com/dataease/dataease/security/advisories/GHSA-9f69-p73j-m73x

CWE Common Weakness Enumeration

NVD-CWE-Other

Vulnerable Configurations

cpe:2.3:a:dataease:dataease:-:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:-:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:1.0.0:-:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:1.0.0:-:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:1.0.0:rc1:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:1.0.0:rc1:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:1.0.0:rc2:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:1.0.0:rc2:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:1.0.1:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:1.0.1:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:1.0.2:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:1.0.2:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:1.1.0:-:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:1.1.0:-:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:1.1.0:rc1:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:1.1.0:rc1:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:1.1.0:rc2:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:1.1.0:rc2:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:1.1.1:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:1.1.1:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:1.2.0:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:1.2.0:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:1.2.1:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:1.2.1:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:1.2.2:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:1.2.2:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:1.2.3:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:1.2.3:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:1.3.0:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:1.3.0:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:1.4.0:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:1.4.0:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:1.4.1:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:1.4.1:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:1.5.0:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:1.5.0:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:1.5.1:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:1.5.1:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:1.5.2:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:1.5.2:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:1.6.0:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:1.6.0:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:1.6.1:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:1.6.1:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:1.6.2:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:1.6.2:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:1.7.0:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:1.7.0:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:1.8.0:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:1.8.0:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:1.9.0:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:1.9.0:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:1.9.1:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:1.9.1:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:1.10.0:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:1.10.0:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:1.11.0:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:1.11.0:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:1.11.1:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:1.11.1:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:1.11.2:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:1.11.2:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:1.11.3:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:1.11.3:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:1.12.0:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:1.12.0:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:1.13.0:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:1.13.0:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:1.13.1:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:1.13.1:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:1.14.0:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:1.14.0:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:1.15.0:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:1.15.0:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:1.15.1:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:1.15.1:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:1.15.2:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:1.15.2:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:1.15.3:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:1.15.3:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:1.15.4:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:1.15.4:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:1.16.0:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:1.16.0:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:1.16.1:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:1.16.1:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:1.17.0:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:1.17.0:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:1.17.1:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:1.17.1:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:1.18.0:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:1.18.0:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:1.18.1:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:1.18.1:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:1.18.2:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:1.18.2:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:1.18.3:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:1.18.3:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:1.18.4:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:1.18.4:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:1.18.5:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:1.18.5:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:1.18.6:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:1.18.6:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:1.18.7:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:1.18.7:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:1.18.8:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:1.18.8:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:1.18.9:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:1.18.9:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:1.18.10:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:1.18.10:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:1.18.11:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:1.18.11:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:1.18.12:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:1.18.12:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:1.18.13:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:1.18.13:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:1.18.14:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:1.18.14:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:1.18.15:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:1.18.15:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:1.18.16:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:1.18.16:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:1.18.17:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:1.18.17:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:1.18.18:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:1.18.18:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:1.18.19:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:1.18.19:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:1.18.20:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:1.18.20:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:1.18.21:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:1.18.21:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:1.18.22:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:1.18.22:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:1.18.23:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:1.18.23:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:1.18.24:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:1.18.24:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:1.18.25:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:1.18.25:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:1.18.26:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:1.18.26:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:1.18.27:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:1.18.27:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:2.0.0:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:2.0.0:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:2.1.0:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:2.1.0:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:2.2.0:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:2.2.0:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:2.3.0:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:2.3.0:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:2.4.0:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:2.4.0:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:2.4.1:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:2.4.1:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:2.5.0:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:2.5.0:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:2.6.0:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:2.6.0:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:2.6.1:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:2.6.1:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:2.7.0:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:2.7.0:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:2.7.1:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:2.7.1:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:2.8.0:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:2.8.0:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:2.8.1:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:2.8.1:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:2.9.0:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:2.9.0:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:2.10.0:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:2.10.0:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:2.10.1:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:2.10.1:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:2.10.2:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:2.10.2:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:2.10.3:*:*:*:*:*:*:*
cpe:2.3:a:dataease:dataease:2.10.3:*:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2024-56511: Combat Critical CVE Threats

Stay updated with real-time CVE vulnerabilities and take action to secure your systems. Enhance your cybersecurity posture with the latest threat intelligence and mitigation techniques. Develop the skills necessary to defend against CVEs and secure critical infrastructures. Join the top cybersecurity professionals safeguarding today's infrastructures.

Other 5 Recently Published CVEs Vulnerabilities

CVE-2025-27636 – Bypass/Injection vulnerability in Apache Camel. This issue affects Apache Camel: from 4.10.0 through <= 4.10.1, from 4.8.0 through <= 4.8.4, from ...
CVE-2025-2121 – A vulnerability classified as critical has been found in Thinkware Car Dashcam F800 Pro up to 20250226. Affected is an unknown function of the comp...
CVE-2025-2120 – A vulnerability was found in Thinkware Car Dashcam F800 Pro up to 20250226. It has been rated as problematic. This issue affects some unknown proce...
CVE-2025-2119 – A vulnerability was found in Thinkware Car Dashcam F800 Pro up to 20250226. It has been declared as problematic. This vulnerability affects unknown...
CVE-2025-2118 – A vulnerability was found in Quantico Tecnologia PRMV 6.48. It has been classified as critical. This affects an unknown part of the file /admin/log...

CVE-2024-56511 Vulnerability Scoring