Accepted postgresql-11 11.10-0+deb10u1 (source) into proposed-updates->stable-new, proposed-updates
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
Format: 1.8
Date: Tue, 01 Dec 2020 10:04:12 +0100
Source: postgresql-11
Architecture: source
Version: 11.10-0+deb10u1
Distribution: buster
Urgency: medium
Maintainer: Debian PostgreSQL Maintainers <team+postgresql@tracker.debian.org>
Changed-By: Christoph Berg <myon@debian.org>
Closes: 974063
Changes:
postgresql-11 (11.10-0+deb10u1) buster; urgency=medium
.
* New upstream version.
+ Fixes timetz regression test failures. (Closes: #974063)
.
+ Block DECLARE CURSOR ... WITH HOLD and firing of deferred triggers
within index expressions and materialized view queries (Noah Misch)
.
This is essentially a leak in the security restricted operation sandbox
mechanism. An attacker having permission to create non-temporary SQL
objects could parlay this leak to execute arbitrary SQL code as a
superuser.
.
The PostgreSQL Project thanks Etienne Stalmans for reporting this
problem. (CVE-2020-25695)
.
+ Fix usage of complex connection-string parameters in pg_dump,
pg_restore, clusterdb, reindexdb, and vacuumdb (Tom Lane)
.
The -d parameter of pg_dump and pg_restore, or the --maintenance-db
parameter of the other programs mentioned, can be a connection string
containing multiple connection parameters rather than just a database
name. In cases where these programs need to initiate additional
connections, such as parallel processing or processing of multiple
databases, the connection string was forgotten and just the basic
connection parameters (database name, host, port, and username) were
used for the additional connections. This could lead to connection
failures if the connection string included any other essential
information, such as non-default SSL or GSS parameters. Worse, the
connection might succeed but not be encrypted as intended, or be
vulnerable to man-in-the-middle attacks that the intended connection
parameters would have prevented. (CVE-2020-25694)
.
+ When psql's \connect command re-uses connection parameters, ensure that
all non-overridden parameters from a previous connection string are
re-used (Tom Lane)
.
This avoids cases where reconnection might fail due to omission of
relevant parameters, such as non-default SSL or GSS options. Worse, the
reconnection might succeed but not be encrypted as intended, or be
vulnerable to man-in-the-middle attacks that the intended connection
parameters would have prevented. This is largely the same problem as
just cited for pg_dump et al, although psql's behavior is more complex
since the user may intentionally override some connection parameters.
(CVE-2020-25694)
.
+ Prevent psql's \gset command from modifying specially-treated variables
(Noah Misch)
.
\gset without a prefix would overwrite whatever variables the server
told it to. Thus, a compromised server could set specially-treated
variables such as PROMPT1, giving the ability to execute arbitrary shell
code in the user's session.
.
The PostgreSQL Project thanks Nick Cleaton for reporting this problem.
(CVE-2020-25696)
Checksums-Sha1:
215fab141ba76bc290e2d3a78aee7d8943d6d10f 3745 postgresql-11_11.10-0+deb10u1.dsc
97bc8d07d30229b52bac57241cd48bcf6116ef44 20003842 postgresql-11_11.10.orig.tar.bz2
110e25c15a16fcc966ab3c3a3bedd15b3485b636 26252 postgresql-11_11.10-0+deb10u1.debian.tar.xz
Checksums-Sha256:
088a20ee67d5f296ad2d608e35f9aaa685cf4afe6be348b0d4bdca3089c7fbdf 3745 postgresql-11_11.10-0+deb10u1.dsc
13e6d2f80662fe463bc7718cdf0de6a9ec67fc78afcc7a3ae66b9ea19bb97899 20003842 postgresql-11_11.10.orig.tar.bz2
638afc81e8ed4baac1814051ddd087d7e93612a5d5c2891dbdfb5ce67d04f611 26252 postgresql-11_11.10-0+deb10u1.debian.tar.xz
Files:
8912adbe88b91e026137f0a0eebd7f91 3745 database optional postgresql-11_11.10-0+deb10u1.dsc
c9dbf5ae42a08b937d1b6cf7921e4669 20003842 database optional postgresql-11_11.10.orig.tar.bz2
9cd116660ae21070bfcd2da04239ca24 26252 database optional postgresql-11_11.10-0+deb10u1.debian.tar.xz
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCAAdFiEEXEj+YVf0kXlZcIfGTFprqxLSp64FAl/GIeEACgkQTFprqxLS
p64xuRAAtVKeQSLdINLmdrsumqOTft+AOFit6Np5jGMcGpi2uLTBxeLRjEMv8d6q
JVLJNr3hRC+HhyYBANzCkpX4hDklrQAYsHXM/j/QKkEoYS53RRF4KtDpSheo0fSf
+SJmmtiGluw5r2FfT0YcIxO+olp7wEnnZkUsylVhN7LSwsWmAQfYSbbEwzOyBsfT
6m5x84auO4neWRIghjQ7rl86sWtB+T1T36HGxRGbV7BxOvhG22bmO1AUZNMs4k4V
xeum9WrOMwG0jhTH1sUoDkfZ2ItJQrEh5O12pl6oMeEGKem0fFd3+RilnAaGbn3v
fjHlOhIMa3hC5f0vDyjQTcyDPtxqBOi/oywLu5EhdX8v9c3/a+iIIQAnxu6FApdP
CvbtryGmWVgFgDsOQ8+S4NORm/BUroNNSNT2RUFP+/4VLA5IBBG/wInoEBmPBth0
kettOQFUENfyI6ne0ZKXs3qWPJo0bdLmP0wlT/CBNtrvznjWWzXF7uoTCHpxmbuR
mt1lmktRCPabhs6sEA7wCCGng3XmoA3K43+tu9ixIPS9yBB1WbNk4SzsjJPdAh82
jHJOr0RduWUDh+G7DJ1ObS7P1hnH186SlgPPJNEamzUuFBVmeu5l/WCj9ibWUanE
Ew9SoRxUCS4cfWDZeVAIBoMl8nAFjrQJXW6iGEUhdHVGA8lwJn0=
=YXya
-----END PGP SIGNATURE-----
Reply to: