The remote SUSE Linux SLES12 host has packages installed that are affected by multiple vulnerabilities as referenced in the SUSE-SU-2024:4052-1 advisory.

    This update ships postgresql17 , and fixes security issues with postgresql16:

    - bsc#1230423: Relax the dependency of extensions on the server       version from exact major.minor to greater or equal, after Tom       Lane confirmed on the PostgreSQL packagers list that ABI       stability is being taken care of between minor releases.

    - bsc#1219340: The last fix was not correct. Improve it by removing       the dependency again and call fillup only if it is installed.

    postgresql16 was updated to 16.6:
    * Repair ABI break for extensions that work with struct       ResultRelInfo.
    * Restore functionality of ALTER {ROLE|DATABASE} SET role.
    * Fix cases where a logical replication slot's restart_lsn could       go backwards.
    * Avoid deleting still-needed WAL files during pg_rewind.
    * Fix race conditions associated with dropping shared statistics       entries.
    * Count index scans in contrib/bloom indexes in the statistics       views, such as the pg_stat_user_indexes.idx_scan counter.
    * Fix crash when checking to see if an index's opclass options       have changed.
    * Avoid assertion failure caused by disconnected NFA sub-graphs       in regular expression parsing.
    * https://www.postgresql.org/docs/release/16.6/

    postgresql16 was updated to 16.5:

    * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as       dependent on the calling role when RLS applies to a       non-top-level table reference.
    * CVE-2024-10977, bsc#1233325: Make libpq discard error messages       received during SSL or GSS protocol negotiation.
    * CVE-2024-10978, bsc#1233326: Fix unintended interactions       between SET SESSION AUTHORIZATION and SET ROLE
    * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from       changing environment variables.
    * https://www.postgresql.org/about/news/p-2955/
    * https://www.postgresql.org/docs/release/16.5/

    - Don't build the libs and mini flavor anymore to hand over to       PostgreSQL 17.

      * https://www.postgresql.org/about/news/p-2910/

    postgresql17 is shipped in version 17.2:

    * CVE-2024-10976, bsc#1233323: Ensure cached plans are marked as       dependent on the calling role when RLS applies to a       non-top-level table reference.
    * CVE-2024-10977, bsc#1233325: Make libpq discard error messages       received during SSL or GSS protocol negotiation.
    * CVE-2024-10978, bsc#1233326: Fix unintended interactions       between SET SESSION AUTHORIZATION and SET ROLE
    * CVE-2024-10979, bsc#1233327: Prevent trusted PL/Perl code from       changing environment variables.
    * https://www.postgresql.org/about/news/p-2955/
    * https://www.postgresql.org/docs/release/17.1/
    * https://www.postgresql.org/docs/release/17.2/

    Upgrade to 17.2:

    * Repair ABI break for extensions that work with struct       ResultRelInfo.
    * Restore functionality of ALTER {ROLE|DATABASE} SET role.
    * Fix cases where a logical replication slot's restart_lsn could       go backwards.
    * Avoid deleting still-needed WAL files during pg_rewind.
    * Fix race conditions associated with dropping shared statistics       entries.
    * Count index scans in contrib/bloom indexes in the statistics       views, such as the pg_stat_user_indexes.idx_scan counter.
    * Fix crash when checking to see if an index's opclass options       have changed.
    * Avoid assertion failure caused by disconnected NFA sub-graphs       in regular expression parsing.

    Upgrade to 17.0:

    * New memory management system for VACUUM, which reduces memory       consumption and can improve overall vacuuming performance.
    * New SQL/JSON capabilities, including constructors, identity       functions, and the JSON_TABLE() function, which converts JSON       data into a table representation.
    * Various query performance improvements, including for       sequential reads using streaming I/O, write throughput under       high concurrency, and searches over multiple values in a btree       index.
    * Logical replication enhancements, including:
      + Failover control       + pg_createsubscriber, a utility that creates logical replicas         from physical standbys       + pg_upgrade now preserves replication slots on both publishers         and subscribers
    * New client-side connection option, sslnegotiation=direct, that       performs a direct TLS handshake to avoid a round-trip       negotiation.
    * pg_basebackup now supports incremental backup.
    * COPY adds a new option, ON_ERROR ignore, that allows a copy       operation to continue in the event of an error.
    * https://www.postgresql.org/about/news/p-2936/
    * https://www.postgresql.org/docs/17/release-17.html

Tenable has extracted the preceding description block directly from the SUSE security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The remote SUSE Linux SLES15 / SLES_SAP15 / openSUSE 15 host has packages installed that are affected by multiple vulnerabilities as referenced in the SUSE-SU-2024:4176-1 advisory.

    - 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).

