openSUSE Security Update: Recommended update for postgresql95 ______________________________________________________________________________ Announcement ID: openSUSE-SU-2018:1900-1 Rating: moderate References: #1091610 Cross-References: CVE-2018-1115 Affected Products: openSUSE Leap 42.3 ______________________________________________________________________________ An update that fixes one vulnerability is now available. Description: 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) Patch Instructions: To install this openSUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch". Alternatively you can run the command listed for your product: - openSUSE Leap 42.3: zypper in -t patch openSUSE-2018-696=1 Package List: - openSUSE Leap 42.3 (i586 x86_64): postgresql95-9.5.13-2.9.1 postgresql95-contrib-9.5.13-2.9.1 postgresql95-contrib-debuginfo-9.5.13-2.9.1 postgresql95-debuginfo-9.5.13-2.9.1 postgresql95-debugsource-9.5.13-2.9.1 postgresql95-devel-9.5.13-2.9.1 postgresql95-devel-debuginfo-9.5.13-2.9.1 postgresql95-libs-debugsource-9.5.13-2.9.1 postgresql95-plperl-9.5.13-2.9.1 postgresql95-plperl-debuginfo-9.5.13-2.9.1 postgresql95-plpython-9.5.13-2.9.1 postgresql95-plpython-debuginfo-9.5.13-2.9.1 postgresql95-pltcl-9.5.13-2.9.1 postgresql95-pltcl-debuginfo-9.5.13-2.9.1 postgresql95-server-9.5.13-2.9.1 postgresql95-server-debuginfo-9.5.13-2.9.1 postgresql95-test-9.5.13-2.9.1 - openSUSE Leap 42.3 (noarch): postgresql95-docs-9.5.13-2.9.1 References: https://www.suse.com/security/cve/CVE-2018-1115.html https://bugzilla.suse.com/1091610