What happened
In SQLBot 1.10.0 through 1.10.3, the PostgreSQL dangerous-function denylist is not applied because DS_SPECIFIC_DANGEROUS_FUNCTIONS keys on 'postgresql' while lookups use the 'pg' type (CWE-184/CWE-1011, CVSS 5.9). An authenticated user can steer LLM-generated SQL past check_sql_read() to call pg_read_file, pg_write_file, lo_import, or lo_export, reading/writing files on the PostgreSQL server.
Why it matters
SQLBot is designed to safely convert natural language into SQL via an LLM. A denylist mismatch defeats the intended read-only safety boundary, so a user (or a prompt-injected query) can get the LLM to generate SQL that reads or writes server-side files through Postgres — turning the 'safe text-to-SQL' boundary into a file-access primitive.
Attack vector
Authenticated user crafts an LLM-generated query that invokes pg_read_file/pg_write_file/lo_import/lo_export, bypassing the denylist and accessing files on the database host
Affected systems
SQLBot 1.10.0 through 1.10.3 (PostgreSQL)
Mitigation
Upgrade to the SQLBot release that fixes the denylist type mismatch