CVE-2020-25694

A flaw was found in PostgreSQL versions before 13.1, before 12.5, before 11.10, before 10.15, before 9.6.20 and before 9.5.24. If a client application that creates additional database connections only reuses the basic connection parameters while dropping security-relevant parameters, an opportunity for a man-in-the-middle attack, or the ability to observe clear-text transmissions, could exist. The highest threat from this vulnerability is to data confidentiality and integrity as well as system availability.

A flaw was found in PostgreSQL versions before 13.1, before 12.5, before 11.10, before 10.15, before 9.6.20 and before 9.5.24. If a client application that creates additional database connections only reuses the basic connection parameters while dropping security-relevant parameters, an opportunity for a man-in-the-middle attack, or the ability to observe clear-text transmissions, could exist. The highest threat from this vulnerability is to data confidentiality and integrity as well as system availability.

A flaw was found in PostgreSQL versions before 13.1, before 12.5, before 11.10, before 10.15, before 9.6.20 and before 9.5.24. If a client application that creates additional database connections only reuses the basic connection parameters while dropping security-relevant parameters, an opportunity for a man-in-the-middle attack, or the ability to observe clear-text transmissions, could exist. The highest threat from this vulnerability is to data confidentiality and integrity as well as system availability.

A flaw was found in PostgreSQL versions before 13.1, before 12.5, before 11.10, before 10.15, before 9.6.20 and before 9.5.24. If a client application that creates additional database connections only reuses the basic connection parameters while dropping security-relevant parameters, an opportunity for a man-in-the-middle attack, or the ability to observe clear-text transmissions, could exist. The highest threat from this vulnerability is to data confidentiality and integrity as well as system availability.

PostgreSQL is an advanced object-relational database management system (DBMS).

The following packages have been upgraded to a later upstream version: postgresql (12.5).

Security Fix(es):

• postgresql: Reconnection can downgrade connection security settings (CVE-2020-25694)

• postgresql: Multiple features escape "security restricted operation" sandbox (CVE-2020-25695)

• postgresql: Uncontrolled search path element in logical replication (CVE-2020-14349)

• postgresql: Uncontrolled search path element in CREATE EXTENSION (CVE-2020-14350)

• postgresql: psql's \gset allows overwriting specially treated variables (CVE-2020-25696)

• postgresql: ALTER ... DEPENDS ON EXTENSION is missing authorization checks (CVE-2020-1720)

For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.

A flaw was found in PostgreSQL versions before 13.1, before 12.5, before 11.10, before 10.15, before 9.6.20 and before 9.5.24. If a client application that creates additional database connections only reuses the basic connection parameters while dropping security-relevant parameters, an opportunity for a man-in-the-middle attack, or the ability to observe clear-text transmissions, could exist. The highest threat from this vulnerability is to data confidentiality and integrity as well as system availability.

PostgreSQL is an advanced object-relational database management system (DBMS).

The following packages have been upgraded to a later upstream version: postgresql (12.5).

Security Fix(es):

• postgresql: Reconnection can downgrade connection security settings (CVE-2020-25694)

• postgresql: Multiple features escape "security restricted operation" sandbox (CVE-2020-25695)

• postgresql: Uncontrolled search path element in logical replication (CVE-2020-14349)

• postgresql: Uncontrolled search path element in CREATE EXTENSION (CVE-2020-14350)

• postgresql: psql's \gset allows overwriting specially treated variables (CVE-2020-25696)

• postgresql: ALTER ... DEPENDS ON EXTENSION is missing authorization checks (CVE-2020-1720)

For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.

A flaw was found in PostgreSQL versions before 13.1, before 12.5, before 11.10, before 10.15, before 9.6.20 and before 9.5.24. If a client application that creates additional database connections only reuses the basic connection parameters while dropping security-relevant parameters, an opportunity for a man-in-the-middle attack, or the ability to observe clear-text transmissions, could exist. The highest threat from this vulnerability is to data confidentiality and integrity as well as system availability.

A flaw was found in PostgreSQL versions before 13.1, before 12.5, before 11.10, before 10.15, before 9.6.20 and before 9.5.24. If a client application that creates additional database connections only reuses the basic connection parameters while dropping security-relevant parameters, an opportunity for a man-in-the-middle attack, or the ability to observe clear-text transmissions, could exist. The highest threat from this vulnerability is to data confidentiality and integrity as well as system availability. (CVE-2020-25694)

A flaw was found in PostgreSQL versions before 13.1, before 12.5, before 11.10, before 10.15, before 9.6.20 and before 9.5.24. An attacker having permission to create non-temporary objects in at least one schema can execute arbitrary SQL functions under the identity of a superuser. The highest threat from this vulnerability is to data confidentiality and integrity as well as system availability. (CVE-2020-25695)

