SUSE-RU-2024:0632-1: Recommended update for postgresql

Published Feb 27, 2024
ยท
Updated

This update for postgresql fixes the following issues: Require fillup package to properly create the config file (bsc#1219340)

Affected Software

53 affected componentsFixes available
All of the following
SUSE openSUSE Leap 15.3 (noarch)
Any of the following
suse/postgresql-test<16-150300.10.21.1
16-150300.10.21.1
suse/postgresql-server-devel<16-150300.10.21.1
16-150300.10.21.1
suse/postgresql-pltcl<16-150300.10.21.1
16-150300.10.21.1
suse/postgresql-llvmjit<16-150300.10.21.1
16-150300.10.21.1
suse/postgresql-server<16-150300.10.21.1
16-150300.10.21.1
suse/postgresql-plpython<16-150300.10.21.1
16-150300.10.21.1
suse/postgresql-docs<16-150300.10.21.1
16-150300.10.21.1
suse/postgresql-llvmjit-devel<16-150300.10.21.1
16-150300.10.21.1
suse/postgresql-devel<16-150300.10.21.1
16-150300.10.21.1
suse/postgresql-plperl<16-150300.10.21.1
16-150300.10.21.1
suse/postgresql-contrib<16-150300.10.21.1
16-150300.10.21.1
suse/postgresql<16-150300.10.21.1
16-150300.10.21.1
All of the following
SUSE SUSE Linux Enterprise High Performance Computing LTSS 15 SP3 (noarch)
Any of the following
suse/postgresql-server-devel<16-150300.10.21.1
16-150300.10.21.1
suse/postgresql-pltcl<16-150300.10.21.1
16-150300.10.21.1
suse/postgresql-server<16-150300.10.21.1
16-150300.10.21.1
suse/postgresql-plpython<16-150300.10.21.1
16-150300.10.21.1
suse/postgresql-docs<16-150300.10.21.1
16-150300.10.21.1
suse/postgresql-devel<16-150300.10.21.1
16-150300.10.21.1
suse/postgresql-plperl<16-150300.10.21.1
16-150300.10.21.1
suse/postgresql-contrib<16-150300.10.21.1
16-150300.10.21.1
suse/postgresql<16-150300.10.21.1
16-150300.10.21.1
All of the following
SUSE SUSE Linux Enterprise Server 15 SP3 LTSS 15-SP3 (noarch)
Any of the following
suse/postgresql-pltcl<16-150300.10.21.1
16-150300.10.21.1
suse/postgresql-contrib<16-150300.10.21.1
16-150300.10.21.1
suse/postgresql-server<16-150300.10.21.1
16-150300.10.21.1
suse/postgresql-plpython<16-150300.10.21.1
16-150300.10.21.1
suse/postgresql-docs<16-150300.10.21.1
16-150300.10.21.1
suse/postgresql-devel<16-150300.10.21.1
16-150300.10.21.1
suse/postgresql-plperl<16-150300.10.21.1
16-150300.10.21.1
suse/postgresql-server-devel<16-150300.10.21.1
16-150300.10.21.1
suse/postgresql<16-150300.10.21.1
16-150300.10.21.1
All of the following
SUSE SUSE Linux Enterprise Server for SAP Applications 15 SP3 (noarch)
Any of the following
suse/postgresql-server-devel<16-150300.10.21.1
16-150300.10.21.1
suse/postgresql-pltcl<16-150300.10.21.1
16-150300.10.21.1
suse/postgresql-server<16-150300.10.21.1
16-150300.10.21.1
suse/postgresql-plpython<16-150300.10.21.1
16-150300.10.21.1
suse/postgresql-docs<16-150300.10.21.1
16-150300.10.21.1
suse/postgresql-devel<16-150300.10.21.1
16-150300.10.21.1
suse/postgresql-plperl<16-150300.10.21.1
16-150300.10.21.1
suse/postgresql-contrib<16-150300.10.21.1
16-150300.10.21.1
suse/postgresql<16-150300.10.21.1
16-150300.10.21.1
All of the following
SUSE SUSE Enterprise Storage 7.1 (noarch)
Any of the following
suse/postgresql-server-devel<16-150300.10.21.1
16-150300.10.21.1
suse/postgresql-pltcl<16-150300.10.21.1
16-150300.10.21.1
suse/postgresql-server<16-150300.10.21.1
16-150300.10.21.1
suse/postgresql-plpython<16-150300.10.21.1
16-150300.10.21.1
suse/postgresql-docs<16-150300.10.21.1
16-150300.10.21.1
suse/postgresql-devel<16-150300.10.21.1
16-150300.10.21.1
suse/postgresql-plperl<16-150300.10.21.1
16-150300.10.21.1
suse/postgresql-contrib<16-150300.10.21.1
16-150300.10.21.1
suse/postgresql<16-150300.10.21.1
16-150300.10.21.1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade suse/postgresql-test to a version that resolves this vulnerability.

    Fixed in 16-150300.10.21.1
  2. Upgrade

    Upgrade suse/postgresql-server-devel to a version that resolves this vulnerability.

    Fixed in 16-150300.10.21.1
  3. Upgrade

    Upgrade suse/postgresql-pltcl to a version that resolves this vulnerability.

    Fixed in 16-150300.10.21.1
  4. Upgrade

    Upgrade suse/postgresql-llvmjit to a version that resolves this vulnerability.

    Fixed in 16-150300.10.21.1
  5. Upgrade

    Upgrade suse/postgresql-server to a version that resolves this vulnerability.

    Fixed in 16-150300.10.21.1
  6. Upgrade

    Upgrade suse/postgresql-plpython to a version that resolves this vulnerability.

    Fixed in 16-150300.10.21.1
  7. Upgrade

    Upgrade suse/postgresql-docs to a version that resolves this vulnerability.

    Fixed in 16-150300.10.21.1
  8. Upgrade

    Upgrade suse/postgresql-llvmjit-devel to a version that resolves this vulnerability.

    Fixed in 16-150300.10.21.1
  9. Upgrade

    Upgrade suse/postgresql-devel to a version that resolves this vulnerability.

    Fixed in 16-150300.10.21.1
  10. Upgrade

    Upgrade suse/postgresql-plperl to a version that resolves this vulnerability.

    Fixed in 16-150300.10.21.1
  11. Upgrade

    Upgrade suse/postgresql-contrib to a version that resolves this vulnerability.

    Fixed in 16-150300.10.21.1
  12. Upgrade

    Upgrade suse/postgresql to a version that resolves this vulnerability.

    Fixed in 16-150300.10.21.1
  13. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Patch SUSE-2024-632=1
  14. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Patch SUSE-SLE-Product-HPC-15-SP3-LTSS-2024-632=1
  15. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Patch SUSE-SLE-Product-SLES-15-SP3-LTSS-2024-632=1
  16. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Patch SUSE-SLE-Product-SLES_SAP-15-SP3-2024-632=1
  17. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Patch SUSE-Storage-7.1-2024-632=1

Event History

Feb 27, 2024
Advisory Published
via SUSEยท12:30 PM

Frequently Asked Questions

1

Which PostgreSQL installations are most likely affected by this issue?

The update applies to installations using the listed SUSE PostgreSQL server, development, documentation, contrib, or procedural language packages. The issue concerns creation of the configuration file, so systems where package installation or update needs to create that file are the relevant cases.

2

What is the immediate mitigation if the update cannot be installed?

The provided information identifies the missing fillup package requirement as the cause of the configuration-file creation problem. No alternative workaround or manual remediation steps are provided.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
ยฉ 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203