cbe1d0d39e
PostgreSQL 12.4, 11.9, 10.14, 9.6.19, 9.5.23 Security Issues CVE-2020-14349: Uncontrolled search path element in logical replication. Versions Affected: 10 - 12. The PostgreSQL search_path setting determines schemas searched for tables, functions, operators, etc. The CVE-2018-1058 fix caused most PostgreSQL-provided client applications to sanitize search_path, but logical replication continued to leave search_path unchanged. Users of a replication publisher or subscriber database can create objects in the public schema and harness them to execute arbitrary SQL functions under the identity running replication, often a superuser. Installations having adopted a documented secure schema usage pattern are not vulnerable. The PostgreSQL project thanks Noah Misch for reporting this problem. CVE-2020-14350: Uncontrolled search path element in CREATE EXTENSION. Versions Affected: 9.5 - 12. The security team typically does not test unsupported versions, but this problem is quite old. When a superuser runs certain CREATE EXTENSION statements, users may be able to execute arbitrary SQL functions under the identity of that superuser. The attacker must have permission to create objects in the new extension's schema or a schema of a prerequisite extension. Not all extensions are vulnerable. In addition to correcting the extensions provided with PostgreSQL, the PostgreSQL Global Development Group is issuing guidance for third-party extension authors to secure their own work. Bug Fixes and Improvements This update also fixes over 50 bugs that were reported in the last several months. Some of these issues affect only version 12, but many affect all supported versions. Some of these fixes include: Fix edge cases in partition pruning involving multiple partition key columns with multiple or no constraining WHERE clauses. Several fixes for query planning and execution involving partitions. Fix for determining when to execute a column-specific UPDATE trigger on a logical replication subscriber. pg_replication_slot_advance() now updates the oldest xmin and LSN values, as the failure to do this could prevent resources (e.g. WAL files) from being cleaned up. Fix a performance regression in ts_headline(). Ensure that pg_read_file() and related functions read until EOF is reached, which fixes compatibility with pipes and other virtual files. Forbid numeric NaN values in jsonpath computations, which do not exist in SQL nor JSON. Several fixes for NaN inputs with aggregate functions. This fixes a change in PostgreSQL 12 where NaN values caused the following aggregates to emit values of 0 instead of NaN: corr(), covar_pop(), regr_intercept(), regr_r2(), regr_slope(), regr_sxx(), regr_sxy(), regr_syy(), stddev_pop(), and var_pop(). time and timetz values fractionally greater than 24:00:00 are now rejected. Several fixes for EXPLAIN, including a fix for reporting resource usage when a plan uses parallel workers with "Gather Merge" nodes. Fix timing of constraint revalidation in ALTER TABLE that could lead to odd errors. Fix for REINDEX CONCURRENTLY that could prevent old values from being included in future logical decoding output. Fix for LATERAL references that could potentially cause crashes during query execution. Use the collation specified for a query when estimating operator costs Fix conflict-checking anomalies in SERIALIZABLE transaction isolation mode. Ensure checkpointer process discards file sync requests when fsync is off Fix issue where pg_control could be written out with an inconsistent checksum, which could lead to the inability to restart the database if it crashed before the next pg_control update. Ensure that libpq continues to try to read from the database connection socket after a write failure, as this allows the connection to collect any final error messages from the server. Report out-of-disk-space errors properly in pg_dump and pg_basebackup Several fixes for pg_restore, including a fix for parallel restore on tables that have both table-level and column-level privileges. Fix for pg_upgrade to ensure it runs with vacuum_defer_cleanup_age set to 0. Fix how pg_rewind handles just-deleted files in the source data directory Fix failure to initialize local state correctly in contrib/dblink, which could lead to dblink_close() issuing an unexpected COMMIT on the remote server. Change contrib/amcheck to not report about deleted index pages that are empty, as this is normal during WAL replay.
19 lines
1.4 KiB
Text
19 lines
1.4 KiB
Text
$NetBSD: distinfo,v 1.21 2020/08/14 06:56:25 adam Exp $
|
|
|
|
SHA1 (postgresql-9.6.19.tar.bz2) = 72cde73fffd187bbd2e6c1de6d473cf5578754d2
|
|
RMD160 (postgresql-9.6.19.tar.bz2) = 5efcd29859fefa41cb880ef28b6b5fb082e1d67d
|
|
SHA512 (postgresql-9.6.19.tar.bz2) = 4d8d4a0e4645d71683a5fccb9cd88917e1870ba139f102e0ea82da9c8d1ad669f029e0feb6d409e2016dfd247229ec7daf04f7f2de3ab6c5b4053834ac244a26
|
|
Size (postgresql-9.6.19.tar.bz2) = 18880036 bytes
|
|
SHA1 (patch-config_missing) = c2d7d742922ba6861e7660c75b7b53f09e564813
|
|
SHA1 (patch-config_perl.m4) = 14c9564577d0df6f82ae0027aeada2f3a6a8f07c
|
|
SHA1 (patch-configure) = db34614cef013a91dc229be319e5f09c657c3f24
|
|
SHA1 (patch-contrib_dblink_dblink.c) = a6f87ab9f2c28a72608d70267b71bd77437b0921
|
|
SHA1 (patch-src_Makefile.global.in) = 2ab3affedc77b202f6749964287438d6179ca23a
|
|
SHA1 (patch-src_Makefile.shlib) = c2b7008ebcee1b7bfec46b9b35e91be2eef287ae
|
|
SHA1 (patch-src_backend_Makefile) = b70b38ea23af6cdde9d2349f2441a429078cfaca
|
|
SHA1 (patch-src_backend_utils_adt_datetime.c) = d1ea70986634d3bfb663eff789425252656e1289
|
|
SHA1 (patch-src_interfaces_ecpg_pgtypeslib_interval.c) = a15012ae34d4ecd1eb2bc29e4d2c40098ea236fd
|
|
SHA1 (patch-src_interfaces_libpq_Makefile) = 61bcf84eb69b6ec9faabab0b61913766f4b20f8c
|
|
SHA1 (patch-src_makefiles_Makefile.solaris) = 0168f5bc105ffc89d5db40907a08966d8465f5a0
|
|
SHA1 (patch-src_pl_plperl_GNUmakefile) = 6ee3e431f46ce5c2a94df499504b2b8bd458bbef
|
|
SHA1 (patch-src_pl_plperl_plperl.h) = 4c9c313bbc872802c57f3efd885a2ce6335d5d79
|