mirror of
https://github.com/postgres/postgres.git
synced 2025-06-08 22:02:03 +03:00
928bca1a30
This makes the client programs behave as documented regardless of the connect-time search_path and regardless of user-created objects. Today, a malicious user with CREATE permission on a search_path schema can take control of certain of these clients' queries and invoke arbitrary SQL functions under the client identity, often a superuser. This is exploitable in the default configuration, where all users have CREATE privilege on schema "public". This changes behavior of user-defined code stored in the database, like pg_index.indexprs and pg_extension_config_dump(). If they reach code bearing unqualified names, "does not exist" or "no schema has been selected to create in" errors might appear. Users may fix such errors by schema-qualifying affected names. After upgrading, consider watching server logs for these errors. The --table arguments of src/bin/scripts clients have been lax; for example, "vacuumdb -Zt pg_am\;CHECKPOINT" performed a checkpoint. That now fails, but for now, "vacuumdb -Zt 'pg_am(amname);CHECKPOINT'" still performs a checkpoint. Back-patch to 9.3 (all supported versions). Reviewed by Tom Lane, though this fix strategy was not his first choice. Reported by Arseniy Sharoglazov. Security: CVE-2018-1058
27 lines
659 B
Perl
27 lines
659 B
Perl
use strict;
|
|
use warnings;
|
|
use TestLib;
|
|
use Test::More tests => 13;
|
|
|
|
program_help_ok('clusterdb');
|
|
program_version_ok('clusterdb');
|
|
program_options_handling_ok('clusterdb');
|
|
|
|
my $tempdir = tempdir;
|
|
start_test_server $tempdir;
|
|
|
|
issues_sql_like(
|
|
[ 'clusterdb', 'postgres' ],
|
|
qr/statement: CLUSTER;/,
|
|
'SQL CLUSTER run');
|
|
|
|
command_fails([ 'clusterdb', '-t', 'nonexistent', 'postgres' ],
|
|
'fails with nonexistent table');
|
|
|
|
psql 'postgres',
|
|
'CREATE TABLE test1 (a int); CREATE INDEX test1x ON test1 (a); CLUSTER test1 USING test1x';
|
|
issues_sql_like(
|
|
[ 'clusterdb', '-t', 'test1', 'postgres' ],
|
|
qr/statement: CLUSTER public\.test1;/,
|
|
'cluster specific table');
|