New upstream microreleases 9.5.23 10.14 and 12.4

[Christian Ehrhardt ]

[Impact]

 * MRE for latest stable fixes of Postgres release on August 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 two CVEs:
   CVE-2020-14349
   CVE-2020-14350

---

Current versions in supported releases:
 postgresql-9.5 | 9.5.21-0ubuntu0.16.04.1 xenial
 postgresql-10 | 10.12-0ubuntu0.18.04.1 bionic
 postgresql-12 | 12.2-4 focal

Special cases:
- Groovy will as usual be synced from Debian.
   I already see
   postgresql-12 | 12.4-1 | groovy-proposed | source, amd64, i386, ppc64el, s390x

Last relevant related stable updates: 9.5.23, 10.14 and 12.4
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
- pad.lv/1863108

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

[Christian Ehrhardt  (paelzer)]

Xenial
PPA: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4218/+packages
MP: https://code.launchpad.net/~paelzer/ubuntu/+source/postgresql-9.5/+git/postgresql-9.5/+merge/389591

Bionic
PPA: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4219/+packages
MP: https://code.launchpad.net/~paelzer/ubuntu/+source/postgresql-10/+git/postgresql-10/+merge/389589

Focal
PPA: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4220/+packages
MP: https://code.launchpad.net/~paelzer/ubuntu/+source/postgresql-12/+git/postgresql-12/+merge/389590

[Christian Ehrhardt  (paelzer)]

Bionic tests are all good
https://bileto.ubuntu.com/excuses/4219/bionic.html

[Christian Ehrhardt  (paelzer)]

Xenial tests are all good as well, just three fails
- https://bileto.ubuntu.com/excuses/4218/xenial.html

Those three are covered by overrides:
- pitti:60:force-badtest bareos/14.2.6-3
- ubuntu-sru:71:force-badtest libreoffice/1:5.1.6~rc2-0ubuntu1~xenial10/i386
- pitti:16:force-badtest pgpool2/3.4.3-1

[Christian Ehrhardt  (paelzer)]

Focal is only mostly good.
The majority of tests is fine at
https://bileto.ubuntu.com/excuses/4220/focal.html

Of the remaining ones two are known overrides/resets:
- ubuntu-release:7143:force-badtest oca-core/all/i386
- ubuntu-release:54:force-reset-test diaspora-installer/0.7.6.1+debian1

But the postgresql-12 tests themselves failed
=> https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-focal-ci-train-ppa-service-4220/focal/amd64/p/postgresql-12/20200820_194445_7401b@/log.gz

The issue seems locally reproducible and needs a further look.

[Christian Ehrhardt  (paelzer)]

Thanks to myon I found this which will need to go along Focal.
https://salsa.debian.org/postgresql/postgresql-common/-/commit/301ab209d65e8c5873bf4fadd70810dee9994543
Because of
https://www.postgresql.org/message-id/20200811111544.GB4154579%40msg.df7cb.de

So an postgresql-common upload along will be needed for Focal.

[Christian Ehrhardt  (paelzer)]

Additional MP
https://code.launchpad.net/~paelzer/ubuntu/+source/postgresql-12/+git/postgresql-12/+merge/389590

Part of the Focal PPA now, tests will be restarted once the build is complete.

[Christian Ehrhardt  (paelzer)]

Ok,
the postgresql-common fixes fix the tests as expected.

Focal is now ready as well
Remaining issues in diaspora-installer, mediawiki, oca-core, postgresql-12@i386, resource-agents@i386 are all known force-badtest/reset entries.

ubuntu-release:10422:force-badtest resource-agents/all/i386 multipath-tools/all/i386
ubuntu-release:10292:force-badtest postgresql-12/all/i386
ubuntu-release:5798:force-badtest mediawiki/all/i386
ubuntu-release:7143:force-badtest oca-core/all/i386
ubuntu-release:54:force-reset-test diaspora-installer/0.7.6.1+debian1
ubuntu-release:1503:force-badtest diaspora-installer/all/i386

