{"affected":[{"ecosystem_specific":{"binaries":[{"libecpg6":"9.6.9-3.19.1","libpq5":"9.6.9-3.19.1","libpq5-32bit":"9.6.9-3.19.1","postgresql96":"9.6.9-3.19.1"}]},"package":{"ecosystem":"SUSE:Linux Enterprise Desktop 12 SP3","name":"postgresql96","purl":"pkg:rpm/suse/postgresql96&distro=SUSE%20Linux%20Enterprise%20Desktop%2012%20SP3"},"ranges":[{"events":[{"introduced":"0"},{"fixed":"9.6.9-3.19.1"}],"type":"ECOSYSTEM"}]},{"ecosystem_specific":{"binaries":[{"libecpg6":"9.6.9-3.19.1","libpq5":"9.6.9-3.19.1","libpq5-32bit":"9.6.9-3.19.1","postgresql96":"9.6.9-3.19.1"}]},"package":{"ecosystem":"SUSE:Linux Enterprise Desktop 12 SP3","name":"postgresql96-libs","purl":"pkg:rpm/suse/postgresql96-libs&distro=SUSE%20Linux%20Enterprise%20Desktop%2012%20SP3"},"ranges":[{"events":[{"introduced":"0"},{"fixed":"9.6.9-3.19.1"}],"type":"ECOSYSTEM"}]},{"ecosystem_specific":{"binaries":[{"postgresql96-devel":"9.6.9-3.19.1"}]},"package":{"ecosystem":"SUSE:Linux Enterprise Software Development Kit 12 SP3","name":"postgresql96-libs","purl":"pkg:rpm/suse/postgresql96-libs&distro=SUSE%20Linux%20Enterprise%20Software%20Development%20Kit%2012%20SP3"},"ranges":[{"events":[{"introduced":"0"},{"fixed":"9.6.9-3.19.1"}],"type":"ECOSYSTEM"}]},{"ecosystem_specific":{"binaries":[{"libecpg6":"9.6.9-3.19.1","libpq5":"9.6.9-3.19.1","libpq5-32bit":"9.6.9-3.19.1","postgresql96":"9.6.9-3.19.1","postgresql96-contrib":"9.6.9-3.19.1","postgresql96-docs":"9.6.9-3.19.1","postgresql96-server":"9.6.9-3.19.1"}]},"package":{"ecosystem":"SUSE:Linux Enterprise Server 12 SP3","name":"postgresql96","purl":"pkg:rpm/suse/postgresql96&distro=SUSE%20Linux%20Enterprise%20Server%2012%20SP3"},"ranges":[{"events":[{"introduced":"0"},{"fixed":"9.6.9-3.19.1"}],"type":"ECOSYSTEM"}]},{"ecosystem_specific":{"binaries":[{"libecpg6":"9.6.9-3.19.1","libpq5":"9.6.9-3.19.1","libpq5-32bit":"9.6.9-3.19.1","postgresql96":"9.6.9-3.19.1","postgresql96-contrib":"9.6.9-3.19.1","postgresql96-docs":"9.6.9-3.19.1","postgresql96-server":"9.6.9-3.19.1"}]},"package":{"ecosystem":"SUSE:Linux Enterprise Server 12 SP3","name":"postgresql96-libs","purl":"pkg:rpm/suse/postgresql96-libs&distro=SUSE%20Linux%20Enterprise%20Server%2012%20SP3"},"ranges":[{"events":[{"introduced":"0"},{"fixed":"9.6.9-3.19.1"}],"type":"ECOSYSTEM"}]},{"ecosystem_specific":{"binaries":[{"libecpg6":"9.6.9-3.19.1","libpq5":"9.6.9-3.19.1","libpq5-32bit":"9.6.9-3.19.1","postgresql96":"9.6.9-3.19.1","postgresql96-contrib":"9.6.9-3.19.1","postgresql96-docs":"9.6.9-3.19.1","postgresql96-server":"9.6.9-3.19.1"}]},"package":{"ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 12 SP3","name":"postgresql96","purl":"pkg:rpm/suse/postgresql96&distro=SUSE%20Linux%20Enterprise%20Server%20for%20SAP%20Applications%2012%20SP3"},"ranges":[{"events":[{"introduced":"0"},{"fixed":"9.6.9-3.19.1"}],"type":"ECOSYSTEM"}]},{"ecosystem_specific":{"binaries":[{"libecpg6":"9.6.9-3.19.1","libpq5":"9.6.9-3.19.1","libpq5-32bit":"9.6.9-3.19.1","postgresql96":"9.6.9-3.19.1","postgresql96-contrib":"9.6.9-3.19.1","postgresql96-docs":"9.6.9-3.19.1","postgresql96-server":"9.6.9-3.19.1"}]},"package":{"ecosystem":"SUSE:Linux Enterprise Server for SAP Applications 12 SP3","name":"postgresql96-libs","purl":"pkg:rpm/suse/postgresql96-libs&distro=SUSE%20Linux%20Enterprise%20Server%20for%20SAP%20Applications%2012%20SP3"},"ranges":[{"events":[{"introduced":"0"},{"fixed":"9.6.9-3.19.1"}],"type":"ECOSYSTEM"}]}],"aliases":[],"details":"\n  \nPostgreSQL was updated to 9.6.9 fixing bugs and security issues:\n\nRelease notes:\n\n- https://www.postgresql.org/about/news/1851/\n- https://www.postgresql.org/docs/current/static/release-9-6-9.html\n\n  A dump/restore is not required for those running 9.6.X.\n  However, if you use the adminpack extension, you should update\n  it as per the first changelog entry below.\n  Also, if the function marking mistakes mentioned in the second\n  and third changelog entries below affect you, you will want to\n  take steps to correct your database catalogs.\n\nSecurity issue fixed:\n\n- CVE-2018-1115: Remove public execute privilege\n  from contrib/adminpack's pg_logfile_rotate() function\n  pg_logfile_rotate() is a deprecated wrapper for the core\n  function pg_rotate_logfile(). When that function was changed\n  to rely on SQL privileges for access control rather than a\n  hard-coded superuser check, pg_logfile_rotate() should have\n  been updated as well, but the need for this was missed. Hence,\n  if adminpack is installed, any user could request a logfile\n  rotation, creating a minor security issue.\n  After installing this update, administrators should update\n  adminpack by performing ALTER EXTENSION adminpack UPDATE in\n  each database in which adminpack is installed. (bsc#1091610)\n\n","id":"SUSE-SU-2018:1695-1","modified":"2018-06-14T14:42:42Z","published":"2018-06-14T14:42:42Z","references":[{"type":"ADVISORY","url":"https://www.suse.com/support/update/announcement/2018/suse-su-20181695-1/"},{"type":"REPORT","url":"https://bugzilla.suse.com/1091610"},{"type":"WEB","url":"https://www.suse.com/security/cve/CVE-2018-1115"}],"related":["CVE-2018-1115"],"summary":"Security update for postgresql96","upstream":["CVE-2018-1115"]}