The PostgreSQL search_path setting determines schemas searched for tables, functions, operators, etc. The CVE-2018-1058 fix caused most PostgreSQL-provided client applications to sanitize search_path, but logical replication continued to leave search_path unchanged. Users of a replication publisher or subscriber database can create objects in the "public" schema and harness them to execute arbitrary SQL functions under the identity running replication, often a superuser. Installations having adopted a documented "secure schema usage pattern" are not vulnerable.
Created postgresql tracking bugs for this issue:
Affects: fedora-all [bug 1868662]
Created postgresql:10/postgresql tracking bugs for this issue:
Affects: fedora-all [bug 1868663]
Created postgresql:11/postgresql tracking bugs for this issue:
Affects: fedora-all [bug 1868665]
Created postgresql:12/postgresql tracking bugs for this issue:
Affects: fedora-all [bug 1868667]
In Red Hat Gluster Storage 3, PostgreSQL was shipped as a part of 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.
This issue has been addressed in the following products:
Red Hat Enterprise Linux 8
Via RHSA-2020:3669 https://access.redhat.com/errata/RHSA-2020:3669
This bug is now closed. Further updates for individual products will be reflected on the CVE page(s):