Re: pg18: Virtual generated columns are not (yet) safe when superuser selects from them - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: pg18: Virtual generated columns are not (yet) safe when superuser selects from them
Date
Msg-id 59664625-e019-440a-b69e-16d092699779@eisentraut.org
Whole thread Raw
In response to pg18: Virtual generated columns are not (yet) safe when superuser selects from them  (Feike Steenbergen <feikesteenbergen@gmail.com>)
Responses Re: pg18: Virtual generated columns are not (yet) safe when superuser selects from them
Re: pg18: Virtual generated columns are not (yet) safe when superuser selects from them
Re: pg18: Virtual generated columns are not (yet) safe when superuser selects from them
List pgsql-hackers
On 23.05.25 10:43, Feike Steenbergen wrote:
> Attached is a sample exploit, that achieves this, key components:
> 
> - the GENERATED column uses a user defined immutable function
> - this immutable function cannot ALTER ROLE (needs volatile)
> - therefore this immutable function calls a volatile function
> - the volatile function can contain any security exploit

I propose to address this by not allowing the use of user-defined 
functions in generation expressions for now.  The attached patch 
implements this.  This assumes that all built-in functions are 
trustworthy, for this purpose, which seems likely true and likely desirable.

I think the feature is still useful like that, and this approach 
provides a path to add new functionality in the future that grows this 
set of allowed functions, for example by allowing some configurable set 
of "trusted" functions or whatever.

Attachment

pgsql-hackers by date:

Previous
From: Nisha Moond
Date:
Subject: Re: Fix slot synchronization with two_phase decoding enabled
Next
From: Peter Eisentraut
Date:
Subject: Re: Possibly hard-to-read message