DataEase < 2.10.4 - Authentication Bypass via Whitelist Path Traversal
DataEase versions up to and including 2.10.3 contain an authentication bypass in `io.dataease.auth.filter.TokenFilter`. The filter passes the raw, unnormalized request URI to `WhitelistUtils.match()`, which only checks for whitelisted prefixes such as `/geo/`, `/customGeo/`, `/map/`, `/oauth2/`, and `/websocket` without resolving `..` segments. By prepending a whitelisted prefix and traversing back into the configured `server.servlet.context-path`, an attacker bypasses the filter while Tomcat still routes the request to the genuine, protected controller. This collapses the entire `/de2api` surface (user management, datasources, dashboards, exports) into unauthenticated access. References: https://github.com/dataease/dataease/security/advisories/GHSA-9f69-p73j-m73x https://nvd.nist.gov/vuln/detail/CVE-2024-56511 Remediation: Upgrade to DataEase 2.10.4 or later, which normalizes the request path before whitelist matching.
10 assets checked · domain, subdomain, ipv4