UbuntuUpdates.org

Package "postgresql-9.6"

Name: postgresql-9.6

Description:

object-relational SQL database, version 9.6 server

Latest version: 9.6.8-0ubuntu0.17.10
Release: artful (17.10)
Level: security
Repository: main
Homepage: http://www.postgresql.org/

Links

Save this URL for the latest version of "postgresql-9.6": https://www.ubuntuupdates.org/postgresql-9.6


Download "postgresql-9.6"


Other versions of "postgresql-9.6" in Artful

Repository Area Version
base universe 9.6.5-1
base main 9.6.5-1
security universe 9.6.8-0ubuntu0.17.10
updates main 9.6.9-0ubuntu0.17.10
updates universe 9.6.9-0ubuntu0.17.10
PPA: Postgresql 9.6.3-1.pgdg12.4+1
PPA: Postgresql 9.6.10-1.pgdg16.04+1
PPA: Postgresql 9.6.10-1.pgdg14.04+1
PPA: Postgresql 9.6.10-1.pgdg18.04+1

Packages in group

Deleted packages are displayed in grey.


Changelog

Version: 9.6.8-0ubuntu0.17.10 2018-03-06 11:07:47 UTC

  postgresql-9.6 (9.6.8-0ubuntu0.17.10) artful-security; urgency=medium

  * New upstream release (LP: #1752271)
    If you run an installation in which not all users are mutually
    trusting, or if you maintain an application or extension that is
    intended for use in arbitrary situations, it is strongly recommended
    that you read the documentation changes described in the first changelog
    entry below, and take suitable steps to ensure that your installation or
    code is secure.

    Also, the changes described in the second changelog entry below may
    cause functions used in index expressions or materialized views to fail
    during auto-analyze, or when reloading from a dump. After upgrading,
    monitor the server logs for such problems, and fix affected functions.

    - Document how to configure installations and applications to guard
      against search-path-dependent trojan-horse attacks from other users

      Using a search_path setting that includes any schemas writable by a
      hostile user enables that user to capture control of queries and then
      run arbitrary SQL code with the permissions of the attacked user. While
      it is possible to write queries that are proof against such hijacking,
      it is notationally tedious, and it's very easy to overlook holes.
      Therefore, we now recommend configurations in which no untrusted schemas
      appear in one's search path.
      (CVE-2018-1058)

    - Avoid use of insecure search_path settings in pg_dump and other client
      programs

      pg_dump, pg_upgrade, vacuumdb and other PostgreSQL-provided applications
      were themselves vulnerable to the type of hijacking described in the
      previous changelog entry; since these applications are commonly run by
      superusers, they present particularly attractive targets. To make them
      secure whether or not the installation as a whole has been secured,
      modify them to include only the pg_catalog schema in their search_path
      settings. Autovacuum worker processes now do the same, as well.

      In cases where user-provided functions are indirectly executed by these
      programs -- for example, user-provided functions in index expressions --
      the tighter search_path may result in errors, which will need to be
      corrected by adjusting those user-provided functions to not assume
      anything about what search path they are invoked under. That has always
      been good practice, but now it will be necessary for correct behavior.
      (CVE-2018-1058)

    - Details about other changes can be found at
      https://www.postgresql.org/docs/9.6/static/release-9-6-8.html

 -- Christian Ehrhardt <email address hidden> Wed, 28 Feb 2018 09:59:10 +0100

Source diff to previous version
1752271 New upstream microreleases 9.3.22, 9.5.12, 9.6.8 and 10.3
CVE-2018-1058 A flaw was found in the way Postgresql allowed a user to modify the behavior of a query for other users. An attacker with a user account could use th

Version: 9.6.7-0ubuntu0.17.10 2018-02-09 14:06:47 UTC

  postgresql-9.6 (9.6.7-0ubuntu0.17.10) artful-security; urgency=medium

  * New upstream release (LP: #1747676)
    - Ensure that all temporary files made by pg_upgrade are non-world-readable
      (CVE-2018-1053)
    - Change the behavior of contrib/cube's cube ~> int operator to make it
      compatible with KNN search.
      The meaning of the second argument (the dimension selector) has been
      changed to make it predictable which value is selected even when
      dealing with cubes of varying dimensionalities.
      This is an incompatible change, but since the point of the operator
      was to be used in KNN searches, it seems rather useless as-is.
      After installing this update, any expression indexes or materialized
      views using this operator will need to be reindexed/refreshed.
    - Details about other changes at full changelog:
      https://www.postgresql.org/docs/9.6/static/release-9-6-7.html

 -- Christian Ehrhardt <email address hidden> Tue, 06 Feb 2018 15:20:19 +0100

Source diff to previous version
1747676 New upstream microreleases 9.3.21, 9.5.11 and 9.6.7
CVE-2018-1053 Ensure that all temp files made during pg_upgrade are non-world-readable

Version: 9.6.6-0ubuntu0.17.10 2017-11-14 14:06:52 UTC

  postgresql-9.6 (9.6.6-0ubuntu0.17.10) artful-security; urgency=medium

  * New upstream release (LP: #1730661)
    - Previously, a race condition allowed some table rows to be omitted from
      the index. It may be necessary to reindex existing BRIN indexes to
      recover from past occurrences of this problem.
    - Details about other changes at full changelog:
      https://www.postgresql.org/docs/9.6/static/release-9-6-6.html

 -- Christian Ehrhardt <email address hidden> Tue, 07 Nov 2017 14:33:54 +0100

1730661 New upstream microreleases 9.3.20, 9.5.10 and 9.6.6



About   -   Send Feedback to @ubuntu_updates