database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2026-10-23 13:29:09 +03:00
Code Activity

doc: Granting TRIGGER or REFERENCES on table is dangerous.

Browse Source 
It's always been the case that granting these privileges to users that
you don't fully trust was a bad idea, but it hasn't always been
obvious to people reading the documentation that this is the case.
To prevent confusion, and also repeated reports to pgsql-security,
mention it explicitly.

Discussion: http://postgr.es/m/CA+TgmobrjCHBuWHrvX3=2vndUCO2thUOdevrCcMDFW86cqCYvw@mail.gmail.com
Reviewed-by: Nathan Bossart <nathandbossart@gmail.com>
Backpatch-through: 14
This commit is contained in:
Robert Haas
2026-07-20 13:36:39 -04:00
parent 19e3aa7041
commit 545e2a9d74
1 changed files with 8 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
doc/src/sgml/ddl.sgml
View File

@@ -2092,7 +2092,11 @@ REVOKE ALL ON accounts FROM PUBLIC;
<listitem>
<para>
Allows creation of a foreign key constraint referencing a
table, or specific column(s) of a table.
table, or specific column(s) of a table. Great care should be taken when
granting this privilege, since a user who creates a foreign key can arrange
for enforcement of that foreign key to call an arbitrary function, such as
a cast function, and such functions will be called with the privileges of
the table owner.
</para>
</listitem>
</varlistentry>
@@ -2101,7 +2105,9 @@ REVOKE ALL ON accounts FROM PUBLIC;
<term><literal>TRIGGER</literal></term>
<listitem>
<para>
Allows creation of a trigger on a table, view, etc.
Allows creation of a trigger on a table, view, etc. Great care should be
taken when granting this privilege, since any triggers added to a table
or view will be executed with the privileges of users who modify it.
</para>
</listitem>
</varlistentry>