[Launchpad Janitor (janitor)]

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

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

  * New upstream release (LP: #1892335).
    - Make contrib modules' installation scripts more secure (Tom Lane)

      Attacks similar to those described in CVE-2018-1058 could be carried out
      against an extension installation script, if the attacker can create
      objects in either the extension's target schema or the schema of some
      prerequisite extension. Since extensions often require superuser
      privilege to install, this can open a path to obtaining superuser
      privilege. To mitigate this risk, be more careful about the search_path
      used to run an installation script; disable check_function_bodies within
      the script; and fix catalog-adjustment queries used in some contrib
      modules to ensure they are secure. Also provide documentation to help
      third-party extension authors make their installation scripts secure.
      This is not a complete solution; extensions that depend on other
      extensions can still be at risk if installed carelessly.
      CVE-2020-14350

    - Details about these and many further changes can be found at:
      https://www.postgresql.org/docs/9.5/static/release-9-5-22.html
      https://www.postgresql.org/docs/9.5/static/release-9-5-23.html

 -- Christian Ehrhardt <email address hidden> Thu, 20 Aug 2020 11:29:10 +0200

[Launchpad Janitor (janitor)]

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

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

  * New upstream release (LP: #1892335).
    - Set a secure search_path in logical replication walsenders and apply
      workers (Noah Misch)

      A malicious user of either the publisher or subscriber database could
      potentially cause execution of arbitrary SQL code by the role running
      replication, which is often a superuser. Some of the risks here are
      equivalent to those described in CVE-2018-1058, and are mitigated in
      this patch by ensuring that the replication sender and receiver execute
      with empty search_path settings. (As with CVE-2018-1058, that change
      might cause problems for under-qualified names used in replicated
      tables' DDL.) Other risks are inherent in replicating objects that
      belong to untrusted roles; the most we can do is document that there is
      a hazard to consider.
      CVE-2020-14349

    - Make contrib modules' installation scripts more secure (Tom Lane)

      Attacks similar to those described in CVE-2018-1058 could be carried out
      against an extension installation script, if the attacker can create
      objects in either the extension's target schema or the schema of some
      prerequisite extension. Since extensions often require superuser
      privilege to install, this can open a path to obtaining superuser
      privilege. To mitigate this risk, be more careful about the search_path
      used to run an installation script; disable check_function_bodies within
      the script; and fix catalog-adjustment queries used in some contrib
      modules to ensure they are secure. Also provide documentation to help
      third-party extension authors make their installation scripts secure.
      This is not a complete solution; extensions that depend on other
      extensions can still be at risk if installed carelessly.
      CVE-2020-14350

    - Details about these and many further changes can be found at:
      https://www.postgresql.org/docs/10/static/release-10-13.html
      https://www.postgresql.org/docs/10/static/release-10-14.html

 -- Christian Ehrhardt <email address hidden> Thu, 20 Aug 2020 11:29:28 +0200

[Launchpad Janitor (janitor)]

This bug was fixed in the package postgresql-12 - 12.4-0ubuntu0.20.04.1

---------------
postgresql-12 (12.4-0ubuntu0.20.04.1) focal-security; urgency=medium

  * New upstream release (LP: #1892335).
    - Set a secure search_path in logical replication walsenders and apply
      workers (Noah Misch)

      A malicious user of either the publisher or subscriber database could
      potentially cause execution of arbitrary SQL code by the role running
      replication, which is often a superuser. Some of the risks here are
      equivalent to those described in CVE-2018-1058, and are mitigated in
      this patch by ensuring that the replication sender and receiver execute
      with empty search_path settings. (As with CVE-2018-1058, that change
      might cause problems for under-qualified names used in replicated
      tables' DDL.) Other risks are inherent in replicating objects that
      belong to untrusted roles; the most we can do is document that there is
      a hazard to consider.
      CVE-2020-14349

    - Make contrib modules' installation scripts more secure (Tom Lane)

      Attacks similar to those described in CVE-2018-1058 could be carried out
      against an extension installation script, if the attacker can create
      objects in either the extension's target schema or the schema of some
      prerequisite extension. Since extensions often require superuser
      privilege to install, this can open a path to obtaining superuser
      privilege. To mitigate this risk, be more careful about the search_path
      used to run an installation script; disable check_function_bodies within
      the script; and fix catalog-adjustment queries used in some contrib
      modules to ensure they are secure. Also provide documentation to help
      third-party extension authors make their installation scripts secure.
      This is not a complete solution; extensions that depend on other
      extensions can still be at risk if installed carelessly.
      CVE-2020-14350

    - Details about these and many further changes can be found at:
      https://www.postgresql.org/docs/10/static/release-12-3.html
      https://www.postgresql.org/docs/10/static/release-12-4.htm

 -- Christian Ehrhardt <email address hidden> Thu, 20 Aug 2020 11:29:14 +0200