New upstream microreleases 9.5.21 10.12 11.7 and 12.2

Bug #1863108 reported by Christian Ehrhardt 
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
postgresql-10 (Ubuntu)
Bionic
Fix Released
Undecided
Ubuntu Security Team
postgresql-11 (Ubuntu)
Eoan
Fix Released
Undecided
Ubuntu Security Team
postgresql-12 (Ubuntu)
Focal
In Progress
Undecided
Unassigned
postgresql-9.5 (Ubuntu)
Xenial
Fix Released
Undecided
Unassigned

Bug Description

[Impact]

 * MRE for latest stable fixes of Postgres release on Feb 13th.

[Test Case]

 * The Postgres MREs traditionally rely on the large set of autopkgtests
   to run for verification. In a PPA those are all already pre-checked to
   be good for this upload.

[Regression Potential]

 * Upstreams tests are usually great and in additon in the Archive there
   are plenty of autopkgtests that in the past catched issues before being
   released.
   But never the less there always is a risk for something to break. Since
   these are general stable releases I can't pinpoint them to a most-likely
   area.
   - usually this works smoothly except a few test hickups (flaky) that need to be
     clarified to be sure. Pre-checks will catch those to be discussed upfront (as last time)

[Other Info]

 * This is a reoccurring MRE, see below and all the references
 * This includes a fix for CVE: CVE-2020-1720 (Affects 9.6-12, so all but xenial)

---

Current versions in supported releases:
 postgresql-9.5 | 9.5.19-0ubuntu0.16.04 xenial
 postgresql-10 | 10.10-0ubuntu0.18.04.1 bionic
 postgresql-11 | 11.5-1eoan
 postgresql-12 | 12.1-2build1 focal

Special cases:
- Focal will as usual be synced from Debian.
   I already see https://buildd.debian.org/status/fetch.php?pkg=postgresql-12&arch=s390x&ver=12.2-1&stamp=1581600108&raw=0

Last relevant related stable updates: 9.5.21, 10.12, 11.5 and 12.2
You'll see that the last update was missed, so I'll combined them.

Standing MRE - Consider last updates as template:
- pad.lv/1637236
- pad.lv/1664478
- pad.lv/1690730
- pad.lv/1713979
- pad.lv/1730661
- pad.lv/1747676
- pad.lv/1752271
- pad.lv/1786938
- pad.lv/1815665
- pad.lv/1828012
- pad.lv/1833211
- pad.lv/1839058

As usual we test and prep from the PPA and then push through SRU/Security as applicable.

Related branches

CVE References

no longer affects: postgresql-11 (Ubuntu)
Changed in postgresql-10 (Ubuntu Bionic):
status: New → Triaged
Changed in postgresql-11 (Ubuntu Eoan):
status: New → Triaged
Changed in postgresql-12 (Ubuntu Focal):
status: New → Triaged
Changed in postgresql-9.5 (Ubuntu Xenial):
status: New → Triaged
description: updated
description: updated
description: updated
Changed in postgresql-12 (Ubuntu Focal):
status: Triaged → In Progress
Revision history for this message
Mike Salvatore (mikesalvatore) wrote :

Given the "medium" priority of CVE-2020-1720, this can go to the -security pocket.

Revision history for this message
Christian Ehrhardt  (paelzer) wrote :

Usual prechecks are on:
Xenial:
- https://bileto.ubuntu.com/#/ticket/3926
- https://bileto.ubuntu.com/excuses/3926/xenial.html
- https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3926
Bionic:
- https://bileto.ubuntu.com/#/ticket/3927
- https://bileto.ubuntu.com/excuses/3927/bionic.html
- https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3927
Eoan:
- https://bileto.ubuntu.com/#/ticket/3928
- https://bileto.ubuntu.com/excuses/3928/eoan.html
- https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/3928

Build is complete and good on all of them.
Checking the autopkgtests against known/new issues.

Xenial bad tests:
- bareos, gearmand (armhf), orafce, pgfincore, pgpool2, postgresql-multicorn, postgresql-plproxy => already known cases with force-badtest
- libreoffice => known to be flaky and working on retries