Tenable has extracted the preceding description block directly from the SUSE security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The remote SUSE Linux SLES15 / SLES_SAP15 / openSUSE 15 host has packages installed that are affected by multiple vulnerabilities as referenced in the SUSE-SU-2024:4098-1 advisory.

    - 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).

Tenable has extracted the preceding description block directly from the SUSE security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The remote SUSE Linux SLES12 host has packages installed that are affected by multiple vulnerabilities as referenced in the SUSE-SU-2024:4114-1 advisory.

    - 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).

Tenable has extracted the preceding description block directly from the SUSE security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The remote RockyLinux 9 host has packages installed that are affected by multiple vulnerabilities as referenced in the RLSA-2024:10787 advisory.

    * postgresql: PostgreSQL SET ROLE, SET SESSION AUTHORIZATION reset to wrong user ID (CVE-2024-10978)

    * postgresql: PostgreSQL PL/Perl environment variable changes execute arbitrary code (CVE-2024-10979)

    * postgresql: PostgreSQL row security below e.g. subqueries disregards user ID changes (CVE-2024-10976)

Tenable has extracted the preceding description block directly from the RockyLinux security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The remote RockyLinux 8 host has packages installed that are affected by multiple vulnerabilities as referenced in the RLSA-2024:10831 advisory.

    * postgresql: PostgreSQL SET ROLE, SET SESSION AUTHORIZATION reset to wrong user ID (CVE-2024-10978)

    * postgresql: PostgreSQL PL/Perl environment variable changes execute arbitrary code (CVE-2024-10979)

    * postgresql: PostgreSQL row security below e.g. subqueries disregards user ID changes (CVE-2024-10976)

Tenable has extracted the preceding description block directly from the RockyLinux security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The version of libpq installed on the remote host is prior to 14.14-1. It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS2POSTGRESQL14-2024-015 advisory.

    Incomplete tracking in PostgreSQL of tables with row security allows a reused query to view or change     different rows from those intended.  CVE-2023-2455 and CVE-2016-2193 fixed most interaction between row     security and user ID changes.  They missed cases where a subquery, WITH query, security invoker view, or     SQL-language function references a table with a row-level security policy.  This has the same consequences     as the two earlier CVEs.  That is to say, it leads to potentially incorrect policies being applied in     cases where role-specific policies are used and a given query is planned under one role and then executed     under other roles.  This scenario can happen under security definer functions or when a common user and     query is planned initially and then re-used across multiple SET ROLEs.  Applying an incorrect policy may     permit a user to complete otherwise-forbidden reads and modifications.  This affects only databases that     have used CREATE POLICY to define a row security policy.  An attacker must tailor an attack to a     particular application's pattern of query plan reuse, user ID changes, and role-specific row security     policies.  Versions before PostgreSQL 17.1, 16.5, 15.9, 14.14, 13.17, and 12.21 are affected.
    (CVE-2024-10976)

    Client use of server error message in PostgreSQL allows a server not trusted under current SSL or GSS     settings to furnish arbitrary non-NUL bytes to the libpq application. For example, a man-in-the-middle     attacker could send a long error message that a human or screen-scraper user of psql mistakes for valid     query results. This is probably not a concern for clients where the user interface unambiguously indicates     the boundary between one error message and other text. Versions before PostgreSQL 17.1, 16.5, 15.9, 14.14,     13.17, and 12.21 are affected. (CVE-2024-10977)

    Incorrect privilege assignment in PostgreSQL allows a less-privileged application user to view or change     different rows from those intended.  An attack requires the application to use SET ROLE, SET SESSION     AUTHORIZATION, or an equivalent feature.  The problem arises when an application query uses parameters     from the attacker or conveys query results to the attacker.  If that query reacts to     current_setting('role') or the current user ID, it may modify or return data as though the session had not     used SET ROLE or SET SESSION AUTHORIZATION.  The attacker does not control which incorrect user ID     applies.  Query text from less-privileged sources is not a concern here, because SET ROLE and SET SESSION     AUTHORIZATION are not sandboxes for unvetted queries.  Versions before PostgreSQL 17.1, 16.5, 15.9, 14.14,     13.17, and 12.21 are affected. (CVE-2024-10978)

    Incorrect control of environment variables in PostgreSQL PL/Perl allows an unprivileged database user to     change sensitive process environment variables (e.g. PATH).  That often suffices to enable arbitrary code     execution, even if the attacker lacks a database server operating system user.  Versions before PostgreSQL     17.1, 16.5, 15.9, 14.14, 13.17, and 12.21 are affected. (CVE-2024-10979)

Tenable has extracted the preceding description block directly from the tested product security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

