Cyber Posture

CVE-2024-56511

CriticalPublic PoC

Published: 10 January 2025

Published
10 January 2025
Modified
20 February 2025
KEV Added
Patch
CVSS Score 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS Score 0.0027 50.4th percentile
Risk Priority 20 60% EPSS · 20% KEV · 20% CVSS

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.

Security Summary

CVE-2024-56511 is an authentication bypass vulnerability in DataEase, an open source data visualization analysis tool. The flaw affects versions prior to 2.10.4 and resides in the io.dataease.auth.filter.TokenFilter class. This class uses request.getRequestURI to obtain the request URL, which is then passed to the WhitelistUtils.match method to check if the URL requires authentication. While the match method filters semicolons, it is insufficient when users configure server.servlet.context-path during deployment, allowing bypass via crafted paths such as /geo/../context-path/.

The vulnerability has a CVSS v3.1 base score of 9.8 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H), indicating critical severity with no prerequisites for exploitation over the network. Remote attackers without privileges can exploit it by sending requests with manipulated paths that evade the whitelist check, gaining unauthorized access to protected interfaces and potentially compromising confidentiality, integrity, and availability of the application.

The issue has been addressed in DataEase version 2.10.4. Security practitioners should upgrade to this version or later. Additional details are available in the GitHub Security Advisory at https://github.com/dataease/dataease/security/advisories/GHSA-9f69-p73j-m73x.

Details

CWE(s)
CWE-289NVD-CWE-Other

Affected Products

dataease
dataease
≤ 2.10.4

References