Summary
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 secure.
* https://www.postgresql.org/docs/9.6/release-9-6-19.html
- Pack the /usr/lib/postgresql symlink only into the main package.
- Let postgresqlXX conflict with postgresql-noarch < 12.0.1 to get
a clean and complete cutover to the new packaging schema.
- update to 9.6.18 (boo#1171924).
https://www.postgresql.org/about/news/2038/
https://www.postgresql.org/docs/9.6/release-9-6-18.html
- Unify the spec file to work across all current PostgreSQL
versions to simplify future maintenance.
- Move from the 'libs' build flavour to a 'mini' package that will
only be used inside the build service and not get shipped, to
avoid confusion with the debuginfo packages (boo#1148643).
- update to 9.6.17 (CVE-2020-1720, boo#1163985)
https://www.postgresql.org/about/news/2011/
https://www.postgresql.org/docs/9.6/release-9-6-17.html
- use and package the sha256 checksum for for source
- update to 9.6.16:
https://www.postgresql.org/about/news/1994/
https://www.postgresql.org/docs/9.6/release-9-6-16.html
- add requires to the devel package for the libs that are returned
by pg_config --libs
- Update to 9.6.15:
* https://www.postgresql.org/about/news/1960/
* https://www.postgresql.org/docs/9.6/release-9-6-15.html
* CVE-2019-10208, boo#1145092: TYPE in pg_temp executes arbitrary
SQL during SECURITY DEFINER execution.
- Use FAT LTO objects in order to provide proper static library.
- Update to 9.6.14:
https://www.postgresql.org/docs/9.6/release-9-6-14.html
- Update to 9.6.13:
* https://www.postgresql.org/docs/9.6/release-9-6-13.html
* https://www.postgresql.org/about/news/1939/
* CVE-2019-10130, boo#1134689: Prevent row-level security
policies from being bypassed via selectivity estimators.
- Make the server-devel package exclusive across versions.
- Update to 9.6.12:
* https://www.postgresql.org/docs/9.6/release-9-6-12.html
* https://www.postgresql.org/about/news/1920/
* By default, panic instead of retrying after fsync() failure
Fixed packages 4
| Release | Package | Fixed in |
|---|---|---|
| openSUSE · Leap 15.1 | postgresql | 12.0.1-lp151.6.9.1 |
| openSUSE · Leap 15.1 | postgresql10 | 10.13-lp151.2.14.1 |
| openSUSE · Leap 15.1 | postgresql12 | 12.3-lp151.2.1 |
| openSUSE · Leap 15.1 | postgresql96 | 9.6.19-lp151.3.3.1 |
Vulnerabilities 7
-
High 8.5
A vulnerability was found in libpq, the default PostgreSQL client library where libpq failed to properly reset its inte…
-
High 7.5
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…
-
High 7.1
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 aut…
-
Medium 4.2
postgresql before versions 10.4, 9.6.9 is vulnerable in the adminpack extension, the pg_catalog.pg_logfile_rotate() fun…
-
Low 3.1
A vulnerability was found in PostgreSQL versions 11.x up to excluding 11.3, 10.x up to excluding 10.8, 9.6.x up to, exc…
-
Low 3.1
A flaw was found in PostgreSQL's "ALTER ... DEPENDS ON EXTENSION", where sub-commands did not perform authorization che…
-
Unscored —
It was found that some PostgreSQL extensions did not use search_path safely in their installation script. An attacker w…
References
-
report
https://bugzilla.suse.com/1091610
-
report
https://bugzilla.suse.com/1104199
-
report
https://bugzilla.suse.com/1104202
-
report
https://bugzilla.suse.com/1134689
-
report
https://bugzilla.suse.com/1145092
-
report
https://bugzilla.suse.com/1148643
-
report
https://bugzilla.suse.com/1163985
-
report
https://bugzilla.suse.com/1171924
-
report
https://bugzilla.suse.com/1175194
-
web
https://www.suse.com/security/cve/CVE-2018-10915
-
web
https://www.suse.com/security/cve/CVE-2018-10925
-
web
https://www.suse.com/security/cve/CVE-2018-1115
-
web
https://www.suse.com/security/cve/CVE-2019-10130
-
web
https://www.suse.com/security/cve/CVE-2019-10208
-
web
https://www.suse.com/security/cve/CVE-2020-14350
-
web
https://www.suse.com/security/cve/CVE-2020-1720