postgresql before versions 10.4, 9.6.9 is vulnerable in the adminpack extension, the pg_catalog.pg_logfile_rotate() function doesn't follow the same ACLs than pg_rorate_logfile. If the adminpack is added to a database, an attacker able to connect to it could exploit this to force log rotation.

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

  - postgresql: Too-permissive access control list on function pg_logfile_rotate() (CVE-2018-1115)

  - postgresql: Certain host connection parameters defeat client-side security defenses (CVE-2018-10915)

  - postgresql: Missing authorization and memory disclosure in INSERT ... ON CONFLICT DO UPDATE statements     (CVE-2018-10925)

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

The remote Redhat Enterprise Linux 6 / 7 host has packages installed that are affected by multiple vulnerabilities as referenced in the RHSA-2018:2566 advisory.

  - postgresql: Memory disclosure in JSON functions (CVE-2017-15098)

  - postgresql: INSERT ... ON CONFLICT DO UPDATE fails to enforce SELECT privileges (CVE-2017-15099)

  - postgresql: pg_upgrade creates file of sensitive metadata under prevailing umask (CVE-2018-1053)

  - postgresql: Uncontrolled search path element in pg_dump and other client applications (CVE-2018-1058)

  - postgresql: Too-permissive access control list on function pg_logfile_rotate() (CVE-2018-1115)

  - postgresql: Certain host connection parameters defeat client-side security defenses (CVE-2018-10915)

  - postgresql: Missing authorization and memory disclosure in INSERT ... ON CONFLICT DO UPDATE statements     (CVE-2018-10925)

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

According to the version of the postgresql packages installed, the EulerOS installation on the remote host is affected by the following vulnerability :

  - postgresql before versions 10.4, 9.6.9 is vulnerable in     the adminpack extension, the     pg_catalog.pg_logfile_rotate() function doesn't follow     the same ACLs than pg_rorate_logfile. If the adminpack     is added to a database, an attacker able to connect to     it could exploit this to force log     rotation.(CVE-2018-1115)

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

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.

This update for postgresql10 fixes the following issues :

PostgreSQL 10 was updated to 10.5 :

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

- https://www.postgresql.org/docs/current/static/release-10-5.html

  A dump/restore is not required for those running 10.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.