psql's \gset allows overwriting specially treated variables. (CVE-2020-25696)

This update for postgresql12 fixes the following issues:

• Upgrade to version 12.5:
  • CVE-2020-25695, bsc#1178666: Block DECLARE CURSOR ... WITH HOLD and firing of deferred triggers within index expressions and materialized view queries.
  • CVE-2020-25694, bsc#1178667: a) Fix usage of complex connection-string parameters in pg_dump, pg_restore, clusterdb, reindexdb, and vacuumdb. b) When psql's \connect command re-uses connection parameters, ensure that all non-overridden parameters from a previous connection string are re-used.
  • CVE-2020-25696, bsc#1178668: Prevent psql's \gset command from modifying specially-treated variables.
  • Fix recently-added timetz test case so it works when the USA is not observing daylight savings time.
  • https://www.postgresql.org/about/news/2111/
  • https://www.postgresql.org/docs/12/release-12-5.html

This update was imported from the SUSE:SLE-15-SP1:Update update project.

This update for postgresql10 fixes the following issues:

• Upgrade to version 10.15:
  • CVE-2020-25695, bsc#1178666: Block DECLARE CURSOR ... WITH HOLD and firing of deferred triggers within index expressions and materialized view queries.
  • CVE-2020-25694, bsc#1178667: a) Fix usage of complex connection-string parameters in pg_dump, pg_restore, clusterdb, reindexdb, and vacuumdb. b) When psql's \connect command re-uses connection parameters, ensure that all non-overridden parameters from a previous connection string are re-used.
  • CVE-2020-25696, bsc#1178668: Prevent psql's \gset command from modifying specially-treated variables.
  • Fix recently-added timetz test case so it works when the USA is not observing daylight savings time.
  • https://www.postgresql.org/about/news/2111/
  • https://www.postgresql.org/docs/10/release-10-15.html

This update was imported from the SUSE:SLE-15-SP1:Update update project.

This update for postgresql10 fixes the following issues:

• Upgrade to version 10.15:
  • CVE-2020-25695, bsc#1178666: Block DECLARE CURSOR ... WITH HOLD and firing of deferred triggers within index expressions and materialized view queries.
  • CVE-2020-25694, bsc#1178667: a) Fix usage of complex connection-string parameters in pg_dump, pg_restore, clusterdb, reindexdb, and vacuumdb. b) When psql's \connect command re-uses connection parameters, ensure that all non-overridden parameters from a previous connection string are re-used.
  • CVE-2020-25696, bsc#1178668: Prevent psql's \gset command from modifying specially-treated variables.
  • Fix recently-added timetz test case so it works when the USA is not observing daylight savings time.
  • https://www.postgresql.org/about/news/2111/
  • https://www.postgresql.org/docs/10/release-10-15.html

This update was imported from the SUSE:SLE-15-SP1:Update update project.

This update for postgresql12 fixes the following issues:

• Upgrade to version 12.5:
  • CVE-2020-25695, bsc#1178666: Block DECLARE CURSOR ... WITH HOLD and firing of deferred triggers within index expressions and materialized view queries.
  • CVE-2020-25694, bsc#1178667: a) Fix usage of complex connection-string parameters in pg_dump, pg_restore, clusterdb, reindexdb, and vacuumdb. b) When psql's \connect command re-uses connection parameters, ensure that all non-overridden parameters from a previous connection string are re-used.
  • CVE-2020-25696, bsc#1178668: Prevent psql's \gset command from modifying specially-treated variables.
  • Fix recently-added timetz test case so it works when the USA is not observing daylight savings time.
  • https://www.postgresql.org/about/news/2111/
  • https://www.postgresql.org/docs/12/release-12-5.html

This update was imported from the SUSE:SLE-15-SP1:Update update project.

This update for postgresql, postgresql13 fixes the following issues:

This update ships postgresql13.

Upgrade to version 13.1:

• CVE-2020-25695, bsc#1178666: Block DECLARE CURSOR ... WITH HOLD and firing of deferred triggers within index expressions and materialized view queries.
• CVE-2020-25694, bsc#1178667: a) Fix usage of complex connection-string parameters in pg_dump, pg_restore, clusterdb, reindexdb, and vacuumdb. b) When psql's \connect command re-uses connection parameters, ensure that all non-overridden parameters from a previous connection string are re-used.
• CVE-2020-25696, bsc#1178668: Prevent psql's \gset command from modifying specially-treated variables.
• Fix recently-added timetz test case so it works when the USA is not observing daylight savings time. (obsoletes postgresql-timetz.patch)
• https://www.postgresql.org/about/news/2111/
• https://www.postgresql.org/docs/13/release-13-1.html

Initial packaging of PostgreSQL 13:

