postgres.git / summary / log / commit / refs

commit    613ed8a588d31f6a3f253e188bf51decb4472b7c
Author:   Noah Misch <noah@leadboat.com>
Date:     Mon Aug 10 16:22:54 2020 +0000
First released in: 14.0, 10.14, 11.9, 12.4, 13.0

    Document clashes between logical replication and untrusted users.
    
    Back-patch to v10, which introduced logical replication.
    
    Security: CVE-2020-14349


doc/src/sgml/logical-replication.sgml | 22 +++++++++++++++++++--- 1 file changed, 19 insertions(+), 3 deletions(-) diff --git a/doc/src/sgml/logical-replication.sgml b/doc/src/sgml/logical-replication.sgml index f657d1d06e0..c9a3c6fbcb4 100644 --- a/doc/src/sgml/logical-replication.sgml +++ b/doc/src/sgml/logical-replication.sgml @@ -502,11 +502,27 @@ <sect1 id="logical-replication-security"> <title>Security</title> + <para> + A user able to modify the schema of subscriber-side tables can execute + arbitrary code as a superuser. Limit ownership + and <literal>TRIGGER</literal> privilege on such tables to roles that + superusers trust. Moreover, if untrusted users can create tables, use only + publications that list tables explicitly. That is to say, create a + subscription <literal>FOR ALL TABLES</literal> only when superusers trust + every user permitted to create a non-temp table on the publisher or the + subscriber. + </para> + <para> The role used for the replication connection must have - the <literal>REPLICATION</literal> attribute (or be a superuser). Access for the role must be - configured in <filename>pg_hba.conf</filename> and it must have the - <literal>LOGIN</literal> attribute. + the <literal>REPLICATION</literal> attribute (or be a superuser). If the + role lacks <literal>SUPERUSER</literal> and <literal>BYPASSRLS</literal>, + publisher row security policies can execute. If the role does not trust + all table owners, include <literal>options=-crow_security=off</literal> in + the connection string; if a table owner then adds a row security policy, + that setting will cause replication to halt rather than execute the policy. + Access for the role must be configured in <filename>pg_hba.conf</filename> + and it must have the <literal>LOGIN</literal> attribute. </para> <para> [parent: 5a936d64c84d]