Mistz1

**Name of the Vulnerable Software and Affected Versions** Rucio versions 1.27.0 through 35.8.4 Rucio versions 38.x through 38.5.4 Rucio versions 39.x through 39.4.1 Rucio versions 40.x through 40.1.0 **Description** A SQL injection issue in the `create sqla query()` function allows authenticated users to execute arbitrary SQL commands against the backend database. This occurs specifically in Oracle deployments using the default `json meta` plugin. The flaw exists because attacker-controlled filter keys and values are interpolated directly into `sqlalchemy.text()` using Python string formatting, which bypasses parameterization. This can be exploited via the 'GET /dids/<scope>/dids/search' endpoint. Successful exploitation may lead to full database compromise, including the extraction of password hashes, authentication tokens, and managed data identifiers, as well as the potential modification of database contents. **Recommendations** Update to version 35.8.5. Update to version 38.5.5. Update to version 39.4.2. Update to version 40.1.1. As a temporary mitigation, restrict access to the 'GET /dids/<scope>/dids/search' endpoint.

**Name of the Vulnerable Software and Affected Versions** Rucio versions 1.30.0 through 35.8.4 Rucio versions 38.x through 38.5.4 Rucio versions 39.x through 39.4.1 Rucio versions 40.x through 40.1.0 **Description** An issue exists in the `FilterEngine.create postgres query()` function where authenticated users can execute arbitrary SQL against the PostgreSQL metadata database. This occurs when the `postgres meta` metadata plugin is configured, as attacker-controlled filter keys and values are interpolated directly into raw SQL strings using Python `.format()`, which are then processed as trusted syntax by `psycopg3`'s `sql.SQL()`. The flaw is accessible via the 'GET /dids/<scope>/dids/search' endpoint. Depending on database privileges, this can lead to the exposure of sensitive tables (such as `identities`, `tokens`, `accounts`, `rse settings`, and `rules`), modification or deletion of metadata, access to server-side files, or remote code execution through the `COPY ... FROM PROGRAM` feature. Password hashes may also be extracted and cracked due to the use of single-iteration SHA-256 without a Key Derivation Function (KDF), a method used to strengthen passwords before hashing. **Recommendations** Update to version 35.8.5. Update to version 38.5.5. Update to version 39.4.2. Update to version 40.1.1. As a temporary mitigation, restrict access to the 'GET /dids/<scope>/dids/search' endpoint or disable the `postgres meta` metadata plugin.

**Name of the Vulnerable Software and Affected Versions** New API versions prior to 0.11.4-alpha.2 **Description** The software features an Insecure Direct Object Reference (IDOR) in the video proxy endpoint. Any authenticated user can access video content belonging to other users by exploiting a missing authorization check. Specifically, the `model.GetByOnlyTaskId(taskID)` function queries tasks using only the `task id` without verifying user ownership, while other task lookups correctly enforce ownership using `model.GetByTaskId(userId, taskID)`. This allows an attacker to bypass tenant isolation for generated media assets and potentially access sensitive data, including upstream response headers and API keys used for contacting AI providers like Google Gemini and OpenAI. The vulnerable API endpoint is `GET /v1/videos/:task id/content`. The vulnerable parameter is `task id`. The vulnerable handler is `controller.VideoProxy`. An attacker can exploit this by sending a request to the affected API endpoint with a known `task id` belonging to another user. **Recommendations** Replace the task lookup in `VideoProxy` with an ownership-checked query: ```go userId := c.GetInt("id") task, exists, err := model.GetByTaskId(userId, taskID) ```

**Name of the Vulnerable Software and Affected Versions** ormar versions 0.23.0 and below **Description** ormar, an async mini ORM for Python, has a Pydantic validation bypass issue in its model constructor. This allows unauthenticated users to skip all field validation by injecting " pk only ": true into a JSON request body. The injection of " pk only ": true allows bypassing type checks, constraints, and other validation rules, leading to the persistence of unvalidated data in the database. A secondary issue involves the " excluded " parameter, which can be used to selectively nullify arbitrary model fields during construction. This affects the recommended FastAPI integration pattern, potentially enabling privilege escalation, data integrity violations, and business logic bypass. The root cause is the direct extraction of " pk only " from user-supplied keyword arguments before validation occurs. The ` pk only ` flag was originally intended for internal optimization but is accessible to external callers. The affected entry points include FastAPI routes using ormar models as request body parameters, as well as direct calls to `Model.objects.create(**user dict)` and `Model(**user dict)`. **Recommendations** Versions prior to 0.23.1 are affected. Replace `kwargs.pop(" pk only ", False)` with a keyword-only parameter that cannot be injected via `**kwargs`. Replace `kwargs.pop(" excluded ", set())` with a keyword-only parameter that cannot be injected via `**kwargs`.

**Name of the Vulnerable Software and Affected Versions** Statmatic versions 6.0.0 through 6.3.9 **Description** Statmatic is a Laravel and Git powered content management system (CMS). Authenticated Control Panel users may, under certain conditions, obtain elevated privileges without completing the intended verification step. This can allow access to sensitive operations and potentially lead to privilege escalation, depending on the user’s existing permissions. **Recommendations** Statmatic versions 6.0.0 through 6.3.9 should be updated to version 6.4.0.

**Name of the Vulnerable Software and Affected Versions** calibre versions prior to 9.4.0 **Description** calibre is an e-book manager for viewing, converting, editing, and cataloging e-books. A HTTP Response Header Injection exists in the calibre Content Server for versions before 9.4.0. An authenticated user can inject arbitrary HTTP headers into server responses through an unsanitized `content disposition` query parameter. This occurs in the `/get/` and `/data-files/get/` API endpoints. The issue is exploitable by any authenticated user, potentially through a crafted link. All users running the calibre Content Server with authentication enabled are affected. **Recommendations** Update to calibre version 9.4.0 or later.