1
0
mirror of https://github.com/postgres/postgres.git synced 2026-10-23 13:29:09 +03:00

Fix privilege handling in postgres_fdw statistics import.

When ANALYZE imports statistics from a remote server, it fetched/stored
the statistics while still running as the user executing ANALYZE, not as
the foreign table's owner.  This is inconsistent with the sampling path,
and it causes a security issue: a role that owns a foreign table but has
no access to the underlying remote data (eg, no access privileges on the
remote server) could obtain that data by having a privileged user run
ANALYZE on the table; the imported statistics like most_common_vals then
expose sampled values from the remote data, as shown in the reproducer
on the discussion thread.

To fix, switch to the foreign table owner's userid in analyze_rel()
before calling the ImportForeignStatistics() routine, mirroring the
identity used by the sampling path.   This not only makes the privilege
handling consistent between the sampling/import paths, but also prevents
statistics import from disclosing data the table owner couldn't
otherwise obtain.

Oversight in commit 28972b6fc.

Reported-by: Fujii Masao <masao.fujii@gmail.com>
Reported-by: Osama Abdul Qader <osamaabdulqader.cs@gmail.com>
Reported-by: Noah Misch <noah@leadboat.com>
Author: Noah Misch <noah@leadboat.com>
Reviewed-by: Matheus Alcantara <matheusssilv97@gmail.com>
Reviewed-by: Etsuro Fujita <etsuro.fujita@gmail.com>
Discussion: https://postgr.es/m/CAPmGK16jVk+i2KMkkgR9ajoPdaUAinvcspkk5Bc6urbo2xYTMQ@mail.gmail.com
Backpatch-through: 19
This commit is contained in:
Etsuro Fujita
2026-09-26 20:35:00 +09:00
parent 1a846a555a
commit 7d47e41238
2 changed files with 30 additions and 9 deletions

View File

@@ -5832,11 +5832,10 @@ fetch_remote_statistics(Relation relation,
}
/*
* Get connection to the foreign server. Connection manager will
* establish new connection if necessary.
*
* Note that unlike the sampling case, we only query pg_class and
* pg_stats, so we do the remote access as the current user.
* Get the connection to use. We do the remote access as the table's
* owner. Note that unlike AnalyzeForeignTable(), the core code would
* already have switched us to the table's owner, before we are called
* from ImportForeignStatistics().
*/
user = GetUserMapping(GetUserId(), table->serverid);
conn = GetConnection(user, false, NULL);