Univention Bugzilla – Bug 56821
postgresql-11: Multiple issues (5.0)
Last modified: 2023-11-15 21:08:48 CET
New Debian postgresql-11 11.22-0+deb10u1 fixes: This update addresses the following issues: 11.21-0+deb10u2 (Mon, 02 Oct 2023 16:15:27 +0200) * Fix changelog of last upload, the original version mistakenly repeated the information from 11.20. 11.22-0+deb10u1 (Tue, 07 Nov 2023 14:50:52 +0100) * New upstream version. * This is expected to be the last PostgreSQL release in the 11.X series. Users are encouraged to update to a newer release branch soon. * Fix handling of unknown-type arguments in DISTINCT "any" aggregate functions (Tom Lane) This error led to a text-type value being interpreted as an unknown-type value (that is, a zero-terminated string) at runtime. This could result in disclosure of server memory following the text value. The PostgreSQL Project thanks Jingzhou Fu for reporting this problem. (CVE-2023-5868) * Detect integer overflow while computing new array dimensions (Tom Lane) When assigning new elements to array subscripts that are outside the current array bounds, an undetected integer overflow could occur in edge cases. Memory stomps that are potentially exploitable for arbitrary code execution are possible, and so is disclosure of server memory. The PostgreSQL Project thanks Pedro Gallegos for reporting this problem. (CVE-2023-5869) * Prevent the pg_signal_backend role from signalling background workers and autovacuum processes (Noah Misch, Jelte Fennema-Nio) The documentation says that pg_signal_backend cannot issue signals to superuser-owned processes. It was able to signal these background processes, though, because they advertise a role OID of zero. Treat that as indicating superuser ownership. The security implications of cancelling one of these process types are fairly small so far as the core code goes (we'll just start another one), but extensions might add background workers that are more vulnerable. Also ensure that the is_superuser parameter is set correctly in such processes. No specific security consequences are known for that oversight, but it might be significant for some extensions. The PostgreSQL Project thanks Hemanth Sandrana and Mahendrakar Srinivasarao for reporting this problem. (CVE-2023-5870) * Rebase debian/patches/libpgport-pkglibdir.
--- mirror/ftp/pool/main/p/postgresql-11/postgresql-11_11.21-0+deb10u1.dsc +++ apt/ucs_5.0-0-errata5.0-5/source/postgresql-11_11.22-0+deb10u1.dsc @@ -1,21 +1,68 @@ +11.22-0+deb10u1 [Tue, 07 Nov 2023 14:50:52 +0100] Christoph Berg <myon@debian.org>: + + * New upstream version. + + * This is expected to be the last PostgreSQL release in the 11.X series. + Users are encouraged to update to a newer release branch soon. + + * Fix handling of unknown-type arguments in DISTINCT "any" aggregate + functions (Tom Lane) + + This error led to a text-type value being interpreted as an unknown-type + value (that is, a zero-terminated string) at runtime. This could result + in disclosure of server memory following the text value. + + The PostgreSQL Project thanks Jingzhou Fu for reporting this problem. + (CVE-2023-5868) + + * Detect integer overflow while computing new array dimensions + (Tom Lane) + + When assigning new elements to array subscripts that are outside the + current array bounds, an undetected integer overflow could occur in edge + cases. Memory stomps that are potentially exploitable for arbitrary + code execution are possible, and so is disclosure of server memory. + + The PostgreSQL Project thanks Pedro Gallegos for reporting this problem. + (CVE-2023-5869) + + * Prevent the pg_signal_backend role from signalling background workers + and autovacuum processes (Noah Misch, Jelte Fennema-Nio) + + The documentation says that pg_signal_backend + cannot issue signals to superuser-owned processes. It was able to + signal these background processes, though, because they advertise a + role OID of zero. Treat that as indicating superuser ownership. + The security implications of cancelling one of these process types + are fairly small so far as the core code goes (we'll just start + another one), but extensions might add background workers that are + more vulnerable. + + Also ensure that the is_superuser parameter is set correctly in such + processes. No specific security consequences are known for that + oversight, but it might be significant for some extensions. + + The PostgreSQL Project thanks Hemanth Sandrana and Mahendrakar + Srinivasarao for reporting this problem. (CVE-2023-5870) + + * Rebase debian/patches/libpgport-pkglibdir. + +11.21-0+deb10u2 [Mon, 02 Oct 2023 16:15:27 +0200] Christoph Berg <myon@debian.org>: + + * Fix changelog of last upload, the original version mistakenly repeated the + information from 11.20. + 11.21-0+deb10u1 [Sun, 01 Oct 2023 22:05:23 +0200] Christoph Berg <myon@debian.org>: * New upstream version. - + Prevent CREATE SCHEMA from defeating changes in search_path - (Report and fix by Alexander Lakhin, CVE-2023-2454) - Within a CREATE SCHEMA command, objects in the prevailing search_path, - as well as those in the newly-created schema, would be visible even - within a called function or script that attempted to set a secure - search_path. This could allow any user having permission to create a - schema to hijack the privileges of a security definer function or - extension script. + + Disallow substituting a schema or owner name into an extension script if + the name contains a quote, backslash, or dollar sign (Noah Misch) - + Enforce row-level security policies correctly after inlining a - set-returning function (Report by Wolfgang Walther, CVE-2023-2455) - If a set-returning SQL-language function refers to a table having - row-level security policies, and it can be inlined into a calling query, - those RLS policies would not get enforced properly in some cases - involving re-using a cached plan under a different role. This could - allow a user to see or modify rows that should have been invisible. + This restriction guards against SQL-injection hazards for trusted + extensions. + The PostgreSQL Project thanks Micah Gate, Valerie Woolard, Tim + Carey-Smith, and Christoph Berg for reporting this problem. + (CVE-2023-39417) + <http://piuparts.knut.univention.de/5.0-5/#1041240649947557998>
OK: bug OK: yaml OK: announce_errata OK: patch OK: piuparts [5.0-5] 862063c747 Bug #56821: postgresql-11 11.22-0+deb10u1 doc/errata/staging/postgresql-11.yaml | 51 ++++++++++++++--------------------- 1 file changed, 20 insertions(+), 31 deletions(-) [5.0-5] b2193d76c7 Bug #56821: postgresql-11 11.22-0+deb10u1 doc/errata/staging/postgresql-11.yaml | 45 +++++++++++++++++++++++++++++++++++ 1 file changed, 45 insertions(+)
<https://errata.software-univention.de/#/?erratum=5.0x876>