Re: Side effect of CVE-2017-7484 fix? - Mailing list pgsql-hackers

From Amit Langote
Subject Re: Side effect of CVE-2017-7484 fix?
Date
Msg-id 0e1f4466-7275-9752-a935-72b042001d55@lab.ntt.co.jp
Whole thread Raw
In response to Re: Side effect of CVE-2017-7484 fix?  (Stephen Frost <sfrost@snowman.net>)
Responses Re: Side effect of CVE-2017-7484 fix?  (Dilip Kumar <dilipbalaut@gmail.com>)
List pgsql-hackers
Hi,

On 2018/10/22 14:41, Stephen Frost wrote:
> Greetings,
> 
> * Dilip Kumar (dilipbalaut@gmail.com) wrote:
>> As part of the security fix
>> (e2d4ef8de869c57e3bf270a30c12d48c2ce4e00c), we have restricted the
>> users from accessing the statistics of the table if the user doesn't
>> have privileges on the table and the function is not leakproof.  Now,
>> as a side effect of this, if the user has the privileges on the root
>> partitioned table but does not have privilege on the child tables, the
>> user will be able to access the data of the child table but it won't
>> be able to access the statistics of the child table. This may result
>> in a bad plan.   I am not sure what should be the fix.  Should we
>> allow to access the statistics of the table if a user has privilege on
>> its parent table?
> 
> Yes...  If the user has access to the parent table then they can see the
> child tables, so they should be able to see the statistics on them.

Yeah, but I'd think only if access the child tables are being accessed via
the parent table.

So, maybe, statistic_proc_security_check() added by that commit should
return true if IS_OTHER_REL(vardata->rel)?

Thanks,
Amit



pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: Function to promote standby servers
Next
From: John Naylor
Date:
Subject: Re: WIP: Avoid creation of the free space map for small tables