CVE-2018-10925

It was discovered that PostgreSQL versions before 10.5, 9.6.10, 9.5.14, 9.4.19, and 9.3.24 failed to properly check authorization on certain statements involved with "INSERT ... ON CONFLICT DO UPDATE". An attacker with "CREATE TABLE" privileges could exploit this to read arbitrary bytes server memory. If the attacker also had certain "INSERT" and limited "UPDATE" privileges to a particular table, they could exploit this to update other columns in the same table.

It was discovered that PostgreSQL versions before 10.5, 9.6.10, 9.5.14, 9.4.19, and 9.3.24 failed to properly check authorization on certain statements involved with "INSERT ... ON CONFLICT DO UPDATE". An attacker with "CREATE TABLE" privileges could exploit this to read arbitrary bytes server memory. If the attacker also had certain "INSERT" and limited "UPDATE" privileges to a particular table, they could exploit this to update other columns in the same table.

A flaw was found in the way Postgresql allowed a user to modify the behavior of a query for other users. An attacker with a user account could use this flaw to execute code with the permissions of superuser in the database (CVE-2018-1058).

Postgresql 9.6.x before 9.6.9 is vulnerable in the adminpack extension, the pg_catalog.pg_logfile_rotate() function doesn't follow the same ACLs than pg_rorate_logfile. If the adminpack is added to a database, an attacker able to connect to it could exploit this to force log rotation (CVE-2018-1115).

Andrew Krasichkov discovered that libpq did not reset all its connection state during reconnects (CVE-2018-10915).

It was discovered that some "CREATE TABLE" statements could disclose server memory (CVE-2018-10925).

Fully fixing these security issues requires manual intervention. See the upstream advisories for details.

This update for postgresql96, postgresql10 and postgresql12 fixes the following issues:

