CVE-2019-10208

A flaw was discovered in postgresql versions 9.4.x before 9.4.24, 9.5.x before 9.5.19, 9.6.x before 9.6.15, 10.x before 10.10 and 11.x before 11.5 where arbitrary SQL statements can be executed given a suitable SECURITY DEFINER function. An attacker, with EXECUTE permission on the function, can execute arbitrary SQL as the owner of the function.

A flaw was discovered in postgresql versions 9.4.x before 9.4.24, 9.5.x before 9.5.19, 9.6.x before 9.6.15, 10.x before 10.10 and 11.x before 11.5 where arbitrary SQL statements can be executed given a suitable SECURITY DEFINER function. An attacker, with EXECUTE permission on the function, can execute arbitrary SQL as the owner of the function.

Updated postgresql packages fix security vulnerabilities:

Given a suitable SECURITY DEFINER function, an attacker can execute arbitrary SQL under the identity of the function owner. An attack requires EXECUTE permission on the function, which must itself contain a function call having inexact argument type match. For example, length('foo'::varchar) and length('foo') are inexact, while length('foo'::text) is exact (CVE-2019-10208).

In a database containing hypothetical, user-defined hash equality operators, an attacker could read arbitrary bytes of server memory. For an attack to become possible, a superuser would need to create unusual operators. It is possible for operators not purpose-crafted for attack to have the properties that enable an attack, but we are not aware of specific examples (CVE-2019-10209).

This update also fixes over 40 bugs that were reported in the last several months. See the upstream release notes for details.

This update for postgresql10 fixes the following issues:

Security issue fixed:

• CVE-2019-10208: Fixed arbitrary SQL execution via suitable SECURITY DEFINER function under the identity of the function owner (bsc#1145092).

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

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 postgresql94 fixes the following issues:

Security issue fixed:

• CVE-2019-10208: Fixed arbitrary SQL execution via suitable SECURITY DEFINER function under the identity of the function owner (bsc#1145092).

This update for postgresql96 fixes the following issues:

Security issue fixed:

• CVE-2019-10208: Fixed arbitrary SQL execution via suitable SECURITY DEFINER function under the identity of the function owner (bsc#1145092).

This update for postgresql10 fixes the following issues:

Security issue fixed:

• CVE-2019-10208: Fixed arbitrary SQL execution via suitable SECURITY DEFINER function under the identity of the function owner (bsc#1145092).

This update for postgresql10 fixes the following issues:

Security issue fixed:

• CVE-2019-10208: Fixed arbitrary SQL execution via suitable SECURITY DEFINER function under the identity of the function owner (bsc#1145092).

Tom Lane discovered that PostgreSQL did not properly restrict functions declared as "SECURITY DEFINER". An attacker could use this to execute arbitrary SQL with the permissions of the function owner. (CVE-2019-10208)

Andreas Seltenreich discovered that PostgreSQL did not properly handle user-defined hash equality operators. An attacker could use this to expose sensitive information (arbitrary PostgreSQL server memory). This issue only affected Ubuntu 19.04. (CVE-2019-10209)