Summary
DataEase versions prior to 2.10.20 are vulnerable to a path traversal issue where the Redshift JDBC driver's IniFile parameter can be manipulated to load attacker-controlled configuration files.
By pointing the IniFile property at arbitrary server-side files, an attacker can inject malicious JDBC properties that may lead to remote code execution when connections are established.
Affected context
This vulnerability appears in DataEase deployments that:
- Use the Redshift JDBC driver from within DataEase
- Allow user-controlled input to influence JDBC URL or connection properties (including
IniFile) - Run with a filesystem layout where attacker-controllable or sensitive files can be referenced as JDBC configuration
The risk is highest in multi-tenant or shared deployments where untrusted users can define or modify data source connection strings or advanced JDBC parameters.
Exploit preconditions
- Attack surface: Data source configuration and JDBC connection setup within DataEase.
- Required access: Ability to create or modify Redshift data source configurations (including JDBC URL parameters or driver properties) inside the application.
- Trigger point: Establishment of a JDBC connection where the Redshift driver resolves the
IniFileproperty or automatically discoversrsjdbc.ini. - Why exploitation is possible: The driver's aggressive configuration discovery and support for an externally specified
IniFiletrust user-controlled file paths without sufficient restriction, enabling path traversal and loading of attacker-controlled configuration files that can alter execution behavior.
Why this happens
The root cause maps to CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') combined with unsafe configuration loading.
The Redshift JDBC driver's getJdbcIniFile logic implements a broad search strategy and accepts arbitrary file paths via the IniFile parameter. DataEase does not adequately constrain or sanitize these paths when they are derived from user-controlled JDBC URLs or properties. As a result, the application allows attackers to direct the driver to read and apply configuration from unintended locations. Because JDBC properties can influence how code is loaded or executed, this unbounded file loading becomes a vehicle for remote code execution.
Potential impact
- Remote code execution in the context of the DataEase server process
- Unauthorized loading of attacker-supplied JDBC configuration files
- Escalation of privileges within the application or host environment
- Access to sensitive data by modifying connection or authentication properties
- Lateral movement to other databases or services reachable via the compromised instance
General mitigation guidance
Effective mitigation generally focuses on constraining file resolution and reducing trust in user-controlled connection properties:
- Restrict which JDBC properties are allowed to be set by end users, and block or ignore
IniFileand similar file-based parameters. - Enforce allowlists for JDBC driver options and validate connection strings against strict schemas.
- Constrain file access by the database connectivity layer to specific, application-controlled directories, avoiding arbitrary filesystem access.
- Run the DataEase service with least-privilege filesystem permissions so that even if a configuration file is loaded, it cannot be placed or modified in powerful locations.
- Centralize and hard-code sensitive JDBC configuration on the server side rather than exposing it for user customization.
How teams detect issues like this
Detection typically involves both configuration review and code-level analysis:
- Review DataEase data source configuration screens and stored metadata for suspicious JDBC URLs or properties, especially those referencing
IniFileor unexpected local file paths. - Implement static or configuration analysis checks that flag use of file-based JDBC properties or unconstrained path parameters in connection logic.
- Add server-side validation and logging for JDBC configuration, alerting on usage of high-risk options (e.g., external configuration file references).
- Use application security testing tools to scan for path traversal and arbitrary file loading patterns around database connection handling.

