Perses is utilized by DevOps teams and software developers to monitor and manage performance metrics through dashboards. It provides a mechanism to create and display visualizations of complex data in real-time. The software is generally employed in production environments to automate the visualization process and to enhance operational efficiency. With ease of deployment and integration capabilities, it has gained popularity in enterprises focusing on continuous delivery and deployment models. Its open-source nature encourages contributions and customization by a wide community. Collaborative features allow cross-functional teams to access, share, and analyze data insights seamlessly.
Path Traversal vulnerabilities allow attackers to access files and directories that are stored outside the web root folder. In the case of Perses, this vulnerability arises because the project query parameter is merged into the resource Query struct without adequate validation. This enables intruders to read arbitrary files on the system, given that authentication is not enforced by default. Such vulnerabilities can undermine the confidentiality and integrity of the system by exposing critical files and data, compromising sensitive information.
The vulnerability is particularly harmful as it allows attackers to exploit endpoints in the Perses application that are not adequately secured. The vulnerable endpoint accepts inputs that are susceptible to path traversal attacks, allowing unsanctioned calls to access unintended file paths. The project parameter is part of the request to the `/api/v1/dashboards` endpoint, which the attacker manipulates to traverse directory structures and read unauthorized file types that are accessible to the running Perses process. This poses a potential risk as these files could include configuration settings, sensitive data, and application secrets.
If exploited, the path traversal can grant unauthorized access to sensitive files located on the server. Malicious actors might extract information such as user credentials, API keys, and database configuration from the misconfigured systems. Utilizing this information, they are able to further penetrate the internal network or manipulate the service's operations, potentially executing malicious directives. The implications of this breach stretch to allow unauthorized manipulation of stored data, unauthorized configuration changes, and access to secret resources.
REFERENCES
- Upgrade Perses to version 0.54.0-rc.0 or later.
- Switch to using an SQL database instead of the file system database to mitigate unauthorized file access.
- Enable authentication for all deployments to ensure that only authorized personnel have access to critical operations and data.
- Regularly audit and monitor access logs to identify unauthorized access patterns.
- Implement a comprehensive security policy to govern file system and access management.
Get AI-powered remediation steps tailored to your asset.
Try AI Solutions →