[ubuntu/maverick-security] postgresql-8.4, postgresql-8.4_8.4.11-0ubuntu0.10.10_armel_translations.tar.gz, postgresql-8.4_8.4.11-0ubuntu0.10.10_powerpc_translations.tar.gz, postgresql-8.4_8.4.11-0ubuntu0.10.10_amd64_translations.tar.gz, postgresql-8.4_8.4.11-0ubuntu0.10.10_i386_translations.tar.gz 8.4.11-0ubuntu0.10.10 (Accepted)

Martin Pitt martin.pitt at ubuntu.com
Tue Feb 28 16:38:40 UTC 2012


postgresql-8.4 (8.4.11-0ubuntu0.10.10) maverick-security; urgency=low

  * New upstream bug fix/security release: (LP: #941912)
    - Require execute permission on the trigger function for "CREATE
      TRIGGER".
      This missing check could allow another user to execute a trigger
      function with forged input data, by installing it on a table he
      owns. This is only of significance for trigger functions marked
      SECURITY DEFINER, since otherwise trigger functions run as the
      table owner anyway. (CVE-2012-0866)
    - Remove arbitrary limitation on length of common name in SSL
      certificates.
      Both libpq and the server truncated the common name extracted from
      an SSL certificate at 32 bytes. Normally this would cause nothing
      worse than an unexpected verification failure, but there are some
      rather-implausible scenarios in which it might allow one
      certificate holder to impersonate another. The victim would have to
      have a common name exactly 32 bytes long, and the attacker would
      have to persuade a trusted CA to issue a certificate in which the
      common name has that string as a prefix. Impersonating a server
      would also require some additional exploit to redirect client
      connections. (CVE-2012-0867)
    - Convert newlines to spaces in names written in pg_dump comments.
      pg_dump was incautious about sanitizing object names that are
      emitted within SQL comments in its output script. A name containing
      a newline would at least render the script syntactically incorrect.
      Maliciously crafted object names could present a SQL injection risk
      when the script is reloaded. (CVE-2012-0868)
    - Fix btree index corruption from insertions concurrent with
      vacuuming.
      An index page split caused by an insertion could sometimes cause a
      concurrently-running "VACUUM" to miss removing index entries that
      it should remove. After the corresponding table rows are removed,
      the dangling index entries would cause errors (such as "could not
      read block N in file ...") or worse, silently wrong query results
      after unrelated rows are re-inserted at the now-free table
      locations. This bug has been present since release 8.2, but occurs
      so infrequently that it was not diagnosed until now. If you have
      reason to suspect that it has happened in your database, reindexing
      the affected index will fix things.
    - Update per-column permissions, not only per-table permissions, when
      changing table owner.
      Failure to do this meant that any previously granted column
      permissions were still shown as having been granted by the old
      owner. This meant that neither the new owner nor a superuser could
      revoke the now-untraceable-to-table-owner permissions.
    - Allow non-existent values for some settings in "ALTER USER/DATABASE
      SET".
      Allow default_text_search_config, default_tablespace, and
      temp_tablespaces to be set to names that are not known. This is
      because they might be known in another database where the setting
      is intended to be used, or for the tablespace cases because the
      tablespace might not be created yet. The same issue was previously
      recognized for search_path, and these settings now act like that
      one.
    - Avoid crashing when we have problems deleting table files
      post-commit.
      Dropping a table should lead to deleting the underlying disk files
      only after the transaction commits. In event of failure then (for
      instance, because of wrong file permissions) the code is supposed
      to just emit a warning message and go on, since it's too late to
      abort the transaction. This logic got broken as of release 8.4,
      causing such situations to result in a PANIC and an unrestartable
      database.
    - Track the OID counter correctly during WAL replay, even when it
      wraps around.
      Previously the OID counter would remain stuck at a high value until
      the system exited replay mode. The practical consequences of that
      are usually nil, but there are scenarios wherein a standby server
      that's been promoted to master might take a long time to advance
      the OID counter to a reasonable value once values are needed.
    - Fix regular expression back-references with - attached.
      Rather than enforcing an exact string match, the code would
      effectively accept any string that satisfies the pattern
      sub-expression referenced by the back-reference symbol.
      A similar problem still afflicts back-references that are embedded
      in a larger quantified expression, rather than being the immediate
      subject of the quantifier. This will be addressed in a future
      PostgreSQL release.
    - Fix recently-introduced memory leak in processing of inet/cidr
      values.
    - Fix dangling pointer after "CREATE TABLE AS"/"SELECT INTO" in a
      SQL-language function.
      In most cases this only led to an assertion failure in
      assert-enabled builds, but worse consequences seem possible.
    - Fix I/O-conversion-related memory leaks in plpgsql.
    - Improve pg_dump's handling of inherited table columns.
      pg_dump mishandled situations where a child column has a different
      default expression than its parent column. If the default is
      textually identical to the parent's default, but not actually the
      same (for instance, because of schema search path differences) it
      would not be recognized as different, so that after dump and
      restore the child would be allowed to inherit the parent's default.
      Child columns that are NOT NULL where their parent is not could
      also be restored subtly incorrectly.
    - Fix pg_restore's direct-to-database mode for INSERT-style table
      data.
      Direct-to-database restores from archive files made with
      "--inserts" or "--column-inserts" options fail when using
      pg_restore from a release dated September or December 2011, as a
      result of an oversight in a fix for another problem. The archive
      file itself is not at fault, and text-mode output is okay.
    - Allow AT option in ecpg DEALLOCATE statements.
      The infrastructure to support this has been there for awhile, but
      through an oversight there was still an error check rejecting the
      case.
    - Fix error in "contrib/intarray"'s int[] & int[] operator.
      If the smallest integer the two input arrays have in common is 1,
      and there are smaller values in either array, then 1 would be
      incorrectly omitted from the result.
    - Fix error detection in "contrib/pgcrypto"'s encrypt_iv() and
      decrypt_iv().
      These functions failed to report certain types of invalid-input
      errors, and would instead return random garbage values for
      incorrect input.
    - Fix one-byte buffer overrun in "contrib/test_parser".
      The code would try to read one more byte than it should, which
      would crash in corner cases. Since "contrib/test_parser" is only
      example code, this is not a security issue in itself, but bad
      example code is still bad.
    - Use __sync_lock_test_and_set() for spinlocks on ARM, if available.
      This function replaces our previous use of the SWPB instruction,
      which is deprecated and not available on ARMv6 and later. Reports
      suggest that the old code doesn't fail in an obvious way on recent
      ARM boards, but simply doesn't interlock concurrent accesses,
      leading to bizarre failures in multiprocess operation.
    - Use "-fexcess-precision=standard" option when building with gcc
      versions that accept it.
      This prevents assorted scenarios wherein recent versions of gcc
      will produce creative results.
    - Allow use of threaded Python on FreeBSD.
      Our configure script previously believed that this combination
      wouldn't work; but FreeBSD fixed the problem, so remove that error
      check.
  * Drop 00git_inet_cidr_unpack.patch, 04-armel-tas.patch: applied upstream.

Date: Mon, 27 Feb 2012 15:13:58 +0100
Changed-By: Martin Pitt <martin.pitt at ubuntu.com>
Maintainer: Ubuntu Developers <ubuntu-devel-discuss at lists.ubuntu.com>
https://launchpad.net/ubuntu/maverick/+source/postgresql-8.4/8.4.11-0ubuntu0.10.10
-------------- next part --------------
Format: 1.8
Date: Mon, 27 Feb 2012 15:13:58 +0100
Source: postgresql-8.4
Binary: libpq-dev libpq5 libecpg6 libecpg-dev libecpg-compat3 libpgtypes3 postgresql-8.4 postgresql-client-8.4 postgresql-server-dev-8.4 postgresql-doc-8.4 postgresql-contrib-8.4 postgresql-plperl-8.4 postgresql-plpython-8.4 postgresql-pltcl-8.4 postgresql postgresql-client postgresql-doc postgresql-contrib
Architecture: source
Version: 8.4.11-0ubuntu0.10.10
Distribution: maverick-security
Urgency: low
Maintainer: Ubuntu Developers <ubuntu-devel-discuss at lists.ubuntu.com>
Changed-By: Martin Pitt <martin.pitt at ubuntu.com>
Description: 
 libecpg-compat3 - older version of run-time library for ECPG programs
 libecpg-dev - development files for ECPG (Embedded PostgreSQL for C)
 libecpg6   - run-time library for ECPG programs
 libpgtypes3 - shared library libpgtypes for PostgreSQL 8.4
 libpq-dev  - header files for libpq5 (PostgreSQL library)
 libpq5     - PostgreSQL C client library
 postgresql - object-relational SQL database (supported version)
 postgresql-8.4 - object-relational SQL database, version 8.4 server
 postgresql-client - front-end programs for PostgreSQL (supported version)
 postgresql-client-8.4 - front-end programs for PostgreSQL 8.4
 postgresql-contrib - additional facilities for PostgreSQL (supported version)
 postgresql-contrib-8.4 - additional facilities for PostgreSQL
 postgresql-doc - documentation for the PostgreSQL database management system
 postgresql-doc-8.4 - documentation for the PostgreSQL database management system
 postgresql-plperl-8.4 - PL/Perl procedural language for PostgreSQL 8.4
 postgresql-plpython-8.4 - PL/Python procedural language for PostgreSQL 8.4
 postgresql-pltcl-8.4 - PL/Tcl procedural language for PostgreSQL 8.4
 postgresql-server-dev-8.4 - development files for PostgreSQL 8.4 server-side programming
Launchpad-Bugs-Fixed: 941912
Changes: 
 postgresql-8.4 (8.4.11-0ubuntu0.10.10) maverick-security; urgency=low
 .
   * New upstream bug fix/security release: (LP: #941912)
     - Require execute permission on the trigger function for "CREATE
       TRIGGER".
       This missing check could allow another user to execute a trigger
       function with forged input data, by installing it on a table he
       owns. This is only of significance for trigger functions marked
       SECURITY DEFINER, since otherwise trigger functions run as the
       table owner anyway. (CVE-2012-0866)
     - Remove arbitrary limitation on length of common name in SSL
       certificates.
       Both libpq and the server truncated the common name extracted from
       an SSL certificate at 32 bytes. Normally this would cause nothing
       worse than an unexpected verification failure, but there are some
       rather-implausible scenarios in which it might allow one
       certificate holder to impersonate another. The victim would have to
       have a common name exactly 32 bytes long, and the attacker would
       have to persuade a trusted CA to issue a certificate in which the
       common name has that string as a prefix. Impersonating a server
       would also require some additional exploit to redirect client
       connections. (CVE-2012-0867)
     - Convert newlines to spaces in names written in pg_dump comments.
       pg_dump was incautious about sanitizing object names that are
       emitted within SQL comments in its output script. A name containing
       a newline would at least render the script syntactically incorrect.
       Maliciously crafted object names could present a SQL injection risk
       when the script is reloaded. (CVE-2012-0868)
     - Fix btree index corruption from insertions concurrent with
       vacuuming.
       An index page split caused by an insertion could sometimes cause a
       concurrently-running "VACUUM" to miss removing index entries that
       it should remove. After the corresponding table rows are removed,
       the dangling index entries would cause errors (such as "could not
       read block N in file ...") or worse, silently wrong query results
       after unrelated rows are re-inserted at the now-free table
       locations. This bug has been present since release 8.2, but occurs
       so infrequently that it was not diagnosed until now. If you have
       reason to suspect that it has happened in your database, reindexing
       the affected index will fix things.
     - Update per-column permissions, not only per-table permissions, when
       changing table owner.
       Failure to do this meant that any previously granted column
       permissions were still shown as having been granted by the old
       owner. This meant that neither the new owner nor a superuser could
       revoke the now-untraceable-to-table-owner permissions.
     - Allow non-existent values for some settings in "ALTER USER/DATABASE
       SET".
       Allow default_text_search_config, default_tablespace, and
       temp_tablespaces to be set to names that are not known. This is
       because they might be known in another database where the setting
       is intended to be used, or for the tablespace cases because the
       tablespace might not be created yet. The same issue was previously
       recognized for search_path, and these settings now act like that
       one.
     - Avoid crashing when we have problems deleting table files
       post-commit.
       Dropping a table should lead to deleting the underlying disk files
       only after the transaction commits. In event of failure then (for
       instance, because of wrong file permissions) the code is supposed
       to just emit a warning message and go on, since it's too late to
       abort the transaction. This logic got broken as of release 8.4,
       causing such situations to result in a PANIC and an unrestartable
       database.
     - Track the OID counter correctly during WAL replay, even when it
       wraps around.
       Previously the OID counter would remain stuck at a high value until
       the system exited replay mode. The practical consequences of that
       are usually nil, but there are scenarios wherein a standby server
       that's been promoted to master might take a long time to advance
       the OID counter to a reasonable value once values are needed.
     - Fix regular expression back-references with - attached.
       Rather than enforcing an exact string match, the code would
       effectively accept any string that satisfies the pattern
       sub-expression referenced by the back-reference symbol.
       A similar problem still afflicts back-references that are embedded
       in a larger quantified expression, rather than being the immediate
       subject of the quantifier. This will be addressed in a future
       PostgreSQL release.
     - Fix recently-introduced memory leak in processing of inet/cidr
       values.
     - Fix dangling pointer after "CREATE TABLE AS"/"SELECT INTO" in a
       SQL-language function.
       In most cases this only led to an assertion failure in
       assert-enabled builds, but worse consequences seem possible.
     - Fix I/O-conversion-related memory leaks in plpgsql.
     - Improve pg_dump's handling of inherited table columns.
       pg_dump mishandled situations where a child column has a different
       default expression than its parent column. If the default is
       textually identical to the parent's default, but not actually the
       same (for instance, because of schema search path differences) it
       would not be recognized as different, so that after dump and
       restore the child would be allowed to inherit the parent's default.
       Child columns that are NOT NULL where their parent is not could
       also be restored subtly incorrectly.
     - Fix pg_restore's direct-to-database mode for INSERT-style table
       data.
       Direct-to-database restores from archive files made with
       "--inserts" or "--column-inserts" options fail when using
       pg_restore from a release dated September or December 2011, as a
       result of an oversight in a fix for another problem. The archive
       file itself is not at fault, and text-mode output is okay.
     - Allow AT option in ecpg DEALLOCATE statements.
       The infrastructure to support this has been there for awhile, but
       through an oversight there was still an error check rejecting the
       case.
     - Fix error in "contrib/intarray"'s int[] & int[] operator.
       If the smallest integer the two input arrays have in common is 1,
       and there are smaller values in either array, then 1 would be
       incorrectly omitted from the result.
     - Fix error detection in "contrib/pgcrypto"'s encrypt_iv() and
       decrypt_iv().
       These functions failed to report certain types of invalid-input
       errors, and would instead return random garbage values for
       incorrect input.
     - Fix one-byte buffer overrun in "contrib/test_parser".
       The code would try to read one more byte than it should, which
       would crash in corner cases. Since "contrib/test_parser" is only
       example code, this is not a security issue in itself, but bad
       example code is still bad.
     - Use __sync_lock_test_and_set() for spinlocks on ARM, if available.
       This function replaces our previous use of the SWPB instruction,
       which is deprecated and not available on ARMv6 and later. Reports
       suggest that the old code doesn't fail in an obvious way on recent
       ARM boards, but simply doesn't interlock concurrent accesses,
       leading to bizarre failures in multiprocess operation.
     - Use "-fexcess-precision=standard" option when building with gcc
       versions that accept it.
       This prevents assorted scenarios wherein recent versions of gcc
       will produce creative results.
     - Allow use of threaded Python on FreeBSD.
       Our configure script previously believed that this combination
       wouldn't work; but FreeBSD fixed the problem, so remove that error
       check.
   * Drop 00git_inet_cidr_unpack.patch, 04-armel-tas.patch: applied upstream.
Checksums-Sha1: 
 00351e78d7a929dbd003b5249b8a4cd926096a53 2628 postgresql-8.4_8.4.11-0ubuntu0.10.10.dsc
 b12084003937d8ed59287b6db2508e098ac52953 18178451 postgresql-8.4_8.4.11.orig.tar.gz
 6dddddb70fa05eb2115fa9f1e5b7376118559188 49581 postgresql-8.4_8.4.11-0ubuntu0.10.10.diff.gz
Checksums-Sha256: 
 e0a5964ba30149431d4145a0be9a7ce708b03868bb0b3d2c1960acae64e8d8e9 2628 postgresql-8.4_8.4.11-0ubuntu0.10.10.dsc
 5d430fe7b72ad466d477867bad8ee428b25eeefbd161560dc13ac73d77b3541d 18178451 postgresql-8.4_8.4.11.orig.tar.gz
 0fd5f2345725cc31ec79ca44d0ad357cd9364da91df7412cb183509a01d7e014 49581 postgresql-8.4_8.4.11-0ubuntu0.10.10.diff.gz
Files: 
 3c4fb17731a9d001c8d2daaca706c8aa 2628 database optional postgresql-8.4_8.4.11-0ubuntu0.10.10.dsc
 413b8ae9ae6e7f053e2a992e068af63e 18178451 database optional postgresql-8.4_8.4.11.orig.tar.gz
 2c066c41bc6b1f81537a1c3e87345c52 49581 database optional postgresql-8.4_8.4.11-0ubuntu0.10.10.diff.gz
Original-Maintainer: Martin Pitt <mpitt at debian.org>


More information about the Maverick-changes mailing list