Langroid vulnerabilities

Langroid before version 0.65.5 has a vulnerability in the Neo4jChatAgent component that allows Cypher query injection. An attacker can influence the query via prompt injection, enabling reading or destroying all graph data, and with APOC or dbms.security procedures enabled, achieving OS command and filesystem access.

Langroid versions prior to 0.65.2 contain a critical sandbox escape vulnerability leading to Remote Code Execution (RCE) in its `TableChatAgent` and `VectorStore` components. When evaluating LLM-generated tool messages with `full_eval=True`, the `eval()` function fails to remove `__builtins__` from the globals dictionary, allowing access to system functions like `__import__('os').system()`. An attacker can exploit this by providing a crafted prompt to achieve unauthenticated RCE on the host.

In Langroid framework prior to version 0.65.1, a SQL injection vulnerability was found in the `SQLChatAgent` component. Despite default dangerous operations being disabled, the protection mechanism using a regex blocklist and SELECT allowlist can be bypassed with crafted PostgreSQL queries, enabling server file reads.

Langroid SQLChatAgent before version 0.63.0 executes SQL generated by an LLM, which is influenceable by prompt injection. An attacker can coerce execution of dangerous operations like COPY ... FROM PROGRAM, leading to remote code execution on the database host.

A vulnerability in Langroid framework prior to version 0.65.3 allows untrusted users to directly invoke tools via raw JSON payloads, even when tools are registered with `use=False, handle=True`.

In the Langroid framework, the ReadFileTool and WriteFileTool do not validate that the file path stays within the working directory (curr_dir). This allows an attacker to read and write files outside the allowed directory using path traversal sequences like ../.

In Langroid library prior to version 0.64.0, the SQLChatAgent component has an imperfect _validate_query defense layer that fails to block all dangerous SQL primitives. The blocklist misses PostgreSQL file-reading functions (pg_read_file, pg_stat_file) and SQL Server/SQLite constructs, allowing an attacker to read files from the database host.