• https://www.postgresql.org/about/news/2077/
• https://www.postgresql.org/docs/13/release-13.html

• bsc#1178961: %ghost the symlinks to pg_config and ecpg.

Changes in postgresql wrapper package:

• Bump major version to 13.
• We also transfer PostgreSQL 9.4.26 to the new package layout in SLE12-SP2 and newer. Reflect this in the conflict with postgresql94.
• Also conflict with PostgreSQL versions before 9.
• Conflicting with older versions is not limited to SLE.

This update was imported from the SUSE:SLE-15-SP2:Update update project.

These are all security issues fixed in the postgresql10-10.18-1.3 package on the GA media of openSUSE Tumbleweed.

These are all security issues fixed in the postgresql11-11.13-1.3 package on the GA media of openSUSE Tumbleweed.

These are all security issues fixed in the postgresql12-12.8-1.3 package on the GA media of openSUSE Tumbleweed.

These are all security issues fixed in the libecpg6-13.4-1.3 package on the GA media of openSUSE Tumbleweed.

These are all security issues fixed in the postgresql14-14.5-2.1 package on the GA media of openSUSE Tumbleweed.

These are all security issues fixed in the postgresql15-15.4-2.1 package on the GA media of openSUSE Tumbleweed.

These are all security issues fixed in the postgresql16-16.4-1.1 package on the GA media of openSUSE Tumbleweed.

These are all security issues fixed in the postgresql17-17.6-2.1 package on the GA media of openSUSE Tumbleweed.

This update for postgresql12 fixes the following issues:

• Upgrade to version 12.5:
  • CVE-2020-25695, bsc#1178666: Block DECLARE CURSOR ... WITH HOLD and firing of deferred triggers within index expressions and materialized view queries.
  • CVE-2020-25694, bsc#1178667: a) Fix usage of complex connection-string parameters in pg_dump, pg_restore, clusterdb, reindexdb, and vacuumdb. b) When psql's \connect command re-uses connection parameters, ensure that all non-overridden parameters from a previous connection string are re-used.
  • CVE-2020-25696, bsc#1178668: Prevent psql's \gset command from modifying specially-treated variables.
  • Fix recently-added timetz test case so it works when the USA is not observing daylight savings time.
  • https://www.postgresql.org/about/news/2111/
  • https://www.postgresql.org/docs/12/release-12-5.html

This update for postgresql10 fixes the following issues:

• Upgrade to version 10.15:
  • CVE-2020-25695, bsc#1178666: Block DECLARE CURSOR ... WITH HOLD and firing of deferred triggers within index expressions and materialized view queries.
  • CVE-2020-25694, bsc#1178667: a) Fix usage of complex connection-string parameters in pg_dump, pg_restore, clusterdb, reindexdb, and vacuumdb. b) When psql's \connect command re-uses connection parameters, ensure that all non-overridden parameters from a previous connection string are re-used.
  • CVE-2020-25696, bsc#1178668: Prevent psql's \gset command from modifying specially-treated variables.
  • Fix recently-added timetz test case so it works when the USA is not observing daylight savings time.
  • https://www.postgresql.org/about/news/2111/
  • https://www.postgresql.org/docs/10/release-10-15.html

This update for postgresql12 fixes the following issues:

• Upgrade to version 12.5:

  • CVE-2020-25695, bsc#1178666: Block DECLARE CURSOR ... WITH HOLD and firing of deferred triggers within index expressions and materialized view queries.
  • CVE-2020-25694, bsc#1178667: a) Fix usage of complex connection-string parameters in pg_dump, pg_restore, clusterdb, reindexdb, and vacuumdb. b) When psql's \connect command re-uses connection parameters, ensure that all non-overridden parameters from a previous connection string are re-used.
  • CVE-2020-25696, bsc#1178668: Prevent psql's \gset command from modifying specially-treated variables.
  • Fix recently-added timetz test case so it works when the USA is not observing daylight savings time.
  • https://www.postgresql.org/about/news/2111/
  • https://www.postgresql.org/docs/12/release-12-5.html

• Stop building the mini and lib packages as they are now coming from postgresql13.

This update for postgresql10 fixes the following issues:

Upgrade to version 10.15:

• CVE-2020-25695, bsc#1178666: Block DECLARE CURSOR ... WITH HOLD and firing of deferred triggers within index expressions and materialized view queries.
• CVE-2020-25694, bsc#1178667: a) Fix usage of complex connection-string parameters in pg_dump, pg_restore, clusterdb, reindexdb, and vacuumdb. b) When psql's \connect command re-uses connection parameters, ensure that all non-overridden parameters from a previous connection string are re-used.
• CVE-2020-25696, bsc#1178668: Prevent psql's \gset command from modifying specially-treated variables.
• https://www.postgresql.org/about/news/2111/
• https://www.postgresql.org/docs/10/release-10-15.html