Bionic bad tests:
- diaspora-installer @armhf, pglogical @armhf => already known cases with force-badtest
- pgagent

Eoan bad tests:
- pglogical, resource-agent, postgresql-hll - known force-badtest
The following are regular fails that need force-badtest added (no new regressions)
- diaspora-installer @armhf @ppc64,
  http://autopkgtest.ubuntu.com/packages/diaspora-installer/eoan/armhf
  http://autopkgtest.ubuntu.com/packages/diaspora-installer/eoan/ppc64el
- pg-snakeoil
  http://autopkgtest.ubuntu.com/packages/pg-snakeoil
  Broken in-release by another update before

The following we hit the first time and need to take a look:
- pgl-ddl-deploy @ppc64
  flaky?
  http://autopkgtest.ubuntu.com/packages/pgl-ddl-deploy/eoan/ppc64el
- postgresql-debversion @ armhf
  http://autopkgtest.ubuntu.com/packages/postgresql-debversion/eoan/armhf
- pglogical-ticker @ppc64
  flaky?
  http://autopkgtest.ubuntu.com/packages/pglogical-ticker/focal/ppc64el
- sqitch @armhf
  http://autopkgtest.ubuntu.com/packages/sqitch/eoan/armhf

I restarted the above, we will have to continue resolving those before the upload.

Revision history for this message
Christian Ehrhardt  (paelzer) wrote :
Revision history for this message
Christian Ehrhardt  (paelzer) wrote :

As assumed of the lists above the flaky ones are resolved, therefore the following are no more needed to be checked:
- pgl-ddl-deploy
- postgresql-debversion
- pglogical-ticker
- sqitch

That was the full list of "new" cases.
We will need/want to add diaspora-installer and pg-snakeoil to force-badtest for Eoan still.

Revision history for this message
Christian Ehrhardt  (paelzer) wrote :

MPs reviewed, minor fixups to the changelogs made.

X: uploaded for SRU team review (no CVE)
B/E: asked the security Team to push to -security as discussed

P.S. @security - I uploaded the final version to the branches as well as to the PPAs that were linked before. Pick from whatever suits you more.

Changed in postgresql-11 (Ubuntu Eoan):
assignee: nobody → Ubuntu Security Team (ubuntu-security)
Changed in postgresql-10 (Ubuntu Bionic):
assignee: nobody → Ubuntu Security Team (ubuntu-security)
Revision history for this message
Christian Ehrhardt  (paelzer) wrote :

FYI PG-12 in Focal is good, but wait for the ICU transition.

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package postgresql-10 - 10.12-0ubuntu0.18.04.1

