The remote Redhat Enterprise Linux 8 host has packages installed that are affected by multiple vulnerabilities as referenced in the RHSA-2021:0167 advisory.

    PostgreSQL is an advanced object-relational database management system (DBMS).

    The following packages have been upgraded to a later upstream version: postgresql (9.6.20).

    Security Fix(es):

    * postgresql: Reconnection can downgrade connection security settings (CVE-2020-25694)

    * postgresql: Multiple features escape security restricted operation sandbox (CVE-2020-25695)

    * postgresql: TYPE in pg_temp executes arbitrary SQL during SECURITY DEFINER execution (CVE-2019-10208)

    * postgresql: Uncontrolled search path element in CREATE EXTENSION (CVE-2020-14350)

    * postgresql: psql's \gset allows overwriting specially treated variables (CVE-2020-25696)

    * postgresql: Selectivity estimators bypass row security policies (CVE-2019-10130)

    * postgresql: ALTER ... DEPENDS ON EXTENSION is missing authorization checks (CVE-2020-1720)

    For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and     other related information, refer to the CVE page(s) listed in the References section.

Tenable has extracted the preceding description block directly from the Red Hat Enterprise 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 Alibaba Cloud Linux 3 host has packages installed that are affected by multiple vulnerabilities as referenced in the ALINUX3-SA-2021:0017 advisory.

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

    CVE-2020-14349:
    It was found that PostgreSQL versions before 12.4, before 11.9 and before 10.14 did not properly sanitize     the search_path during logical replication. An authenticated attacker could use this flaw in an attack     similar to CVE-2018-1058, in order to execute arbitrary SQL command in the context of the user used for     replication.

    CVE-2020-14350:
    It was found that some PostgreSQL extensions did not use search_path safely in their installation script.
    An attacker with sufficient privileges could use this flaw to trick an administrator into executing a     specially crafted script, during the installation or update of such extension. This affects PostgreSQL     versions before 12.4, before 11.9, before 10.14, before 9.6.19, and before 9.5.23.

    CVE-2020-1720:
    A flaw was found in PostgreSQL's ALTER ... DEPENDS ON EXTENSION, where sub-commands did not perform     authorization checks. An authenticated attacker could use this flaw in certain configurations to perform     drop objects such as function, triggers, et al., leading to database corruption. This issue affects     PostgreSQL versions before 12.2, before 11.7, before 10.12 and before 9.6.17.

    CVE-2020-25694:
    A flaw was found in PostgreSQL versions before 13.1, before 12.5, before 11.10, before 10.15, before     9.6.20 and before 9.5.24. If a client application that creates additional database connections only reuses     the basic connection parameters while dropping security-relevant parameters, an opportunity for a man-in-     the-middle attack, or the ability to observe clear-text transmissions, could exist. The highest threat     from this vulnerability is to data confidentiality and integrity as well as system availability.

    CVE-2020-25695:
    A flaw was found in PostgreSQL versions before 13.1, before 12.5, before 11.10, before 10.15, before     9.6.20 and before 9.5.24. An attacker having permission to create non-temporary objects in at least one     schema can execute arbitrary SQL functions under the identity of a superuser. The highest threat from this     vulnerability is to data confidentiality and integrity as well as system availability.

    CVE-2020-25696:
    A flaw was found in the psql interactive terminal of PostgreSQL in versions before 13.1, before 12.5,     before 11.10, before 10.15, before 9.6.20 and before 9.5.24. If an interactive psql session uses \gset     when querying a compromised server, the attacker can execute arbitrary code as the operating system     account running psql. The highest threat from this vulnerability is to data confidentiality and integrity     as well as system availability.

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 remote Oracle Linux 8 host has packages installed that are affected by multiple vulnerabilities as referenced in the ELSA-2020-3669 advisory.

    [10.14-1]
    - Rebase to upstream release 10.14       Fixes RHBZ#1727803       Fixes RHBZ#1741489       Fixes RHBZ#1709196

    [10.13-1]
    - Rebase to upstream release 10.13       Fixes RHBZ#1727803       Fixes RHBZ#1741489       Fixes RHBZ#1709196

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 CentOS Linux 8 host has packages installed that are affected by multiple vulnerabilities as referenced in the CESA-2020:3669 advisory.

  - postgresql: Selectivity estimators bypass row security policies (CVE-2019-10130)

  - postgresql: Stack-based buffer overflow via setting a password (CVE-2019-10164)

  - postgresql: TYPE in pg_temp executes arbitrary SQL during SECURITY DEFINER execution (CVE-2019-10208)

  - postgresql: Uncontrolled search path element in logical replication (CVE-2020-14349)

  - postgresql: Uncontrolled search path element in CREATE EXTENSION (CVE-2020-14350)

  - postgresql: ALTER ... DEPENDS ON EXTENSION is missing authorization checks (CVE-2020-1720)

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