postgresql10 was updated to 10.13 (bsc#1171924).

https://www.postgresql.org/about/news/2038/ https://www.postgresql.org/docs/10/release-10-13.html

postgresql10 was updated to 10.12 (CVE-2020-1720, bsc#1163985)

• https://www.postgresql.org/about/news/2011/
• https://www.postgresql.org/docs/10/release-10-12.html

postgresql10 was updated to 10.11:

• https://www.postgresql.org/about/news/1994/
• https://www.postgresql.org/docs/10/release-10-11.html

postgresql12 was updated to 12.3 (bsc#1171924).

Bug Fixes and Improvements:

• Several fixes for GENERATED columns, including an issue where it was possible to crash or corrupt data in a table when the output of the generated column was the exact copy of a physical column on the table, e.g. if the expression called a function which could return its own input.
• Several fixes for ALTER TABLE, including ensuring the SET STORAGE directive is propagated to a table's indexes.
• Fix a potential race condition when using DROP OWNED BY while another session is deleting the same objects.
• Allow for a partition to be detached when it has inherited ROW triggers.
• Several fixes for REINDEX CONCURRENTLY, particularly with issues when a REINDEX CONCURRENTLY operation fails.
• Fix crash when COLLATE is applied to an uncollatable type in a partition bound expression.
• Fix performance regression in floating point overflow/underflow detection.
• Several fixes for full text search, particularly with phrase searching.
• Fix query-lifespan memory leak for a set-returning function used in a query's FROM clause.
• Several reporting fixes for the output of VACUUM VERBOSE.
• Allow input of type circle to accept the format (x,y),r, which is specified in the documentation.
• Allow for the get_bit() and set_bit() functions to not fail on bytea strings longer than 256MB.
• Avoid premature recycling of WAL segments during crash recovery, which could lead to WAL segments being recycled before being archived.
• Avoid attempting to fetch nonexistent WAL files from archive storage during recovery by skipping irrelevant timelines.
• Several fixes for logical replication and replication slots.
• Fix several race conditions in synchronous standby management, including one that occurred when changing the synchronous_standby_names setting.
• Several fixes for GSSAPI support, include a fix for a memory leak that occurred when using GSSAPI encryption.
• Ensure that members of the pg_read_all_stats role can read all statistics views.
• Fix performance regression in information_schema.triggers view.
• Fix memory leak in libpq when using sslmode=verify-full.
• Fix crash in psql when attempting to re-establish a failed connection.
• Allow tab-completion of the filename argument to \gx command in psql.
• Add pg_dump support for ALTER ... DEPENDS ON EXTENSION.
• Several other fixes for pg_dump, which include dumping comments on RLS policies and postponing restore of event triggers until the end.
• Ensure pg_basebackup generates valid tar files.
• pg_checksums skips tablespace subdirectories that belong to a different PostgreSQL major version
• Several Windows compatibility fixes

This update also contains timezone tzdata release 2020a for DST law changes in Morocco and the Canadian Yukon, plus historical corrections for Shanghai. The America/Godthab zone has been renamed to America/Nuuk to reflect current English usage ; however, the old name remains available as a compatibility link. This also updates initdb's list of known Windows time zone names to include recent additions.

For more details, check out:

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

Other fixes:

• Let postgresqlXX conflict with postgresql-noarch < 12.0.1 to get a clean and complete cutover to the new packaging schema.

postgresql96 was updated to 9.6.19:

• CVE-2020-14350, boo#1175194: Make contrib modules' installation scripts more…

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.

This update for postgresql10 fixes the following issues:

PostgreSQL 10 was updated to 10.5:

• https://www.postgresql.org/about/news/1851/

• https://www.postgresql.org/docs/current/static/release-10-5.html

  A dump/restore is not required for those running 10.X. However, if you use the adminpack extension, you should update it as per the first changelog entry below. Also, if the function marking mistakes mentioned in the second and third changelog entries below affect you, you will want to take steps to correct your database catalogs.

Security issues fixed:

• CVE-2018-1115: Remove public execute privilege from contrib/adminpack's pg_logfile_rotate() function pg_logfile_rotate() is a deprecated wrapper for the core function pg_rotate_logfile(). When that function was changed to rely on SQL privileges for access control rather than a hard-coded superuser check, pg_logfile_rotate() should have been updated as well, but the need for this was missed. Hence, if adminpack is installed, any user could request a logfile rotation, creating a minor security issue. After installing this update, administrators should update adminpack by performing ALTER EXTENSION adminpack UPDATE in each database in which adminpack is installed (bsc#1091610).
• CVE-2018-10915: libpq failed to properly reset its internal state between connections. If an affected version of libpq was used with 'host' or 'hostaddr' connection parameters from untrusted input, attackers could have bypassed client-side connection security features, obtain access to higher privileged connections or potentially cause other impact SQL injection, by causing the PQescape() functions to malfunction (bsc#1104199)
• CVE-2018-10925: Add missing authorization check on certain statements involved with 'INSERT ... ON CONFLICT DO UPDATE'. An attacker with 'CREATE TABLE' privileges could have exploited this to read arbitrary bytes server memory. If the attacker also had certain 'INSERT' and limited 'UPDATE' privileges to a particular table, they could have exploited this to update other columns in the same table (bsc#1104202).

This update for postgresql96 to 9.6.10 fixes the following issues:

These security issues were fixed:

• CVE-2018-10915: libpq failed to properly reset its internal state between connections. If an affected version of libpq was used with 'host' or 'hostaddr' connection parameters from untrusted input, attackers could have bypassed client-side connection security features, obtain access to higher privileged connections or potentially cause other impact SQL injection, by causing the PQescape() functions to malfunction (bsc#1104199)
• CVE-2018-10925: Add missing authorization check on certain statements involved with 'INSERT ... ON CONFLICT DO UPDATE'. An attacker with 'CREATE TABLE' privileges could have exploited this to read arbitrary bytes server memory. If the attacker also had certain 'INSERT' and limited 'UPDATE' privileges to a particular table, they could have exploited this to update other columns in the same table (bsc#1104202)

For addition details please see https://www.postgresql.org/docs/current/static/release-9-6-10.html

Andrew Krasichkov discovered that the PostgreSQL client library incorrectly reset its internal state between connections. A remote attacker could possibly use this issue to bypass certain client-side connection security features. This issue only affected Ubuntu 16.04 LTS and Ubuntu 18.04 LTS. (CVE-2018-10915)

It was discovered that PostgreSQL incorrectly checked authorization on certain statements. A remote attacker could possibly use this issue to read arbitrary server memory or alter certain data. (CVE-2018-10925)