txtai - Unauthenticated Remote Code Execution via Unsafe Reflection in API /reindex function Parameter
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| neuml | txtai | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Neuml | Txtai |
|
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: 1.4% (1.354% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | txtai through 9.10.0, fixed in commit 11b32da, exposes an API /reindex endpoint whose function body parameter is resolved through txtai.util.Resolver, which performs __import__ and getattr on the caller-supplied dotted path with no allowlist. When the API is exposed with no TOKEN configured (authentication is opt-in, so all endpoints are unauthenticated) and the index is configured writable, a remote attacker can set function to an arbitrary callable such as subprocess.getoutput, achieving remote code execution as the server process during reindexing. Exploitation requires those deployment conditions (API exposed, no TOKEN, writable index); it is not the default configuration. The fix gates the endpoint behind a new reindex configuration flag. | |
| Title | txtai - Unauthenticated Remote Code Execution via Unsafe Reflection in API /reindex function Parameter | |
| First Time appeared |
Neuml
Neuml txtai |
|
| Weaknesses | CWE-94 | |
| CPEs | cpe:2.3:a:neuml:txtai:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Neuml
Neuml txtai |
|
| References |
|
|
| Metrics |
cvssV3_1
|