It is, therefore, affected by multiple vulnerabilities as referenced in the ALAS2023-2024-787 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.

Detections

Analytics

Amazon Linux 2023 : postgresql15, postgresql15-contrib, postgresql15-llvmjit (ALAS2023-2024-787)

high Nessus Plugin ID 212335

Version 1.3

Version 1.1

Version 1.3 Feb 21, 2025, 11:26 AM IAVM reference Plugin Feed: 202502211126
Version 1.1 Dec 11, 2024, 3:04 PM New Plugin Feed: 202412111504