SUSE-CU-2023:3823-1: Security update of suse/postgres

Wed Nov 22 19:20:20 UTC 2023

SUSE Container Update Advisory: suse/postgres
-----------------------------------------------------------------
Container Advisory ID : SUSE-CU-2023:3823-1
Container Tags        : suse/postgres:15 , suse/postgres:15-12.17 , suse/postgres:15.5 , suse/postgres:15.5-12.17 , suse/postgres:latest
Container Release     : 12.17
Severity              : important
Type                  : security
References            : 1122892 1179231 1206796 1209208 1216022 1216734 1216960 1216961
                        1216962 CVE-2023-5868 CVE-2023-5869 CVE-2023-5870 
-----------------------------------------------------------------

The container suse/postgres was updated. The following patches have been included in this update:

-----------------------------------------------------------------
Advisory ID: SUSE-SU-2023:4495-1
Released:    Tue Nov 21 08:39:58 2023
Summary:     Security update for postgresql, postgresql15, postgresql16
Type:        security
Severity:    important
References:  1122892,1179231,1206796,1209208,1216022,1216734,1216960,1216961,1216962,CVE-2023-5868,CVE-2023-5869,CVE-2023-5870
This update for postgresql, postgresql15, postgresql16 fixes the following issues:

This update ships postgresql 16.

Security issues fixed:

* CVE-2023-5868: Fix handling of unknown-type
  arguments in DISTINCT 'any' aggregate functions. 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. (bsc#1216962)
* CVE-2023-5869: Detect integer overflow while
  computing new array dimensions. 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. (bsc#1216961)
* CVE-2023-5870: Prevent the pg_signal_backend role
  from signalling background workers and autovacuum processes.
  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.
  (bsc#1216960)

Changes in postgresql16:

- Upgrade to 16.1:

  * https://www.postgresql.org/about/news/2715
  * https://www.postgresql.org/docs/16/release-16.html
  * https://www.postgresql.org/docs/16/release-16-1.html

- Overhaul postgresql-README.SUSE and move it from the binary
  package to the noarch wrapper package.
- Change the unix domain socket location from /var/run to /run.

Changes in postgresql15:

- Update to 15.5 https://www.postgresql.org/docs/15/release-15-5.html

- The libs and mini package are now provided by postgresql16.

- Overhaul postgresql-README.SUSE and move it from the binary
  package to the noarch wrapper package.
- Change the unix domain socket location from /var/run to /run.

Changes in postgresql:

- Interlock version and release of all noarch packages except for
  the postgresql-docs.
- bsc#1122892: Add a sysconfig variable for initdb.
- Overhaul postgresql-README.SUSE and move it from the binary
  package to the noarch wrapper package.
- bsc#1179231: Add an explanation for the /tmp -> /run/postgresql
  move and permission change.
- Add postgresql-README as a separate source file.
- bsc#1209208: Drop hard dependency on systemd
- bsc#1206796: Refine the distinction of where to use sysusers and
  use bcond to have the expression only in one place.

The following package changes have been done:

- libxml2-2-2.10.3-150500.5.11.1 updated
- libopenssl1_1-1.1.1l-150500.17.22.1 updated
- libopenssl1_1-hmac-1.1.1l-150500.17.22.1 updated
- libpq5-16.1-150200.5.7.1 updated
- postgresql-16-150500.10.3.2 updated
- postgresql15-15.5-150200.5.19.1 updated
- postgresql-server-16-150500.10.3.2 updated
- postgresql15-server-15.5-150200.5.19.1 updated
- container:sles15-image-15.0.0-36.5.57 updated
- dbus-1-1.12.2-150400.18.8.1 removed
- kbd-2.4.0-150400.5.6.1 removed
- kbd-legacy-2.4.0-150400.5.6.1 removed
- libapparmor1-3.0.4-150500.11.9.1 removed
- libargon2-1-0.0+git20171227.670229c-2.14 removed
- libcryptsetup12-2.4.3-150400.3.3.1 removed
- libcryptsetup12-hmac-2.4.3-150400.3.3.1 removed
- libdbus-1-3-1.12.2-150400.18.8.1 removed
- libdevmapper1_03-2.03.16_1.02.185-150500.7.6.1 removed
- libexpat1-2.4.4-150400.3.12.1 removed
- libffi7-3.2.1.git259-10.8 removed
- libip4tc2-1.8.7-1.1 removed
- libjson-c3-0.13-3.3.1 removed
- libkmod2-29-4.15.1 removed
- libp11-kit0-0.23.22-150500.6.1 removed
- libseccomp2-2.5.3-150400.2.4 removed
- libudev1-249.16-150400.8.35.5 removed
- netcfg-11.6-3.3.1 removed
- pam-config-1.1-3.3.1 removed
- pkg-config-0.29.2-1.436 removed
- systemd-249.16-150400.8.35.5 removed
- systemd-default-settings-0.7-3.2.1 removed
- systemd-default-settings-branding-SLE-0.7-3.2.1 removed
- systemd-presets-branding-SLE-15.1-150100.20.11.1 removed
- systemd-presets-common-SUSE-15-150500.20.3.1 removed