mirrors/postgres
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

doc: warn of SECURITY DEFINER schemas for non-sql_body functions

Browse Source 
Non-sql_body functions are evaluated at runtime.

Reported-by: Erki Eessaar

Discussion: https://postgr.es/m/AM9PR01MB8268BF5E74E119828251FD34FE409@AM9PR01MB8268.eurprd01.prod.exchangelabs.com

Backpatch-through: 10
This commit is contained in:
Bruce Momjian 2022-08-31 21:10:37 -04:00
parent a009cb3141
commit 1703726488
1 changed files with 4 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
doc/src/sgml/ref/create_function.sgml
View File

@ -779,7 +779,10 @@ SELECT * FROM dup(42);
<para>
Because a <literal>SECURITY DEFINER</literal> function is executed
with the privileges of the user that owns it, care is needed to
ensure that the function cannot be misused. For security,
ensure that the function cannot be misused. This is particularly
important for non-<replaceable>sql_body</replaceable> functions because
their function bodies are evaluated at run-time, not creation time.
For security,
<xref linkend="guc-search-path"/> should be set to exclude any schemas
writable by untrusted users. This prevents
malicious users from creating objects (e.g., tables, functions, and