This update for postgresql96 fixes the following issues :

PostgreSQL was updated to version 9.6.17.

Security issue fixed :

CVE-2020-1720: Fixed a missing authorization check in the ALTER ...
DEPENDS ON extension (bsc#1163985).

Note that Tenable Network Security has extracted the preceding description block directly from the SUSE security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

The remote Redhat Enterprise Linux 8 host has packages installed that are affected by multiple vulnerabilities as referenced in the RHSA-2020:5619 advisory.

    PostgreSQL is an advanced object-relational database management system (DBMS).

    The following packages have been upgraded to a later upstream version: postgresql (9.6.20).

    Security Fix(es):

    * postgresql: Reconnection can downgrade connection security settings (CVE-2020-25694)

    * postgresql: Multiple features escape security restricted operation sandbox (CVE-2020-25695)

    * postgresql: TYPE in pg_temp executes arbitrary SQL during SECURITY DEFINER execution (CVE-2019-10208)

    * postgresql: Uncontrolled search path element in CREATE EXTENSION (CVE-2020-14350)

    * postgresql: psql's \gset allows overwriting specially treated variables (CVE-2020-25696)

    * postgresql: Selectivity estimators bypass row security policies (CVE-2019-10130)

    * postgresql: ALTER ... DEPENDS ON EXTENSION is missing authorization checks (CVE-2020-1720)

    For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and     other related information, refer to the CVE page(s) listed in the References section.

Tenable has extracted the preceding description block directly from the Red Hat Enterprise 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.

This update for postgresql96, postgresql10 and postgresql12 fixes the following issues :

postgresql10 was updated to 10.13 (bsc#1171924).

https://www.postgresql.org/about/news/2038/ https://www.postgresql.org/docs/10/release-10-13.html

postgresql10 was updated to 10.12 (CVE-2020-1720, bsc#1163985)

- https://www.postgresql.org/about/news/2011/

- https://www.postgresql.org/docs/10/release-10-12.html

postgresql10 was updated to 10.11 :

- https://www.postgresql.org/about/news/1994/

- https://www.postgresql.org/docs/10/release-10-11.html

postgresql12 was updated to 12.3 (bsc#1171924).

Bug Fixes and Improvements :

  - Several fixes for GENERATED columns, including an issue     where it was possible to crash or corrupt data in a     table when the output of the generated column was the     exact copy of a physical column on the table, e.g. if     the expression called a function which could return its     own input.

  - Several fixes for ALTER TABLE, including ensuring the     SET STORAGE directive is propagated to a table's     indexes.

  - Fix a potential race condition when using DROP OWNED BY     while another session is deleting the same objects.

  - Allow for a partition to be detached when it has     inherited ROW triggers.

  - Several fixes for REINDEX CONCURRENTLY, particularly     with issues when a REINDEX CONCURRENTLY operation fails.

  - Fix crash when COLLATE is applied to an uncollatable     type in a partition bound expression.

  - Fix performance regression in floating point     overflow/underflow detection.

  - Several fixes for full text search, particularly with     phrase searching.

  - Fix query-lifespan memory leak for a set-returning     function used in a query's FROM clause.

  - Several reporting fixes for the output of VACUUM     VERBOSE.

  - Allow input of type circle to accept the format (x,y),r,     which is specified in the documentation.

  - Allow for the get_bit() and set_bit() functions to not     fail on bytea strings longer than 256MB.

  - Avoid premature recycling of WAL segments during crash     recovery, which could lead to WAL segments being     recycled before being archived.

  - Avoid attempting to fetch nonexistent WAL files from     archive storage during recovery by skipping irrelevant     timelines.

  - Several fixes for logical replication and replication     slots.

  - Fix several race conditions in synchronous standby     management, including one that occurred when changing     the synchronous_standby_names setting.

  - Several fixes for GSSAPI support, include a fix for a     memory leak that occurred when using GSSAPI encryption.

  - Ensure that members of the pg_read_all_stats role can     read all statistics views.

  - Fix performance regression in     information_schema.triggers view.

  - Fix memory leak in libpq when using sslmode=verify-full.

  - Fix crash in psql when attempting to re-establish a     failed connection.

  - Allow tab-completion of the filename argument to \gx     command in psql.

  - Add pg_dump support for ALTER ... DEPENDS ON EXTENSION.

  - Several other fixes for pg_dump, which include dumping     comments on RLS policies and postponing restore of event     triggers until the end.

  - Ensure pg_basebackup generates valid tar files.

  - pg_checksums skips tablespace subdirectories that belong     to a different PostgreSQL major version

  - Several Windows compatibility fixes

This update also contains timezone tzdata release 2020a for DST law changes in Morocco and the Canadian Yukon, plus historical corrections for Shanghai. The America/Godthab zone has been renamed to America/Nuuk to reflect current English usage ; however, the old name remains available as a compatibility link. This also updates initdb's list of known Windows time zone names to include recent additions.

For more details, check out :

  - https://www.postgresql.org/docs/12/release-12-3.html

Other fixes :

  - Let postgresqlXX conflict with postgresql-noarch <     12.0.1 to get a clean and complete cutover to the new     packaging schema.

postgresql96 was updated to 9.6.19 :

  - CVE-2020-14350, boo#1175194: Make contrib modules'     installation scripts more secure.

  - https://www.postgresql.org/docs/9.6/release-9-6-19.html

  - Pack the /usr/lib/postgresql symlink only into the main     package.

  - Let postgresqlXX conflict with postgresql-noarch <     12.0.1 to get a clean and complete cutover to the new     packaging schema.

  - update to 9.6.18 (boo#1171924).
    https://www.postgresql.org/about/news/2038/     https://www.postgresql.org/docs/9.6/release-9-6-18.html

  - Unify the spec file to work across all current     PostgreSQL versions to simplify future maintenance.

  - Move from the 'libs' build flavour to a 'mini' package     that will only be used inside the build service and not     get shipped, to avoid confusion with the debuginfo     packages (boo#1148643).

  - update to 9.6.17 (CVE-2020-1720, boo#1163985)     https://www.postgresql.org/about/news/2011/     https://www.postgresql.org/docs/9.6/release-9-6-17.html

  - use and package the sha256 checksum for for source

  - update to 9.6.16:
    https://www.postgresql.org/about/news/1994/     https://www.postgresql.org/docs/9.6/release-9-6-16.html

  - add requires to the devel package for the libs that are     returned by pg_config --libs

  - Update to 9.6.15 :

  - https://www.postgresql.org/about/news/1960/

  - https://www.postgresql.org/docs/9.6/release-9-6-15.html

  - CVE-2019-10208, boo#1145092: TYPE in pg_temp executes     arbitrary SQL during SECURITY DEFINER execution.

  - Use FAT LTO objects in order to provide proper static     library.

  - Update to 9.6.14:
    https://www.postgresql.org/docs/9.6/release-9-6-14.html

  - Update to 9.6.13 :

  - https://www.postgresql.org/docs/9.6/release-9-6-13.html

  - https://www.postgresql.org/about/news/1939/

  - CVE-2019-10130, boo#1134689: Prevent row-level security     policies from being bypassed via selectivity estimators.

  - Make the server-devel package exclusive across versions.

  - Update to 9.6.12 :

  - https://www.postgresql.org/docs/9.6/release-9-6-12.html

  - https://www.postgresql.org/about/news/1920/

  - By default, panic instead of retrying after fsync()     failure, to avoid possible data corruption.

  - Numerous other bug fixes.

  - Overhaul README.SUSE

  - Update to 9.6.11 :

  - Numerous bug fixes, see the release notes:
    https://www.postgresql.org/docs/9.6/release-9-6-11.html

  - Remove unneeded library dependencies from PGXS.

  - add provides for the new server-devel package that will     be introduced in postgresql 11

  - Update to 9.6.10:
    https://www.postgresql.org/docs/current/static/release-9
    -6-10.html

  - CVE-2018-10915, boo#1104199: Fix failure to reset     libpq's state fully between connection attempts.

  - CVE-2018-10925, boo#1104202: Fix INSERT ... ON CONFLICT     UPDATE through a view that isn't just SELECT * FROM ...

  - Update to 9.6.9:
    https://www.postgresql.org/about/news/1851/     https://www.postgresql.org/docs/current/static/release-9
    -6-9.html A dump/restore is not required for those     running 9.6.X. However, if you use the adminpack     extension, you should update it as per the first     changelog entry below. Also, if the function marking     mistakes mentioned in the second and third changelog     entries below affect you, you will want to take steps to     correct your database catalogs.

  - CVE-2018-1115, boo#1091610: Remove public execute     privilege from contrib/adminpack's pg_logfile_rotate()     function pg_logfile_rotate() is a deprecated wrapper for     the core function pg_rotate_logfile(). When that     function was changed to rely on SQL privileges for     access control rather than a hard-coded superuser check,     pg_logfile_rotate() should have been updated as well,     but the need for this was missed. Hence, if adminpack is     installed, any user could request a logfile rotation,     creating a minor security issue. After installing this     update, administrators should update adminpack by     performing ALTER EXTENSION adminpack UPDATE in each     database in which adminpack is installed.

  - Fix incorrect volatility markings on a few built-in     functions

  - Fix incorrect parallel-safety markings on a few built-in     functions.

This update was imported from the SUSE:SLE-15-SP1:Update update project.

ID	Name	Product	Family	Published	Updated	Severity
145227	RHEL 8 : postgresql:9.6 (RHSA-2021:0167)	Nessus	Red Hat Local Security Checks	1/20/2021	11/7/2024	high
236609	Alibaba Cloud Linux 3 : 0017: postgresql:12 (ALINUX3-SA-2021:0017)	Nessus	Alibaba Cloud Linux Local Security Checks	5/14/2025	5/14/2025	high
140486	Oracle Linux 8 : postgresql:10 (ELSA-2020-3669)	Nessus	Oracle Linux Local Security Checks	9/10/2020	10/22/2024	high
145882	CentOS 8 : postgresql:10 (CESA-2020:3669)	Nessus	CentOS Local Security Checks	2/1/2021	1/24/2024	high
134295	SUSE SLES12 Security Update : postgresql96 (SUSE-SU-2020:0586-1)	Nessus	SuSE Local Security Checks	3/6/2020	1/13/2021	medium
144395	RHEL 8 : postgresql:9.6 (RHSA-2020:5619)	Nessus	Red Hat Local Security Checks	12/18/2020	3/15/2025	high
139655	openSUSE Security Update : postgresql96 / postgresql10 and postgresql12 (openSUSE-2020-1227)	Nessus	SuSE Local Security Checks	8/18/2020	2/26/2024	critical

Detections

Analytics

Plugins Search

high

high

high

high

medium

high

critical