Vulnerability Scan Report for registry.suse.com/suse/postgres:14-24.9
PostgreSQL 14 container based on the SLE Base Container Image.
Last scanned on: December 08, 2024 12:41
PostgreSQL 14 container based on the SLE Base Container Image.
Last scanned on: December 08, 2024 12:41
Package Name | Severity | Status | Description | Reference links | |
---|---|---|---|---|---|
postgresql14 | HIGH | fixed |
Security update for postgresql16 Vulnerability ID: SUSE-SU-2024:3169-1 Installed Version: 14.9-150200.5.29.1 Fixed Version: 14.13-150200.5.47.1 This update for postgresql16 fixes the following issues: - Upgrade to 14.13 (bsc#1229013) - CVE-2024-7348: PostgreSQL relation replacement during pg_dump executes arbitrary SQL. (bsc#1229013) |
||
postgresql14 | HIGH | fixed |
Security update for postgresql14 Vulnerability ID: SUSE-SU-2024:4176-1 Installed Version: 14.9-150200.5.29.1 Fixed Version: 14.15-150200.5.50.1 This update for postgresql14 fixes the following issues: - CVE-2024-10976: Ensure cached plans are marked as dependent on the calling role when RLS applies to a non-top-level table reference (bsc#1233323). - CVE-2024-10977: Make libpq discard error messages received during SSL or GSS protocol negotiation (bsc#1233325). - CVE-2024-10978: Fix unintended interactions between SET SESSION AUTHORIZATION and SET ROLE (bsc#1233326). - CVE-2024-10979: Prevent trusted PL/Perl code from changing environment variables (bsc#1233327). |
||
postgresql14-server | CRITICAL | fixed |
Security update for postgresql14 Vulnerability ID: SUSE-SU-2023:4479-1 Installed Version: 14.9-150200.5.29.1 Fixed Version: 14.10-150200.5.36.1 This update for postgresql14 fixes the following issues: 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) - update to 14.10: https://www.postgresql.org/docs/14/release-14-10.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. |
||
postgresql14-server | HIGH | fixed |
Security update for postgresql14 Vulnerability ID: SUSE-SU-2024:0552-1 Installed Version: 14.9-150200.5.29.1 Fixed Version: 14.11-150200.5.39.1 This update for postgresql14 fixes the following issues: Upgrade to 14.11: - CVE-2024-0985: Tighten security restrictions within REFRESH MATERIALIZED VIEW CONCURRENTLY (bsc#1219679). |
||
postgresql14-server | HIGH | fixed |
Security update for postgresql16 Vulnerability ID: SUSE-SU-2024:3169-1 Installed Version: 14.9-150200.5.29.1 Fixed Version: 14.13-150200.5.47.1 This update for postgresql16 fixes the following issues: - Upgrade to 14.13 (bsc#1229013) - CVE-2024-7348: PostgreSQL relation replacement during pg_dump executes arbitrary SQL. (bsc#1229013) |