Remote Code Execution in txtai via Reindex API

Executive Summary

This vulnerability exists in txtai versions through 9.10.0 and involves the /reindex API endpoint. The endpoint accepts a function body parameter that is resolved using txtai.util.Resolver, which uses Python's __import__ and getattr functions on a caller-supplied dotted path without any allowlist. If the API is exposed without a TOKEN configured (authentication is optional and off by default) and the index is writable, a remote attacker can specify an arbitrary callable function such as subprocess.getoutput. This allows the attacker to execute arbitrary code remotely on the server process during reindexing.

Exploitation requires specific deployment conditions: the API must be exposed, no authentication token must be set, and the index must be writable. These are not default settings. The vulnerability was fixed by gating the endpoint behind a new reindex configuration flag.

Useful 0 Not Useful 0

Detection Guidance

This vulnerability can be detected by checking if the txtai API /reindex endpoint is exposed without authentication (no TOKEN configured) and if the index is writable. Since exploitation requires sending a crafted POST request to the /reindex endpoint with a function parameter that allows arbitrary code execution, monitoring for such requests can help detect exploitation attempts.

You can use network monitoring tools or command-line utilities like curl to test if the /reindex endpoint is accessible and vulnerable by sending a POST request with a suspicious payload.

• Example curl command to test the vulnerability (do this only in a controlled environment):
• curl -X POST http://<target-host>/reindex -H "Content-Type: application/json" -d '{"config": {}, "function": "os.system"}'

If the server responds without authentication and processes the request, it indicates the vulnerability is present. Additionally, checking the server configuration for the presence or absence of a TOKEN environment variable and whether the reindex configuration flag is enabled can help identify vulnerable deployments.

Useful 0 Not Useful 0

Impact Analysis

This vulnerability can lead to remote code execution on the server running txtai. An attacker who exploits this can run arbitrary commands with the same privileges as the server process, potentially leading to full system compromise, data theft, data manipulation, or disruption of services.

Useful 0 Not Useful 0

Compliance Impact

The vulnerability allows unauthenticated remote code execution on the server process when certain deployment conditions are met, such as the API being exposed without authentication and the index being writable. This critical security flaw could lead to unauthorized access, data breaches, or manipulation of sensitive information.

Such unauthorized access and potential data compromise can negatively impact compliance with common standards and regulations like GDPR and HIPAA, which require strict controls over data confidentiality, integrity, and access.

However, exploitation requires specific non-default configurations (no TOKEN authentication and writable index), so proper configuration and mitigation reduce the risk of non-compliance.

Useful 0 Not Useful 0

Mitigation Strategies

To mitigate this vulnerability, ensure that the /reindex API endpoint is not exposed without authentication by configuring a TOKEN, as authentication is opt-in and endpoints are unauthenticated by default.

Additionally, avoid configuring the index as writable if not necessary, since a writable index combined with an exposed unauthenticated API allows remote code execution.

Applying the fix that gates the /reindex endpoint behind a new reindex configuration flag is also recommended.

Useful 0 Not Useful 0