pg.ddx.io pgsql-general@postgresql.org mailing list archive
help / color / mirror / Atom feed wiki.postgres Tighten trigger permission checks already resolved
2+ messages / 2 participants
[nested] [flat]
* wiki.postgres Tighten trigger permission checks already resolved
@ 2023-04-25 02:09 jian he <jian.universality@gmail.com>
2023-04-25 03:06 ` Re: wiki.postgres Tighten trigger permission checks already resolved Tom Lane <tgl@sss.pgh.pa.us>
0 siblings, 1 reply; 2+ messages in thread
From: jian he @ 2023-04-25 02:09 UTC (permalink / raw)
To: pgsql-general list <pgsql-general@lists.postgresql.org>
Hi.
The following Todo item seems already resolved in pg15.
https://wiki.postgresql.org/wiki/Todo#Triggers
> Tighten trigger permission checks
>
> - Security leak with trigger functions?
> <http://archives.postgresql.org/pgsql-hackers/2006-12/msg00564.php;
>
>
But it seems to not appear in the pg15 release notes. (I searched for the
keywords "trigger" and "function").
^ permalink raw reply [nested|flat] 2+ messages in thread
* Re: wiki.postgres Tighten trigger permission checks already resolved
2023-04-25 02:09 wiki.postgres Tighten trigger permission checks already resolved jian he <jian.universality@gmail.com>
@ 2023-04-25 03:06 ` Tom Lane <tgl@sss.pgh.pa.us>
0 siblings, 0 replies; 2+ messages in thread
From: Tom Lane @ 2023-04-25 03:06 UTC (permalink / raw)
To: jian he <jian.universality@gmail.com>; +Cc: pgsql-general list <pgsql-general@lists.postgresql.org>
jian he <jian.universality@gmail.com> writes:
> The following Todo item seems already resolved in pg15.
> https://wiki.postgresql.org/wiki/Todo#Triggers
>> Tighten trigger permission checks
>> - Security leak with trigger functions?
>> <http://archives.postgresql.org/pgsql-hackers/2006-12/msg00564.php;
> But it seems to not appear in the pg15 release notes. (I searched for the
> keywords "trigger" and "function").
The case shown at the head of that thread was fixed more than a decade
ago, cf commit 891e6e7bf (CVE-2012-0866). However, the followup questions
discussed in the thread are still live: should there be a run-time not
only trigger-creation-time privilege check, and if so what should it
check exactly? And is a separate TRIGGER privilege even reasonable,
rather than just saying you must be table owner to create a trigger?
regards, tom lane
^ permalink raw reply [nested|flat] 2+ messages in thread
end of thread, other threads:[~2023-04-25 03:06 UTC | newest]
Thread overview: 2+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2023-04-25 02:09 wiki.postgres Tighten trigger permission checks already resolved jian he <jian.universality@gmail.com>
2023-04-25 03:06 ` Tom Lane <tgl@sss.pgh.pa.us>
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox