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:23:45 +0000
committerTom Lane <tgl@sss.pgh.pa.us>2008-01-03 21:23:45 +0000
commit3af35f8d40bede09c4fe976050ff402dc346dbf2 (patch)
treec91e4271dd0c01688da04733af50e83f9f43a635 /src/backend/utils/adt/ruleutils.c
parent0f8fe9bed141e78bbce03f4517fdc5a6e35665c9 (diff)
downloadpostgresql-3af35f8d40bede09c4fe976050ff402dc346dbf2.tar.gz
postgresql-3af35f8d40bede09c4fe976050ff402dc346dbf2.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