Terence Monteiro

An issue exists in the Report Execution API 'runreports' endpoint where report parameter values are incorporated into the generated SQL query without sufficient validation. This allows an authenticated user with report execution permissions to inject arbitrary SQL through crafted parameter values, potentially leading to unauthorized access to data beyond the intended scope of the report.

An authenticated user with permissions to view clients can exploit a boolean-based SQL Injection in the Client Search API endpoint '/api/v1/clients'. The issue occurs because the `orderBy` and `sortOrder` parameters are concatenated into a SQL query without sufficient validation. This allows for blind boolean-based data extraction and, specifically on MySQL or MariaDB, the disclosure of arbitrary files readable by the database process through the `LOAD FILE()` function.

An authenticated user with permissions to view offices can perform a time-based blind SQL injection via the 'Office Search API' endpoint '/api/v1/offices'. The issue occurs because the `orderBy` request parameter is concatenated into a SQL query without sufficient validation, bypassing the ColumnValidator. This allows the injection of arbitrary SQL, which can be used for data exfiltration. Additionally, because the injected queries block database connections, concurrent exploitation may exhaust the database connection pool, leading to a denial of service.