]> git.ipfire.org Git - thirdparty/postgresql.git/commit
In security-restricted operations, block enqueue of at-commit user code.
authorNoah Misch <noah@leadboat.com>
Mon, 9 Nov 2020 15:32:09 +0000 (07:32 -0800)
committerNoah Misch <noah@leadboat.com>
Mon, 9 Nov 2020 15:32:13 +0000 (07:32 -0800)
commit43ebfea5a988582e9edc752cb1e22e929edac03b
tree760c0a95f29bfe75cf1377207c7a5a8956e3d75e
parent5a55a80cc35da1e450f8d0fe22aa380e7fe68d64
In security-restricted operations, block enqueue of at-commit user code.

Specifically, this blocks DECLARE ... WITH HOLD and firing of deferred
triggers within index expressions and materialized view queries.  An
attacker having permission to create non-temp objects in at least one
schema could execute arbitrary SQL functions under the identity of the
bootstrap superuser.  One can work around the vulnerability by disabling
autovacuum and not manually running ANALYZE, CLUSTER, REINDEX, CREATE
INDEX, VACUUM FULL, or REFRESH MATERIALIZED VIEW.  (Don't restore from
pg_dump, since it runs some of those commands.)  Plain VACUUM (without
FULL) is safe, and all commands are fine when a trusted user owns the
target object.  Performance may degrade quickly under this workaround,
however.  Back-patch to 9.5 (all supported versions).

Reviewed by Robert Haas.  Reported by Etienne Stalmans.

Security: CVE-2020-25695
contrib/postgres_fdw/connection.c
src/backend/access/transam/xact.c
src/backend/commands/portalcmds.c
src/backend/commands/trigger.c
src/test/regress/expected/privileges.out
src/test/regress/sql/privileges.sql