aboutsummaryrefslogtreecommitdiff
path: root/src/backend/utils/adt/ruleutils.c
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2008-01-03 21:25:34 +0000
committerTom Lane <tgl@sss.pgh.pa.us>2008-01-03 21:25:34 +0000
commit230d5cfc4739bc4963c8d67e4a7cd84abe53ef93 (patch)
tree0fa8d138ed251e873bd55a4e7b402fbdd9f57488 /src/backend/utils/adt/ruleutils.c
parent0776cb2116f4eaec743f1e304c1255c318a20d1f (diff)
downloadpostgresql-230d5cfc4739bc4963c8d67e4a7cd84abe53ef93.tar.gz
postgresql-230d5cfc4739bc4963c8d67e4a7cd84abe53ef93.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/ruleutils.c')
0 files changed, 0 insertions, 0 deletions