UbuntuUpdates.org

Package "libecpg6"

Name: libecpg6

Description:

run-time library for ECPG programs

Latest version: 15.6-0ubuntu0.23.10.1
Release: mantic (23.10)
Level: updates
Repository: main
Head package: postgresql-15
Homepage: http://www.postgresql.org/

Links


Download "libecpg6"


Other versions of "libecpg6" in Mantic

Repository Area Version
base main 15.4-1ubuntu1
security main 15.6-0ubuntu0.23.10.1
PPA: Postgresql 9.4.1-1.pgdg10.4+1
PPA: Postgresql 9.6.3-1.pgdg12.4+1
PPA: Postgresql 11.3-1.pgdg14.04+1
PPA: Postgresql 13.3-1.pgdg16.04+1
PPA: Postgresql 16.3-1.pgdg20.04+1
PPA: Postgresql 15.3-1.pgdg18.04+1
PPA: Postgresql 16.3-1.pgdg22.04+1

Changelog

Version: 15.6-0ubuntu0.23.10.1 2024-02-26 16:07:02 UTC

  postgresql-15 (15.6-0ubuntu0.23.10.1) mantic-security; urgency=medium

  * New upstream version (LP: #2052850).

    + A dump/restore is not required for those running 15.X.

    + However, one bug was fixed that could have resulted in corruption of
      GIN indexes during concurrent updates. If you suspect such
      corruption, reindex affected indexes after installing this update.

    + Also, if you are upgrading from a version earlier than 15.5, see
      those release notes as well please.

    + Tighten security restrictions within REFRESH MATERIALIZED
      VIEW CONCURRENTLY (Heikki Linnakangas)

      One step of a concurrent refresh command was run under weak security
      restrictions. If a materialized view's owner could persuade a
      superuser or other high-privileged user to perform a concurrent
      refresh on that view, the view's owner could control code executed
      with the privileges of the user running REFRESH.
      Fix things so that all user-determined code is run as the view's
      owner, as expected.

      The only known exploit for this error does not work in PostgreSQL
      16.0 and later, so it may be that v16 is not vulnerable in practice.

      The PostgreSQL Project thanks Pedro Gallegos for reporting this
      problem.
      (CVE-2024-0985)

    + Details about these and many further changes can be found at:
      https://www.postgresql.org/docs/15/release-15-6.html.

  * d/postgresql-15.NEWS: Update.

 -- Sergio Durigan Junior <email address hidden> Fri, 09 Feb 2024 19:43:36 -0500

Source diff to previous version
2052850 New upstream microreleases 12.18, 14.11, 15.6 and 16.2
CVE-2024-0985 Late privilege drop in REFRESH MATERIALIZED VIEW CONCURRENTLY in PostgreSQL allows an object creator to execute arbitrary SQL functions as the comman

Version: 15.5-0ubuntu0.23.10.1 2023-12-06 18:06:59 UTC

  postgresql-15 (15.5-0ubuntu0.23.10.1) mantic-security; urgency=medium

  * New upstream version (LP: #2040469).

    + A dump/restore is not required for those running 15.X.

    + However, several mistakes have been discovered that could lead to
      certain types of indexes yielding wrong search results or being
      unnecessarily inefficient. It is advisable to REINDEX
      potentially-affected indexes after installing this update.

    + Also, if you are upgrading from a version earlier than 15.4, see
      those release notes as well please.

    + Fix handling of unknown-type arguments in DISTINCT "any" aggregate
      functions (Tom Lane)

      This error led to a text-type value being interpreted as an unknown-type
      value (that is, a zero-terminated string) at runtime. This could result
      in disclosure of server memory following the text value.
      (CVE-2023-5868)

    + Detect integer overflow while computing new array dimensions (Tom Lane)

      When assigning new elements to array subscripts that are outside the
      current array bounds, an undetected integer overflow could occur in edge
      cases. Memory stomps that are potentially exploitable for arbitrary code
      execution are possible, and so is disclosure of server memory.
      (CVE-2023-5869)

    + Prevent the pg_signal_backend role from signalling background workers
      and autovacuum processes (Noah Misch, Jelte Fennema-Nio)

      The documentation says that pg_signal_backend cannot issue signals to
      superuser-owned processes. It was able to signal these background
      processes, though, because they advertise a role OID of zero. Treat that
      as indicating superuser ownership. The security implications of
      cancelling one of these process types are fairly small so far as the
      core code goes (we'll just start another one), but extensions might add
      background workers that are more vulnerable.

      Also ensure that the is_superuser parameter is set correctly in such
      processes. No specific security consequences are known for that
      oversight, but it might be significant for some extensions.
      (CVE-2023-5870)

    + Fix misbehavior during recursive page split in GiST index build
      (Heikki Linnakangas)

      Fix a case where the location of a page downlink was incorrectly
      tracked, and introduce some logic to allow recovering from such
      situations rather than silently doing the wrong thing. This error could
      result in incorrect answers from subsequent index searches. It may be
      advisable to reindex all GiST indexes after installing this update.

    + Prevent de-duplication of btree index entries for interval columns
      (Noah Misch)

      There are interval values that are distinguishable but compare equal,
      for example 24:00:00 and 1 day. This breaks assumptions made by btree
      de-duplication, so interval columns need to be excluded from
      de-duplication. This oversight can cause incorrect results from
      index-only scans. Moreover, after updating amcheck will report an error
      for almost all such indexes. Users should reindex any btree indexes on
      interval columns.

    + Process date values more sanely in BRIN datetime_minmax_multi_ops
      indexes (Tomas Vondra)

      The distance calculation for dates was backward, causing poor decisions
      about which entries to merge. The index still produces correct results,
      but is much less efficient than it should be. Reindexing BRIN
      minmax_multi indexes on date columns is advisable.

    + Process large timestamp and timestamptz values more sanely in BRIN
      datetime_minmax_multi_ops indexes (Tomas Vondra)

      Infinities were mistakenly treated as having distance zero rather than a
      large distance from other values, causing poor decisions about which
      entries to merge. Also, finite-but-very-large values (near the endpoints
      of the representable timestamp range) could result in internal
      overflows, again causing poor decisions. The index still produces
      correct results, but is much less efficient than it should be.
      Reindexing BRIN minmax_multi indexes on timestamp and timestamptz
      columns is advisable if the column contains, or has contained,
      infinities or large finite values.

    + Details about these and many further changes can be found at:
      https://www.postgresql.org/docs/15/release-15-5.html.

  * d/p/libpgport-pkglibdir: adjust patch for new release.

 -- Athos Ribeiro <email address hidden> Thu, 23 Nov 2023 08:16:23 -0300

2040469 New upstream microreleases 12.17, 14.10, and 15.5



About   -   Send Feedback to @ubuntu_updates