aboutsummaryrefslogtreecommitdiff
path: root/src/backend/utils/adt/tsquery_gist.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2008-01-03 21:23:15 +0000
committerTom Lane <tgl@sss.pgh.pa.us>2008-01-03 21:23:15 +0000
commiteedb068c0a7474fb11d67d03b0a9e1ded5df82c4 (patch)
tree1e5a19e0970f87fea7d5e2d243d5614318229f79 /src/backend/utils/adt/tsquery_gist.c
parent98f27aaef34291246c09ce5d0e0fba4f4477467a (diff)
downloadpostgresql-eedb068c0a7474fb11d67d03b0a9e1ded5df82c4.tar.gz
postgresql-eedb068c0a7474fb11d67d03b0a9e1ded5df82c4.zip
Make standard maintenance operations (including VACUUM, ANALYZE, REINDEX,
and CLUSTER) execute as the table owner rather than the calling user, using the same privilege-switching mechanism already used for SECURITY DEFINER functions. The purpose of this change is to ensure that user-defined functions used in index definitions cannot acquire the privileges of a superuser account that is performing routine maintenance. While a function used in an index is supposed to be IMMUTABLE and thus not able to do anything very interesting, there are several easy ways around that restriction; and even if we could plug them all, there would remain a risk of reading sensitive information and broadcasting it through a covert channel such as CPU usage. To prevent bypassing this security measure, execution of SET SESSION AUTHORIZATION and SET ROLE is now forbidden within a SECURITY DEFINER context. Thanks to Itagaki Takahiro for reporting this vulnerability. Security: CVE-2007-6600
Diffstat (limited to 'src/backend/utils/adt/tsquery_gist.c')
0 files changed, 0 insertions, 0 deletions