Change log for postgresql-15 package in Ubuntu
| 1 → 16 of 16 results | First • Previous • Next • Last |
postgresql-15 (15.7-0ubuntu0.23.10.1) mantic-security; urgency=medium * New upstream version (LP: #2067388). + A dump/restore is not required for those running 15.X. + However, a security vulnerability was found in the system views pg_stats_ext and pg_stats_ext_exprs, potentially allowing authenticated database users to see data they shouldn't. If this is of concern in your installation, follow the steps below to rectify it. + Also, if you are upgrading from a version earlier than 15.6, see those release notes as well please. + Restrict visibility of pg_stats_ext and pg_stats_ext_exprs entries to the table owner (Nathan Bossart) These views failed to hide statistics for expressions that involve columns the accessing user does not have permission to read. View columns such as most_common_vals might expose security-relevant data. The potential interactions here are not fully clear, so in the interest of erring on the side of safety, make rows in these views visible only to the owner of the associated table. The PostgreSQL Project thanks Lukas Fittl for reporting this problem. By itself, this fix will only fix the behavior in newly initdb'd database clusters. If you wish to apply this change in an existing cluster, you will need to do the following: - In each database of the cluster, run the /usr/share/postgresql/15/fix-CVE-2024-4317.sql script as superuser. In psql this would look like: \i /usr/share/postgresql/15/fix-CVE-2024-4317.sql It will not hurt to run the script more than once. - Do not forget to include the template0 and template1 databases, or the vulnerability will still exist in databases you create later. To fix template0, you'll need to temporarily make it accept connections. Do that with: ALTER DATABASE template0 WITH ALLOW_CONNECTIONS true; and then after fixing template0, undo it with: ALTER DATABASE template0 WITH ALLOW_CONNECTIONS false; (CVE-2024-4317) + Details about these and many further changes can be found at: https://www.postgresql.org/docs/15/release-15-7.html. * d/postgresql-15.NEWS: Update. -- Sergio Durigan Junior <email address hidden> Tue, 28 May 2024 10:27:51 -0400
Available diffs
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
Available diffs
postgresql-15 (15.5-0ubuntu0.23.04.1) lunar-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 11:27:03 -0300
Available diffs
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
Available diffs
| Deleted in noble-release (Reason: Noble transition to postgreql-16 completed (LP: #2045029)) |
| Deleted in noble-proposed (Reason: Moved to noble) |
postgresql-15 (15.4-3) unstable; urgency=medium * Stop building lib packages, postgresql-16 is in unstable. * Use LLVM 15 for JIT support, 16 is not supported yet. (Closes: #1051881) -- Christoph Berg <email address hidden> Thu, 14 Sep 2023 09:28:43 +0200
Available diffs
postgresql-15 (15.4-0ubuntu0.23.04.1) lunar-security; urgency=medium * New upstream version (LP: #2028426). + A dump/restore is not required for those running 15.X. + However, if you use BRIN indexes, it may be advisable to reindex them. + Also, if you are upgrading from a version earlier than 15.1, see those release notes as well please. + Disallow substituting a schema or owner name into an extension script if the name contains a quote, backslash, or dollar sign (Noah Misch) This restriction guards against SQL-injection hazards for trusted extensions. (CVE-2023-39417) + Fix MERGE to enforce row security policies properly (Dean Rasheed) (CVE-2023-39418) + Fix confusion between empty (no rows) ranges and all-NULL ranges in BRIN indexes, as well as incorrect merging of all-NULL summaries (Tomas Vondra) Each of these oversights could result in forgetting that a BRIN index range contains any NULL values, potentially allowing subsequent queries that should return NULL values to miss doing so. This fix will not in itself correct faulty BRIN entries. It's recommended to REINDEX any BRIN indexes that may be used to search for nulls. + Details about these and many further changes can be found at: https://www.postgresql.org/docs/15/release-15-4.html. -- Athos Ribeiro <email address hidden> Wed, 09 Aug 2023 09:00:47 -0300
Available diffs
| Superseded in noble-release |
| Published in mantic-release |
| Deleted in mantic-proposed (Reason: Moved to mantic) |
postgresql-15 (15.4-1ubuntu1) mantic; urgency=medium * d/control: pin llvm-15 build dependencies. (LP: #2029498) -- Athos Ribeiro <email address hidden> Thu, 10 Aug 2023 20:53:01 -0300
Available diffs
- diff from 15.3-1 (in Debian) to 15.4-1ubuntu1 (915.7 KiB)
- diff from 15.4-1 (in Debian) to 15.4-1ubuntu1 (787 bytes)
postgresql-15 (15.4-1) unstable; urgency=medium
* New upstream version.
+ Disallow substituting a schema or owner name into an extension script if
the name contains a quote, backslash, or dollar sign (Noah Misch)
This restriction guards against SQL-injection hazards for trusted
extensions.
The PostgreSQL Project thanks Micah Gate, Valerie Woolard, Tim
Carey-Smith, and Christoph Berg for reporting this problem.
(CVE-2023-39417)
+ Fix MERGE to enforce row security policies properly (Dean Rasheed)
When MERGE performs an UPDATE action, it should enforce any UPDATE or
SELECT RLS policies defined on the target table, to be consistent with
the way that a plain UPDATE with a WHERE clause works. Instead it was
enforcing INSERT RLS policies for both INSERT and UPDATE actions.
In addition, when MERGE performs a DO NOTHING action, it applied the
target table's DELETE RLS policies to existing rows, even though those
rows are not being deleted. While it's not a security problem, this
could result in unwanted errors.
The PostgreSQL Project thanks Dean Rasheed for reporting this problem.
(CVE-2023-39418)
* Test-Depend on tzdata-legacy | tzdata (<< 2023c-8).
-- Christoph Berg <email address hidden> Tue, 08 Aug 2023 10:10:20 +0200
Available diffs
- diff from 15.3-1 to 15.4-1 (915.3 KiB)
postgresql-15 (15.3-0ubuntu0.23.04.1) lunar-security; urgency=medium * New upstream version (LP: #2019214). + A dump/restore is not required for those running 15.X. + Also, if you are upgrading from a version earlier than 15.1, see those release notes as well please. + Prevent CREATE SCHEMA from defeating changes in search_path (Alexander Lakhin) Within a CREATE SCHEMA command, objects in the prevailing search_path, as well as those in the newly-created schema, would be visible even within a called function or script that attempted to set a secure search_path. This could allow any user having permission to create a schema to hijack the privileges of a security definer function or extension script. (CVE-2023-2454) + Enforce row-level security policies correctly after inlining a set-returning function (Stephen Frost, Tom Lane) If a set-returning SQL-language function refers to a table having row-level security policies, and it can be inlined into a calling query, those RLS policies would not get enforced properly in some cases involving re-using a cached plan under a different role. This could allow a user to see or modify rows that should have been invisible. (CVE-2023-2455) + Details about these and many further changes can be found at: https://www.postgresql.org/docs/15/release-15-3.html. -- Sergio Durigan Junior <email address hidden> Thu, 11 May 2023 16:24:27 -0400
Available diffs
| Superseded in mantic-proposed |
postgresql-15 (15.3-0+deb12u1) unstable; urgency=medium
* New upstream version.
+ Prevent CREATE SCHEMA from defeating changes in search_path
(Report and fix by Alexander Lakhin, CVE-2023-2454)
Within a CREATE SCHEMA command, objects in the prevailing search_path,
as well as those in the newly-created schema, would be visible even
within a called function or script that attempted to set a secure
search_path. This could allow any user having permission to create a
schema to hijack the privileges of a security definer function or
extension script.
+ Enforce row-level security policies correctly after inlining a
set-returning function (Report by Wolfgang Walther, CVE-2023-2455)
If a set-returning SQL-language function refers to a table having
row-level security policies, and it can be inlined into a calling query,
those RLS policies would not get enforced properly in some cases
involving re-using a cached plan under a different role. This could
allow a user to see or modify rows that should have been invisible.
-- Christoph Berg <email address hidden> Tue, 09 May 2023 19:05:02 +0200
Available diffs
- diff from 15.2-2 to 15.3-0+deb12u1 (2.2 MiB)
postgresql-15 (15.3-1) experimental; urgency=medium
* New upstream version.
+ Prevent CREATE SCHEMA from defeating changes in search_path
(Report and fix by Alexander Lakhin, CVE-2023-2454)
Within a CREATE SCHEMA command, objects in the prevailing search_path,
as well as those in the newly-created schema, would be visible even
within a called function or script that attempted to set a secure
search_path. This could allow any user having permission to create a
schema to hijack the privileges of a security definer function or
extension script.
+ Enforce row-level security policies correctly after inlining a
set-returning function (Report by Wolfgang Walther, CVE-2023-2455)
If a set-returning SQL-language function refers to a table having
row-level security policies, and it can be inlined into a calling query,
those RLS policies would not get enforced properly in some cases
involving re-using a cached plan under a different role. This could
allow a user to see or modify rows that should have been invisible.
* Reenable JIT on s390x using workaround patch from SUSE.
-- Christoph Berg <email address hidden> Tue, 09 May 2023 19:05:02 +0200
Available diffs
- diff from 15.2-2 to 15.3-1 (2.2 MiB)
- diff from 15.3-0+deb12u1 to 15.3-1 (2.7 KiB)
postgresql-15 (15.2-2) unstable; urgency=medium * Add Romanian debconf translation, mulțumesc Remus-Gabriel Chelu! * Fix update-alternatives when doc package is installed stand-alone. -- Christoph Berg <email address hidden> Mon, 27 Feb 2023 10:30:23 +0100
Available diffs
- diff from 15.2-1 to 15.2-2 (1.8 KiB)
| Superseded in mantic-release |
| Published in lunar-release |
| Deleted in lunar-proposed (Reason: Moved to lunar) |
postgresql-15 (15.2-1) unstable; urgency=medium
* New upstream version.
+ libpq can leak memory contents after GSSAPI transport encryption
initiation fails (Jacob Champion)
A modified server, or an unauthenticated man-in-the-middle, can send a
not-zero-terminated error message during setup of GSSAPI (Kerberos)
transport encryption. libpq will then copy that string, as well as
following bytes in application memory up to the next zero byte, to its
error report. Depending on what the calling application does with the
error report, this could result in disclosure of application memory
contents. There is also a small probability of a crash due to reading
beyond the end of memory. Fix by properly zero-terminating the server
message. (CVE-2022-41862)
-- Christoph Berg <email address hidden> Tue, 07 Feb 2023 14:57:10 +0100
Available diffs
| Superseded in lunar-proposed |
postgresql-15 (15.1-1build2) lunar; urgency=medium * Rebuild against latest icu -- Jeremy Bicha <email address hidden> Sun, 05 Feb 2023 08:43:02 -0500
Available diffs
- diff from 15.1-1build1 to 15.1-1build2 (323 bytes)
postgresql-15 (15.1-1build1) lunar; urgency=medium * No-change rebuild with Python 3.11 as default -- Graham Inggs <email address hidden> Mon, 26 Dec 2022 10:03:07 +0000
Available diffs
- diff from 15.1-1 (in Debian) to 15.1-1build1 (318 bytes)
| Superseded in lunar-release |
| Deleted in lunar-proposed (Reason: Moved to lunar) |
| Superseded in lunar-proposed |
postgresql-15 (15.1-1) unstable; urgency=medium * New upstream version. -- Christoph Berg <email address hidden> Tue, 08 Nov 2022 10:59:12 +0100
| 1 → 16 of 16 results | First • Previous • Next • Last |