Security issues fixed :

  - CVE-2018-1115: 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 (bsc#1091610).

  - CVE-2018-10915: libpq failed to properly reset its     internal state between connections. If an affected     version of libpq was used with 'host' or 'hostaddr'     connection parameters from untrusted input, attackers     could have bypassed client-side connection security     features, obtain access to higher privileged connections     or potentially cause other impact SQL injection, by     causing the PQescape() functions to malfunction     (bsc#1104199)

  - CVE-2018-10925: Add missing authorization check on     certain statements involved with 'INSERT ... ON CONFLICT     DO UPDATE'. An attacker with 'CREATE TABLE' privileges     could have exploited this to read arbitrary bytes server     memory. If the attacker also had certain 'INSERT' and     limited 'UPDATE' privileges to a particular table, they     could have exploited this to update other columns in the     same table (bsc#1104202).

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

update to 10.4 per release notes:
https://www.postgresql.org/docs/10/static/release-10-4.html

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

This update for postgresql10 fixes the following issues :

PostgreSQL 10 was updated to 10.5 :

https://www.postgresql.org/about/news/1851/

https://www.postgresql.org/docs/current/static/release-10-5.html

A dump/restore is not required for those running 10.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.

Security issues fixed: CVE-2018-1115: 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 (bsc#1091610).

CVE-2018-10915: libpq failed to properly reset its internal state between connections. If an affected version of libpq was used with 'host' or 'hostaddr' connection parameters from untrusted input, attackers could have bypassed client-side connection security features, obtain access to higher privileged connections or potentially cause other impact SQL injection, by causing the PQescape() functions to malfunction (bsc#1104199)

CVE-2018-10925: Add missing authorization check on certain statements involved with 'INSERT ... ON CONFLICT DO UPDATE'. An attacker with 'CREATE TABLE' privileges could have exploited this to read arbitrary bytes server memory. If the attacker also had certain 'INSERT' and limited 'UPDATE' privileges to a particular table, they could have exploited this to update other columns in the same table (bsc#1104202).

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.

A vulnerability was found in libpq, the default PostgreSQL client library where libpq failed to properly reset its internal state between connections. If an affected version of libpq were used with 'host' or 'hostaddr' connection parameters from untrusted input, attackers could bypass client-side connection security features, obtain access to higher privileged connections or potentially cause other impact through SQL injection, by causing the PQescape() functions to malfunction.(CVE-2018-10915)

It was discovered that PostgreSQL failed to properly check authorization on certain statements involved with 'INSERT ... ON CONFLICT DO UPDATE'. An attacker with 'CREATE TABLE' privileges could exploit this to read arbitrary bytes server memory. If the attacker also had certain 'INSERT' and limited 'UPDATE' privileges to a particular table, they could exploit this to update other columns in the same table.(CVE-2018-10925)

It was found that pg_catalog.pg_logfile_rotate(), from the adminpack extension, did not follow the same ACLs than pg_rorate_logfile. If the adminpack is added to a database, an attacker able to connect to it could use this flaw to force log rotation.(CVE-2018-1115 )

The remote host is affected by the vulnerability described in GLSA-201810-08 (PostgreSQL: Multiple vulnerabilities)

    Multiple vulnerabilities have been discovered in PostgreSQL. Please       review the referenced CVE identifiers for details.
    In addition it was discovered that Gentoo&rsquo;s PostgreSQL installation       suffered from a privilege escalation vulnerability due to a runscript       which called OpenRC&rsquo;s checkpath() on a user controlled path and allowed       user running PostgreSQL to kill arbitrary processes via PID file       manipulation.
  Impact :

    A remote attacker could bypass certain client-side connection security       features, read arbitrary server memory or alter certain data.
    In addition, a local attacker could gain privileges or cause a Denial of       Service condition by  killing arbitrary processes.
  Workaround :

    There is no known workaround at this time.

This update for postgresql95 fixes the following issues :

  - Update to PostgreSQL 9.5.13 :

  - https://www.postgresql.org/docs/9.5/static/release-9-5-13.html A dump/restore is not required for those running 9.5.X.
However, if the function marking mistakes mentioned belowpg_logfile_rotate affect you, you will want to take steps to correct your database catalogs.
The functions query_to_xml, cursor_to_xml, cursor_to_xmlschema, query_to_xmlschema, and query_to_xml_and_xmlschema should be marked volatile because they execute user-supplied queries that might contain volatile operations. They were not, leading to a risk of incorrect query optimization. This has been repaired for new installations by correcting the initial catalog data, but existing installations will continue to contain the incorrect markings. Practical use of these functions seems to pose little hazard, but in case of trouble, it can be fixed by manually updating these functions' pg_proc entries, for example: ALTER FUNCTION pg_catalog.query_to_xml(text, boolean, boolean, text) VOLATILE.
    (Note that that will need to be done in each database of the installation.) Another option is to pg_upgrade the database to a version containing the corrected initial data.
Security issue fixed :

  - CVE-2018-1115: 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. (bsc#1091610)

PostgreSQL was updated to 9.6.9 fixing bugs and security issues :

Release notes :

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

Security issue fixed :

  - CVE-2018-1115: 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. (bsc#1091610)

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

PostgreSQL was updated to 9.6.9 fixing bugs and security issues:
Release notes :

- 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.
Security issue fixed :

  - CVE-2018-1115: 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. (bsc#1091610)

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 version of PostgreSQL installed on the remote host is 9.3.x prior to 9.3.23, 9.4.x prior to 9.4.18, 9.5.x prior to 9.5.13, or 9.6.x prior to 9.6.9, or 10.3.x.  As such, it is potentially affected by Insecure ACL Remote Issue

update to 9.6.9 per release notes https://www.postgresql.org/docs/9.6/static/release-9-6-9.html

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

update to 9.6.9 per release notes:
https://www.postgresql.org/docs/9.6/static/release-9-6-9.html

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

ID	Name	Product	Family	Severity
194127	RHEL 7 : rh-postgresql10-postgresql (RHSA-2018:2565)	Nessus	Red Hat Local Security Checks	critical
194117	RHEL 6 / 7 : rh-postgresql96-postgresql (RHSA-2018:2566)	Nessus	Red Hat Local Security Checks	critical
139979	EulerOS 2.0 SP8 : postgresql (EulerOS-SA-2020-1876)	Nessus	Huawei Local Security Checks	critical
139655	openSUSE Security Update : postgresql96 / postgresql10 and postgresql12 (openSUSE-2020-1227)	Nessus	SuSE Local Security Checks	critical
123286	openSUSE Security Update : postgresql10 (openSUSE-2019-659)	Nessus	SuSE Local Security Checks	critical
120220	Fedora 28 : postgresql (2018-08550a9006)	Nessus	Fedora Local Security Checks	critical
120090	SUSE SLED15 / SLES15 Security Update : postgresql10 (SUSE-SU-2018:2564-1)	Nessus	SuSE Local Security Checks	critical
119478	Amazon Linux AMI : postgresql96 (ALAS-2018-1119)	Nessus	Amazon Linux Local Security Checks	critical
118508	GLSA-201810-08 : PostgreSQL: Multiple vulnerabilities	Nessus	Gentoo Local Security Checks	critical
112269	openSUSE Security Update : postgresql10 (openSUSE-2018-955)	Nessus	SuSE Local Security Checks	critical
110955	openSUSE Security Update : postgresql95 (openSUSE-2018-696)	Nessus	SuSE Local Security Checks	critical
110588	openSUSE Security Update : postgresql96 (openSUSE-2018-638)	Nessus	SuSE Local Security Checks	critical
110548	SUSE SLED12 / SLES12 Security Update : postgresql96 (SUSE-SU-2018:1695-1)	Nessus	SuSE Local Security Checks	critical
110288	PostgreSQL 9.3 < 9.3.23 / 9.4 < 9.4.18 / 9.5 < 9.5.13 / 9.6 < 9.6.9 / 10.3 Insecure ACL Remote Issue	Nessus	Databases	critical
109972	Fedora 26 : postgresql (2018-bd6f9237b5)	Nessus	Fedora Local Security Checks	critical
109971	Fedora 27 : postgresql (2018-937c789f2a)	Nessus	Fedora Local Security Checks	critical

Detections

Analytics

CVE-2018-1115

critical

Tenable Plugins

critical

critical

critical

critical

critical

critical

critical

critical

critical

critical

critical

critical

critical

critical

critical

critical