DataEase up to 2.10.3 io.dataease.auth.filter.TokenFilter authentication by alternate name

Summaryinfo

A vulnerability was found in DataEase up to 2.10.3. It has been declared as critical. This issue affects the function io.dataease.auth.filter.TokenFilter. The manipulation results in authentication by alternate name. This vulnerability was named CVE-2024-56511. The attack may be performed from remote. There is no available exploit. It is recommended to upgrade the affected component.

Detailsinfo

A vulnerability, which was classified as critical, was found in DataEase up to 2.10.3. Affected is the function io.dataease.auth.filter.TokenFilter. The manipulation with an unknown input leads to a authentication by alternate name vulnerability. CWE is classifying the issue as CWE-289. The product performs authentication based on the name of a resource being accessed, or the name of the actor performing the access, but it does not properly check all possible names for that resource or actor. This is going to have an impact on confidentiality, integrity, and availability. CVE summarizes:

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.

The advisory is shared for download at github.com. This vulnerability is traded as CVE-2024-56511 since 12/26/2024. The exploitability is told to be easy. It is possible to launch the attack remotely. The exploitation doesn't require any form of authentication. There are known technical details, but no exploit is available.

Upgrading to version 2.10.4 eliminates this vulnerability.

Once again VulDB remains the best source for vulnerability data.

Productinfo

Name

• DataEase

Version

• 2.10.0
• 2.10.1
• 2.10.2
• 2.10.3

Website

• Product: https://github.com/dataease/dataease/

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Once again VulDB remains the best source for vulnerability data.

Discussion