-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Format: 1.8
Date: Tue, 11 Aug 2020 12:07:26 +0200
Source: postgresql-12
Architecture: source
Version: 12.4-1
Distribution: unstable
Urgency: medium
Maintainer: Debian PostgreSQL Maintainers <team+postgresql@tracker.debian.org>
Changed-By: Christoph Berg <myon@debian.org>
Changes:
postgresql-12 (12.4-1) unstable; urgency=medium
.
* New upstream version.
+ Set a secure search_path in logical replication walsenders and apply
workers (Noah Misch)
.
A malicious user of either the publisher or subscriber database could
potentially cause execution of arbitrary SQL code by the role running
replication, which is often a superuser. Some of the risks here are
equivalent to those described in CVE-2018-1058, and are mitigated in
this patch by ensuring that the replication sender and receiver execute
with empty search_path settings. (As with CVE-2018-1058, that change
might cause problems for under-qualified names used in replicated
tables' DDL.) Other risks are inherent in replicating objects that
belong to untrusted roles; the most we can do is document that there is
a hazard to consider. (CVE-2020-14349)
.
+ Make contrib modules' installation scripts more secure (Tom Lane)
.
Attacks similar to those described in CVE-2018-1058 could be carried out
against an extension installation script, if the attacker can create
objects in either the extension's target schema or the schema of some
prerequisite extension. Since extensions often require superuser
privilege to install, this can open a path to obtaining superuser
privilege. To mitigate this risk, be more careful about the search_path
used to run an installation script; disable check_function_bodies within
the script; and fix catalog-adjustment queries used in some contrib
modules to ensure they are secure. Also provide documentation to help
third-party extension authors make their installation scripts secure.
This is not a complete solution; extensions that depend on other
extensions can still be at risk if installed carelessly.
(CVE-2020-14350)
.
* DH 13.
Checksums-Sha1:
76afbe79eaedaa2f375d2a4610fd8fa58e6d0758 3627 postgresql-12_12.4-1.dsc
5a64e3916a42547227f2afec359d1c9ddc3eba8e 20669776 postgresql-12_12.4.orig.tar.bz2
8aa3e4ef495be5c487ae705ba1f05abb7a73175d 23736 postgresql-12_12.4-1.debian.tar.xz
Checksums-Sha256:
483e2c17b982240256bdd5812b3ed0669c5017e4be645423e0bbb409fb759d6f 3627 postgresql-12_12.4-1.dsc
bee93fbe2c32f59419cb162bcc0145c58da9a8644ee154a30b9a5ce47de606cc 20669776 postgresql-12_12.4.orig.tar.bz2
525e1a0bc8f14cf5a437f1c8775be501c6490f8c55a45d9b87f905cfd6d5c87b 23736 postgresql-12_12.4-1.debian.tar.xz
Files:
1e28f7dd5d157336dbcbba77cd42912a 3627 database optional postgresql-12_12.4-1.dsc
80ebbf0e55193b123760e5f8e48c6cff 20669776 database optional postgresql-12_12.4.orig.tar.bz2
50e330d3d91c9795cf11aa154ecce1d1 23736 database optional postgresql-12_12.4-1.debian.tar.xz
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCAAdFiEEXEj+YVf0kXlZcIfGTFprqxLSp64FAl80+H8ACgkQTFprqxLS
p65r8BAAuAJHpM6F25c2sGcm7Dln68DuNkzUUFFfrUcCUykvKCtPNcLisDWewsAL
ki6Yr9lFt1W9HEuDeDOGxM5Ks1T0v89jTwDgfO7cQgp+X4jVL1zAMIz0MnSqzDyX
gRKGeHMnWyV7851Pqc70m2/7eLKCzamRsx9qcJD285J0bmVO3wIqzCusi5ayyFFf
KQBuEmWtD5A/RDmtSLqp3zN9oezNRtA/LqoLBLVs19V7216VZQDU+E8nWuYy+wEI
KHsrXEWyw5uCaWKj+WAk5oJcZ1mfds1qOJ0ZOAAwDHBgbALofvxdUNAZ5d/l7dxr
wRHnsFif90KYt20nlB3eOxPdU9FM3zKuWbwmYQU7Zdn4wPCJYhfaM39wETmjhLA4
hnVFuYbRnaGDJaxpqpSqhwkZV+n7FaUgx8dUnEhtOU7ffsm7+cwbmK2S2OVrFt/6
++tTxoQ5x7sYOQw0T65kHvmNuXdGZNamkgne1BwtCu88qYd//MQf/3eEJAwJr0Xg
V7Qbb0VFth9YCb0SQWnOAcfFupZM4QwCagisyXc6jlhYQ1Xbv8GBBPiSONE6x6C/
CJSqOr7Ay2HHy/kAVtpwdpqr1PY7eQBgfsmWeMzVJE1batRm//QKsXsqoUEwHCcr
Ur7pTeDImbjqSeY6LUzPukx6VNC9B9aZamQdgc9qW7TIG90BASs=
=VmYw
-----END PGP SIGNATURE-----