The version of postgresql installed on the remote host is prior to 14.14-1. It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS2POSTGRESQL14-2024-014 advisory.

    Incomplete tracking in PostgreSQL of tables with row security allows a reused query to view or change     different rows from those intended.  CVE-2023-2455 and CVE-2016-2193 fixed most interaction between row     security and user ID changes.  They missed cases where a subquery, WITH query, security invoker view, or     SQL-language function references a table with a row-level security policy.  This has the same consequences     as the two earlier CVEs.  That is to say, it leads to potentially incorrect policies being applied in     cases where role-specific policies are used and a given query is planned under one role and then executed     under other roles.  This scenario can happen under security definer functions or when a common user and     query is planned initially and then re-used across multiple SET ROLEs.  Applying an incorrect policy may     permit a user to complete otherwise-forbidden reads and modifications.  This affects only databases that     have used CREATE POLICY to define a row security policy.  An attacker must tailor an attack to a     particular application's pattern of query plan reuse, user ID changes, and role-specific row security     policies.  Versions before PostgreSQL 17.1, 16.5, 15.9, 14.14, 13.17, and 12.21 are affected.
    (CVE-2024-10976)

    Client use of server error message in PostgreSQL allows a server not trusted under current SSL or GSS     settings to furnish arbitrary non-NUL bytes to the libpq application. For example, a man-in-the-middle     attacker could send a long error message that a human or screen-scraper user of psql mistakes for valid     query results. This is probably not a concern for clients where the user interface unambiguously indicates     the boundary between one error message and other text. Versions before PostgreSQL 17.1, 16.5, 15.9, 14.14,     13.17, and 12.21 are affected. (CVE-2024-10977)

    Incorrect privilege assignment in PostgreSQL allows a less-privileged application user to view or change     different rows from those intended.  An attack requires the application to use SET ROLE, SET SESSION     AUTHORIZATION, or an equivalent feature.  The problem arises when an application query uses parameters     from the attacker or conveys query results to the attacker.  If that query reacts to     current_setting('role') or the current user ID, it may modify or return data as though the session had not     used SET ROLE or SET SESSION AUTHORIZATION.  The attacker does not control which incorrect user ID     applies.  Query text from less-privileged sources is not a concern here, because SET ROLE and SET SESSION     AUTHORIZATION are not sandboxes for unvetted queries.  Versions before PostgreSQL 17.1, 16.5, 15.9, 14.14,     13.17, and 12.21 are affected. (CVE-2024-10978)

    Incorrect control of environment variables in PostgreSQL PL/Perl allows an unprivileged database user to     change sensitive process environment variables (e.g. PATH).  That often suffices to enable arbitrary code     execution, even if the attacker lacks a database server operating system user.  Versions before PostgreSQL     17.1, 16.5, 15.9, 14.14, 13.17, and 12.21 are affected. (CVE-2024-10979)

Tenable has extracted the preceding description block directly from the tested product security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

An update of the postgresql14 package has been released.

An update of the postgresql15 package has been released.

ID	Name	Product	Family	Published	Updated	Severity
212542	SUSE SLES12 Security Update : postgresql, postgresql16, postgresql17 (SUSE-SU-2024:4052-1)	Nessus	SuSE Local Security Checks	12/12/2024	2/21/2025	high
212550	SUSE SLES15 / openSUSE 15 Security Update : postgresql14 (SUSE-SU-2024:4176-1)	Nessus	SuSE Local Security Checks	12/12/2024	2/21/2025	high
212559	SUSE SLES15 / openSUSE 15 Security Update : postgresql15 (SUSE-SU-2024:4098-1)	Nessus	SuSE Local Security Checks	12/12/2024	2/21/2025	high
212571	SUSE SLES12 Security Update : postgresql13 (SUSE-SU-2024:4114-1)	Nessus	SuSE Local Security Checks	12/12/2024	2/21/2025	high
213205	RockyLinux 9 : postgresql:15 (RLSA-2024:10787)	Nessus	Rocky Linux Local Security Checks	12/19/2024	2/12/2025	high
213210	RockyLinux 8 : postgresql:16 (RLSA-2024:10831)	Nessus	Rocky Linux Local Security Checks	12/19/2024	2/12/2025	high
213361	Amazon Linux 2 : libpq (ALASPOSTGRESQL14-2024-015)	Nessus	Amazon Linux Local Security Checks	12/23/2024	2/12/2025	high
213364	Amazon Linux 2 : postgresql (ALASPOSTGRESQL14-2024-014)	Nessus	Amazon Linux Local Security Checks	12/23/2024	2/21/2025	high
213424	Photon OS 4.0: Postgresql14 PHSA-2024-4.0-0720	Nessus	PhotonOS Local Security Checks	12/30/2024	2/21/2025	high
213425	Photon OS 4.0: Postgresql15 PHSA-2024-4.0-0720	Nessus	PhotonOS Local Security Checks	12/30/2024	2/21/2025	high

Detections

Analytics

Plugins Search

high

high

high

high

high

high

high

high

high

high