---------------
postgresql-10 (10.12-0ubuntu0.18.04.1) bionic-security; urgency=medium

  * New upstream release (LP: #1863108)
    - A dump/restore is not required however, if you use the contrib/intarray
      extension with a GiST index, and you rely on indexed searches for the <@
      operator, see the release notes for details in regard to a related fix.
    - Add missing permissions checks for ALTER ... DEPENDS ON EXTENSION.
      Marking an object as dependent on an extension did not have any
      privilege check whatsoever. This oversight allowed any user to mark
      routines, triggers, materialized views, or indexes as droppable by
      anyone able to drop an extension. Require that the calling user own the
      specified object (and hence have privilege to drop it). (CVE-2020-1720)
    - Details about these and many further changes can be found at:
      https://www.postgresql.org/docs/10/static/release-10-11.html
      https://www.postgresql.org/docs/10/static/release-10-12.html

 -- Christian Ehrhardt <email address hidden> Thu, 13 Feb 2020 15:18:22 +0100

Changed in postgresql-10 (Ubuntu Bionic):
status: Triaged → Fix Released
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package postgresql-11 - 11.7-0ubuntu0.19.10.1

---------------
postgresql-11 (11.7-0ubuntu0.19.10.1) eoan-security; urgency=medium

  * New upstream release (LP: #1863108)
    - A dump/restore is not required however, if you use the contrib/intarray
      extension with a GiST index, and you rely on indexed searches for the <@
      operator, see the release notes for details in regard to a related fix.
    - Add missing permissions checks for ALTER ... DEPENDS ON EXTENSION.
      Marking an object as dependent on an extension did not have any
      privilege check whatsoever. This oversight allowed any user to mark
      routines, triggers, materialized views, or indexes as droppable by
      anyone able to drop an extension. Require that the calling user own the
      specified object (and hence have privilege to drop it). (CVE-2020-1720)
    - Details about these and many further changes can be found at:
      https://www.postgresql.org/docs/11/static/release-11-6.html
      https://www.postgresql.org/docs/11/static/release-11-7.html

 -- Christian Ehrhardt <email address hidden> Thu, 13 Feb 2020 15:18:24 +0100

Changed in postgresql-11 (Ubuntu Eoan):
status: Triaged → Fix Released
Revision history for this message
Robie Basak (racb) wrote : Please test proposed package

Hello Christian, or anyone else affected,

Accepted postgresql-9.5 into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/postgresql-9.5/9.5.21-0ubuntu0.16.04.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Changed in postgresql-9.5 (Ubuntu Xenial):
status: Triaged → Fix Committed
tags: added: verification-needed verification-needed-xenial
Revision history for this message
Ubuntu SRU Bot (ubuntu-sru-bot) wrote : Autopkgtest regression report (postgresql-9.5/9.5.21-0ubuntu0.16.04.1)

All autopkgtests for the newly accepted postgresql-9.5 (9.5.21-0ubuntu0.16.04.1) for xenial have finished running.
The following regressions have been reported in tests triggered by the package:

libreoffice/1:5.1.6~rc2-0ubuntu1~xenial10 (i386)

Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-migration/xenial/update_excuses.html#postgresql-9.5

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

Revision history for this message
Christian Ehrhardt  (paelzer) wrote :

The one test that was flagged is a known flaky one, I restarted it.

Revision history for this message
Christian Ehrhardt  (paelzer) wrote :

Well I said it was known to be flaky (which is true) but I also found it actually was even elevated to a force-badtest as it didn't work the last 2-1/3 years.

It was (last time we did a postgres SRU into xenial) at:
brian-murray:8:force-badtest libreoffice/1:5.1.6~rc2-0ubuntu1~xenial6/i386 libreoffice/1:5.1.6~rc2-0ubuntu1~xenial7/i386

It was bumped later and now is
brian-murray:8:force-badtest libreoffice/1:5.1.6~rc2-0ubuntu1~xenial7/i386 libreoffice/1:5.1.6~rc2-0ubuntu1~xenial9/i386

But now the version in xenial is at:
1:5.1.6~rc2-0ubuntu1~xenial10

We need to bump the override accordingly.
=> https://code.launchpad.net/~paelzer/britney/hints-ubuntu-xenial-pg-update-march-2020/+merge/380811

Revision history for this message
Christian Ehrhardt  (paelzer) wrote :

The only test left with issues is a known bad one (see the MP bumping the override).
Therefore as postgresql MREs are handled that means we can set verification-done as all tests completed.

tags: added: verification-done verification-done-xenial
removed: verification-needed verification-needed-xenial
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package postgresql-9.5 - 9.5.21-0ubuntu0.16.04.1

---------------
postgresql-9.5 (9.5.21-0ubuntu0.16.04.1) xenial; urgency=medium

  * New upstream release (LP: #1863108)
    - A dump/restore is not required however, if you use the contrib/intarray
      extension with a GiST index, and you rely on indexed searches for the <@
      operator, see the release notes for details in regard to a related fix.
    - Details about these and many further changes can be found at:
      https://www.postgresql.org/docs/9.5/static/release-9-5-20.html
      https://www.postgresql.org/docs/9.5/static/release-9-5-21.html

 -- Christian Ehrhardt <email address hidden> Thu, 13 Feb 2020 15:18:20 +0100

Changed in postgresql-9.5 (Ubuntu Xenial):
status: Fix Committed → Fix Released
Revision history for this message
Brian Murray (brian-murray) wrote : Update Released

The verification of the Stable Release Update for postgresql-9.5 has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.