Update to 10.14:

• CVE-2020-14349, bsc#1175193: Set a secure search_path in logical replication walsenders and apply workers
• CVE-2020-14350, bsc#1175194: Make contrib modules' installation scripts more secure.
• https://www.postgresql.org/docs/10/release-10-14.html

This update for postgresql10 fixes the following issues:

• Upgrade to version 10.15:
  • CVE-2020-25695, bsc#1178666: Block DECLARE CURSOR ... WITH HOLD and firing of deferred triggers within index expressions and materialized view queries.
  • CVE-2020-25694, bsc#1178667: a) Fix usage of complex connection-string parameters in pg_dump, pg_restore, clusterdb, reindexdb, and vacuumdb. b) When psql's \connect command re-uses connection parameters, ensure that all non-overridden parameters from a previous connection string are re-used.
  • CVE-2020-25696, bsc#1178668: Prevent psql's \gset command from modifying specially-treated variables.
  • Fix recently-added timetz test case so it works when the USA is not observing daylight savings time.
  • https://www.postgresql.org/about/news/2111/
  • https://www.postgresql.org/docs/10/release-10-15.html

This update for postgresql96 fixes the following issues:

Upgrade to version 9.6.20:

• CVE-2020-25695, bsc#1178666: Block DECLARE CURSOR ... WITH HOLD and firing of deferred triggers within index expressions and materialized view queries.
• CVE-2020-25694, bsc#1178667: a) Fix usage of complex connection-string parameters in pg_dump, pg_restore, clusterdb, reindexdb, and vacuumdb. b) When psql's \connect command re-uses connection parameters, ensure that all non-overridden parameters from a previous connection string are re-used.
• CVE-2020-25696, bsc#1178668: Prevent psql's \gset command from modifying specially-treated variables.
• https://www.postgresql.org/about/news/2111/
• https://www.postgresql.org/docs/9.6/release-9-6-20.html

Changes from 9.6.19:

• CVE-2020-14350, bsc#1175194: Make contrib modules installation

This update for postgresql12 fixes the following issues:

Upgrade to version 12.5:

• CVE-2020-25695, bsc#1178666: Block DECLARE CURSOR ... WITH HOLD and firing of deferred triggers within index expressions and materialized view queries.
• CVE-2020-25694, bsc#1178667: a) Fix usage of complex connection-string parameters in pg_dump, pg_restore, clusterdb, reindexdb, and vacuumdb. b) When psql's \connect command re-uses connection parameters, ensure that all non-overridden parameters from a previous connection string are re-used.
• CVE-2020-25696, bsc#1178668: Prevent psql's \gset command from modifying specially-treated variables.
• Fix recently-added timetz test case so it works when the USA is not observing daylight savings time. (obsoletes postgresql-timetz.patch)
• https://www.postgresql.org/about/news/2111/
• https://www.postgresql.org/docs/12/release-12-5.html

The previous postgresql12 update already addressed:

Update to 12.4:

• CVE-2020-14349, bsc#1175193: Set a secure search_path in logical replication walsenders and apply workers

• CVE-2020-14350, bsc#1175194: Make contrib modules' installation scripts more secure.

• https://www.postgresql.org/docs/12/release-12-4.html

This update for postgresql, postgresql13 fixes the following issues:

This update ships postgresql13.

Upgrade to version 13.1:

• CVE-2020-25695, bsc#1178666: Block DECLARE CURSOR ... WITH HOLD and firing of deferred triggers within index expressions and materialized view queries.
• CVE-2020-25694, bsc#1178667: a) Fix usage of complex connection-string parameters in pg_dump, pg_restore, clusterdb, reindexdb, and vacuumdb. b) When psql's \connect command re-uses connection parameters, ensure that all non-overridden parameters from a previous connection string are re-used.
• CVE-2020-25696, bsc#1178668: Prevent psql's \gset command from modifying specially-treated variables.
• Fix recently-added timetz test case so it works when the USA is not observing daylight savings time. (obsoletes postgresql-timetz.patch)
• https://www.postgresql.org/about/news/2111/
• https://www.postgresql.org/docs/13/release-13-1.html

Initial packaging of PostgreSQL 13:

• https://www.postgresql.org/about/news/2077/
• https://www.postgresql.org/docs/13/release-13.html

• bsc#1178961: %ghost the symlinks to pg_config and ecpg.

Changes in postgresql wrapper package:

• Bump major version to 13.
• We also transfer PostgreSQL 9.4.26 to the new package layout in SLE12-SP2 and newer. Reflect this in the conflict with postgresql94.
• Also conflict with PostgreSQL versions before 9.
• Conflicting with older versions is not limited to SLE.