The \gset meta-command, which sets psql variables based on query results, does not distinguish variables that control psql behavior. If an interactive psql session uses \gset when querying a compromised server, the attacker can execute arbitrary code as the operating system account running psql. Using \gset with a prefix not found among specially treated variables, e.g. any lowercase string, precludes the attack in an unpatched psql.
Acknowledgments: Name: Nick Cleaton
Created mingw-postgresql tracking bugs for this issue: Affects: fedora-all [bug 1897233] Created postgresql tracking bugs for this issue: Affects: fedora-all [bug 1897230] Created postgresql:10/postgresql tracking bugs for this issue: Affects: fedora-all [bug 1897227] Created postgresql:11/postgresql tracking bugs for this issue: Affects: fedora-all [bug 1897224] Created postgresql:12/postgresql tracking bugs for this issue: Affects: fedora-all [bug 1897221] Created postgresql:9.6/postgresql tracking bugs for this issue: Affects: fedora-all [bug 1897218]
External References: https://www.postgresql.org/about/news/postgresql-131-125-1110-1015-9620-and-9524-released-2111/
Mitigation: Using \gset with a prefix not found among specially treated variables, e.g. any lowercase string, precludes the attack in an unpatched psql.
Upstream fix: https://git.postgresql.org/gitweb/?p=postgresql.git;a=commit;h=098fb00799ffb026ff12c64bd21635f963cfc609
This issue has been addressed in the following products: Red Hat Software Collections for Red Hat Enterprise Linux 7 Red Hat Software Collections for Red Hat Enterprise Linux 7.6 EUS Red Hat Software Collections for Red Hat Enterprise Linux 7.7 EUS Via RHSA-2020:5316 https://access.redhat.com/errata/RHSA-2020:5316
This issue has been addressed in the following products: Red Hat Software Collections for Red Hat Enterprise Linux 7 Red Hat Software Collections for Red Hat Enterprise Linux 7.6 EUS Red Hat Software Collections for Red Hat Enterprise Linux 7.7 EUS Via RHSA-2020:5317 https://access.redhat.com/errata/RHSA-2020:5317
This bug is now closed. Further updates for individual products will be reflected on the CVE page(s): https://access.redhat.com/security/cve/cve-2020-25696
This issue has been addressed in the following products: Red Hat Enterprise Linux 8 Via RHSA-2020:5401 https://access.redhat.com/errata/RHSA-2020:5401
This issue has been addressed in the following products: Red Hat Enterprise Linux 8 Via RHSA-2020:5567 https://access.redhat.com/errata/RHSA-2020:5567
Statement: In Red Hat Gluster Storage 3, PostgreSQL (embedded in rhevm-dependencies) was shipped as a part of the Red Hat Gluster Storage Console that is no longer supported for use with Red Hat Gluster Storage 3.5. Red Hat Gluster Storage Web Administration is now the recommended monitoring tool for Red Hat Storage Gluster clusters. In Red Hat Virtualization, the manager appliance uses a vulnerable version of postgresql. Once a fix has been shipped for RHEL 8 the appliance can consume the fix via a regular yum update.
This issue has been addressed in the following products: Red Hat Enterprise Linux 8 Via RHSA-2020:5619 https://access.redhat.com/errata/RHSA-2020:5619
This issue has been addressed in the following products: Red Hat Enterprise Linux 8 Via RHSA-2020:5620 https://access.redhat.com/errata/RHSA-2020:5620
This issue has been addressed in the following products: Red Hat Enterprise Linux 8.0 Update Services for SAP Solutions Via RHSA-2020:5638 https://access.redhat.com/errata/RHSA-2020:5638
This issue has been addressed in the following products: Red Hat Enterprise Linux 8.0 Update Services for SAP Solutions Via RHSA-2020:5661 https://access.redhat.com/errata/RHSA-2020:5661
This issue has been addressed in the following products: Red Hat Enterprise Linux 8.0 Update Services for SAP Solutions Via RHSA-2020:5664 https://access.redhat.com/errata/RHSA-2020:5664
This issue has been addressed in the following products: Red Hat Enterprise Linux 8.2 Extended Update Support Via RHSA-2021:0057 https://access.redhat.com/errata/RHSA-2021:0057
This issue has been addressed in the following products: Red Hat Enterprise Linux 8.2 Extended Update Support Via RHSA-2021:0161 https://access.redhat.com/errata/RHSA-2021:0161
This issue has been addressed in the following products: Red Hat Enterprise Linux 8.2 Extended Update Support Via RHSA-2021:0163 https://access.redhat.com/errata/RHSA-2021:0163
This issue has been addressed in the following products: Red Hat Enterprise Linux 8.2 Extended Update Support Via RHSA-2021:0164 https://access.redhat.com/errata/RHSA-2021:0164
This issue has been addressed in the following products: Red Hat Enterprise Linux 8.1 Extended Update Support Via RHSA-2021:0165 https://access.redhat.com/errata/RHSA-2021:0165
This issue has been addressed in the following products: Red Hat Enterprise Linux 8.1 Extended Update Support Via RHSA-2021:0166 https://access.redhat.com/errata/RHSA-2021:0166
This issue has been addressed in the following products: Red Hat Enterprise Linux 8.1 Extended Update Support Via RHSA-2021:0167 https://access.redhat.com/errata/RHSA-2021:0167