Description
SQL injection vulnerability in pgAdmin 4 Maintenance Tool. Four user-supplied JSON fields (buffer_usage_limit, vacuum_parallel, vacuum_index_cleanup, reindex_tablespace) were concatenated directly into the rendered VACUUM/ANALYZE/REINDEX command and passed to psql --command. An authenticated user with the tools_maintenance permission could break out of the option syntax and execute arbitrary SQL on the connected PostgreSQL server. The injected SQL could in turn invoke COPY ... TO PROGRAM to escalate to operating-system command execution on the database host. Fix introduces server-side allow-listing of all four fields and switches reindex_tablespace from manual quoting to the qtIdent filter. This issue affects pgAdmin 4: before 9.15.
Authenticated pgAdmin user with tools_maintenance permission. SQL injection escalates within the privileges already granted to the user's database connection; RCE via COPY ... TO PROGRAM additionally requires PostgreSQL superuser on the target connection. S:U reflects that the impact remains within the user's existing database privilege scope rather than crossing a security authority boundary.
Authenticated pgAdmin user with tools_maintenance permission. SQL injection escalates within the privileges already granted to the user's database connection; RCE via COPY ... TO PROGRAM additionally requires PostgreSQL superuser on the target connection. S:U reflects that the impact remains within the user's existing database privilege scope rather than crossing a security authority boundary.
Product status
7.6 (custom) before 9.15
Credits
j3seer
References
github.com/pgadmin-org/pgadmin4/issues/9898