Publishing details
Changelog
postgresql-10 (10.17-0ubuntu0.18.04.1~ubuntu16.04.1) xenial; urgency=medium
* Backport to xenial:
- Use old-style PIE config in debian/rules.
postgresql-10 (10.17-0ubuntu0.18.04.1) bionic-security; urgency=medium
* New upstream version (LP: #1928773).
+ Prevent integer overflows in array subscripting calculations (Tom Lane)
The array code previously did not complain about cases where an array's
lower bound plus length overflows an integer. This resulted in later
entries in the array becoming inaccessible (since their subscripts could
not be written as integers), but more importantly it confused subsequent
assignment operations. This could lead to memory overwrites, with
ensuing crashes or unwanted data modifications. (CVE-2021-32027)
+ Fix mishandling of junk columns in INSERT ... ON CONFLICT ... UPDATE
target lists (Tom Lane)
If the UPDATE list contains any multi-column sub-selects (which give
rise to junk columns in addition to the results proper), the UPDATE path
would end up storing tuples that include the values of the extra junk
columns. That's fairly harmless in the short run, but if new columns are
added to the table then the values would become accessible, possibly
leading to malfunctions if they don't match the datatypes of the added
columns.
In addition, in versions supporting cross-partition updates, a
cross-partition update triggered by such a case had the reverse problem:
the junk columns were removed from the target list, typically causing an
immediate crash due to malfunction of the multi-column sub-select
mechanism. (CVE-2021-32028)
+ Details about these and many further changes can be found at:
https://www.postgresql.org/docs/10/release-10-17.html
postgresql-10 (10.16-0ubuntu0.18.04.1) bionic; urgency=medium
* New upstream version (LP: #1915254)
+ Fix CREATE INDEX CONCURRENTLY to wait for
concurrent prepared transactions (Andrey Borodin)
At the point where CREATE INDEX CONCURRENTLY
waits for all concurrent transactions to complete so that it can see
rows they inserted, it must also wait for all prepared transactions
to complete, for the same reason. Its failure to do so meant that
rows inserted by prepared transactions might be omitted from the new
index, causing queries relying on the index to miss such rows.
In installations that have enabled prepared transactions
(max_prepared_transactions > 0),
it's recommended to reindex any concurrently-built indexes in
case this problem occurred when they were built.
+ Details about this and many further changes can be found at:
https://www.postgresql.org/docs/10/static/release-10-16.html
postgresql-10 (10.15-0ubuntu0.18.04.1) bionic-security; urgency=medium
* New upstream version.
+ 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)
+ Details about these and many further changes can be found at:
https://www.postgresql.org/docs/10/static/release-10-15.html
postgresql-10 (10.14-0ubuntu0.18.04.1) bionic-security; urgency=medium
* New upstream release (LP: #1892335).
- 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
- Details about these and many further changes can be found at:
https://www.postgresql.org/docs/10/static/release-10-13.html
https://www.postgresql.org/docs/10/static/release-10-14.html
postgresql-10 (10.12-0ubuntu0.18.04.1) bionic-security; urgency=medium
* New upstream release (LP: #1863108)
- A dump/restore is not required however, if you use the contrib/intarray
extension with a GiST index, and you rely on indexed searches for the <@
operator, see the release notes for details in regard to a related fix.
- Add missing permissions checks for ALTER ... DEPENDS ON EXTENSION.
Marking an object as dependent on an extension did not have any
privilege check whatsoever. This oversight allowed any user to mark
routines, triggers, materialized views, or indexes as droppable by
anyone able to drop an extension. Require that the calling user own the
specified object (and hence have privilege to drop it). (CVE-2020-1720)
- Details about these and many further changes can be found at:
https://www.postgresql.org/docs/10/static/release-10-11.html
https://www.postgresql.org/docs/10/static/release-10-12.html
postgresql-10 (10.10-0ubuntu0.18.04.1) bionic-security; urgency=medium
* SECURITY UPDATE: New upstream release (LP: #1839058)
- Require schema qualification to cast to a temporary type when using
functional cast syntax (CVE-2019-10208)
- Fix failure of ALTER TABLE ... ALTER COLUMN TYPE when altering multiple
columns' types in one command. This fixes a regression introduced in the
most recent minor releases
- Details about these and many further changes can be found at:
https://www.postgresql.org/docs/10/static/release-10-10.html
-- Colin Watson <email address hidden> Wed, 21 Jul 2021 15:24:58 +0100
Builds
Built packages
-
libecpg-compat3
older version of run-time library for ECPG programs
-
libecpg-dev
development files for ECPG (Embedded PostgreSQL for C)
-
libecpg6
run-time library for ECPG programs
-
libpgtypes3
shared library libpgtypes for PostgreSQL 10
-
libpq-dev
header files for libpq5 (PostgreSQL library)
-
libpq5
PostgreSQL C client library
-
postgresql-10
object-relational SQL database, version 10 server
-
postgresql-client-10
front-end programs for PostgreSQL 10
-
postgresql-doc-10
documentation for the PostgreSQL database management system
-
postgresql-plperl-10
PL/Perl procedural language for PostgreSQL 10
-
postgresql-plpython-10
PL/Python procedural language for PostgreSQL 10
-
postgresql-plpython3-10
PL/Python 3 procedural language for PostgreSQL 10
-
postgresql-pltcl-10
PL/Tcl procedural language for PostgreSQL 10
-
postgresql-server-dev-10
development files for PostgreSQL 10 server-side programming
Package files