The version of Tencent Linux installed on the remote TencentOS Server 3 host is prior to tested version. It is, therefore, affected by multiple vulnerabilities as referenced in the TSSA-2024:1121 advisory.

    Package updates are available for TencentOS Server 3 that fix the following vulnerabilities:

    CVE-2024-10976:
    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-10978:
    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-10979:
    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.

Tenable has extracted the preceding description block directly from the Tencent Linux 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 Tencent Linux installed on the remote TencentOS Server 3 host is prior to tested version. It is, therefore, affected by multiple vulnerabilities as referenced in the TSSA-2024:1119 advisory.

    Package updates are available for TencentOS Server 3 that fix the following vulnerabilities:

    CVE-2024-10976:
    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-10978:
    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-10979:
    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.

Tenable has extracted the preceding description block directly from the Tencent Linux 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 Oracle Linux 9 host has packages installed that are affected by multiple vulnerabilities as referenced in the ELSA-2024-10788 advisory.

    - Fixes: CVE-2024-10976 CVE-2024-10978 CVE-2024-10979
    - Fixes: CVE-2023-2454 CVE-2023-2455

Tenable has extracted the preceding description block directly from the Oracle Linux 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 AlmaLinux 8 host has packages installed that are affected by multiple vulnerabilities as referenced in the ALSA-2024:10785 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 AlmaLinux 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 AlmaLinux 9 host has packages installed that are affected by multiple vulnerabilities as referenced in the ALSA-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 AlmaLinux 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 AlmaLinux 8 host has packages installed that are affected by multiple vulnerabilities as referenced in the ALSA-2024:10832 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 AlmaLinux 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 Azure Linux 3.0 host is prior to tested version. It is, therefore, affected by a vulnerability as referenced in the CVE-2024-10976 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)

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

The remote Alibaba Cloud Linux 3 host has packages installed that are affected by multiple vulnerabilities as referenced in the ALINUX3-SA-2024:0270 advisory.

    Package updates are available for Alibaba Cloud Linux 3 that fix the following vulnerabilities:

    CVE-2024-10976:
    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-10978:
    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-10979:
    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.

Tenable has extracted the preceding description block directly from the Alibaba Cloud Linux 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 Tencent Linux installed on the remote TencentOS Server 3 host is prior to tested version. It is, therefore, affected by multiple vulnerabilities as referenced in the TSSA-2024:1120 advisory.

    Package updates are available for TencentOS Server 3 that fix the following vulnerabilities:

    CVE-2024-10976:
    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-10978:
    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-10979:
    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.

Tenable has extracted the preceding description block directly from the Tencent Linux 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 MiracleLinux 9 host has packages installed that are affected by multiple vulnerabilities as referenced in the AXSA:2024-9434:05 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 MiracleLinux 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 Debian 12 host has packages installed that are affected by multiple vulnerabilities as referenced in the dsa-5812 advisory.

    - -------------------------------------------------------------------------     Debian Security Advisory DSA-5812-1                   security@debian.org     https://www.debian.org/security/                       Moritz Muehlenhoff     November 15, 2024                     https://www.debian.org/security/faq
    - -------------------------------------------------------------------------

    Package        : postgresql-15     CVE ID         : CVE-2024-10976 CVE-2024-10977 CVE-2024-10978 CVE-2024-10979

    Multiple security issues were discovered in PostgreSQL, which may result in     the execution of arbitrary code, privilege escalation or log manipulation.

    For the stable distribution (bookworm), these problems have been fixed in     version 15.9-0+deb12u1.

    We recommend that you upgrade your postgresql-15 packages.

    For the detailed security status of postgresql-15 please refer to     its security tracker page at:
    https://security-tracker.debian.org/tracker/postgresql-15

    Further information about Debian Security Advisories, how to apply     these updates to your system and frequently asked questions can be     found at: https://www.debian.org/security/

    Mailing list: debian-security-announce@lists.debian.org

Tenable has extracted the preceding description block directly from the Debian 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 postgresql13 package has been released.

The version of Tencent Linux installed on the remote TencentOS Server 4 host is prior to tested version. It is, therefore, affected by multiple vulnerabilities as referenced in the TSSA-2024:0887 advisory.

    Package updates are available for TencentOS Server 4 that fix the following vulnerabilities:

    CVE-2024-10979:
    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-10978:
    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-10977:
    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-10976:
    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.

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

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

ID	名称	产品	系列	发布时间	最近更新时间	严重程度
238732	TencentOS Server 3: postgresql:15 (TSSA-2024:1121)	Nessus	Tencent Local Security Checks	2025/6/16	2025/12/4	high
239692	TencentOS Server 3: postgresql:13 (TSSA-2024:1119)	Nessus	Tencent Local Security Checks	2025/6/16	2025/12/4	high
212079	Oracle Linux 9 : postgresql:16 (ELSA-2024-10788)	Nessus	Oracle Linux Local Security Checks	2024/12/5	2025/9/9	high
212097	AlmaLinux 8 : postgresql:12 (ALSA-2024:10785)	Nessus	Alma Linux Local Security Checks	2024/12/5	2025/2/12	high
212100	AlmaLinux 9 : postgresql:15 (ALSA-2024:10787)	Nessus	Alma Linux Local Security Checks	2024/12/5	2025/2/12	high
212104	AlmaLinux 8 : postgresql:13 (ALSA-2024:10832)	Nessus	Alma Linux Local Security Checks	2024/12/5	2026/2/25	high
215871	Azure Linux 3.0 Security Update: postgresql (CVE-2024-10976)	Nessus	Azure Linux Local Security Checks	2025/2/10	2025/9/15	medium
236341	Alibaba Cloud Linux 3 : 0270: postgresql:13 (ALINUX3-SA-2024:0270)	Nessus	Alibaba Cloud Linux Local Security Checks	2025/5/14	2025/5/14	high
239635	TencentOS Server 3: postgresql:12 (TSSA-2024:1120)	Nessus	Tencent Local Security Checks	2025/6/16	2025/12/4	high
292295	MiracleLinux 9 : postgresql-13.18-1.el9_5 (AXSA:2024-9434:05)	Nessus	Miracle Linux Local Security Checks	2026/1/20	2026/1/20	high
211509	Debian dsa-5812 : libecpg-compat3 - security update	Nessus	Debian Local Security Checks	2024/11/18	2025/2/21	high
213423	Photon OS 4.0: Postgresql13 PHSA-2024-4.0-0720	Nessus	PhotonOS Local Security Checks	2024/12/30	2025/2/21	high
276368	TencentOS Server 4: postgresql (TSSA-2024:0887)	Nessus	Tencent Local Security Checks	2025/11/20	2025/11/20	high

检测

插件搜索

high

high

high

high

high

high

medium

high

high

high

high

high

high