| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Kirill Reshke <reshkekirill(at)gmail(dot)com> |
| Cc: | jian he <jian(dot)universality(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: pageinspect some function no need superuser priv |
| Date: | 2025-10-14 14:29:39 |
| Message-ID: | 954668.1760452179@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Kirill Reshke <reshkekirill(at)gmail(dot)com> writes:
> On Tue, 14 Oct 2025, 18:27 jian he, <jian(dot)universality(at)gmail(dot)com> wrote:
>> If you're the table owner, you should be allowed to use get_raw_page (and
>> other pageinspect module functions)?
> I was also wondering if there is any security vulnerability with that.
> I was thinking about page lsn, checkpoint and wal compression as a possible
> way to abuse, but did not managed to came up with exploit
Yeah, I do not think it follows that being table owner should
entitle you to such low-level access. I'm inclined to reject
this proposal.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Nathan Bossart | 2025-10-14 15:51:51 | Re: pageinspect some function no need superuser priv |
| Previous Message | Melanie Plageman | 2025-10-14 14:16:24 | Re: eliminate xl_heap_visible to reduce WAL (and eventually set VM on-access) |