From: Tom Lane <tgl@sss.pgh.pa.us>
To: jian he <jian.universality@gmail.com>
Cc: pgsql-general list <pgsql-general@lists.postgresql.org>
Subject: Re: wiki.postgres Tighten trigger permission checks already resolved
Date: Mon, 24 Apr 2023 23:06:28 -0400
Message-ID: <603516.1682391988@sss.pgh.pa.us> (raw)
In-Reply-To: <CACJufxHcOisqCgRXcWVP4tgyEbGPbShrtsj4toMBHsXCFwO8Tg@mail.gmail.com>
References: <CACJufxHcOisqCgRXcWVP4tgyEbGPbShrtsj4toMBHsXCFwO8Tg@mail.gmail.com>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-general@postgresql.org
Cc: tgl@sss.pgh.pa.us, jian.universality@gmail.com
Subject: Re: wiki.postgres Tighten trigger permission checks already resolved
In-Reply-To: <603516.1682391988@sss.pgh.pa.us>
References: <CACJufxHcOisqCgRXcWVP4tgyEbGPbShrtsj4toMBHsXCFwO8Tg@mail.gmail.com> <603516.1682391988@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
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