Bug 1894425 (CVE-2020-25695) - CVE-2020-25695 postgresql: Multiple features escape "security restricted operation" sandbox
Summary: CVE-2020-25695 postgresql: Multiple features escape "security restricted oper...
Keywords:
Status: NEW
Alias: CVE-2020-25695
Product: Security Response
Classification: Other
Component: vulnerability
Version: unspecified
Hardware: All
OS: Linux
high
high
Target Milestone: ---
Assignee: Red Hat Product Security
QA Contact:
URL:
Whiteboard:
Depends On: 1897217 1897220 1897223 1897226 1897229 1897232 1898328 1898329 1898330 1898331 1898332 1898333 1898334 1898335 1898336 1898337 1898338 1898339 1898340 1898341 1898342 1898345 1898346 1898961 1898962
Blocks: 1894439
TreeView+ depends on / blocked
 
Reported: 2020-11-04 09:06 UTC by Michael Kaplan
Modified: 2020-11-25 10:47 UTC (History)
78 users (show)

Fixed In Version: postgresql 13.1, postgresql 12.5, postgresql 11.10, postgresql 10.15, postgresql 9.6.20, postgresql 9.5.24
Doc Type: If docs needed, set a value
Doc Text:
A flaw was found in postgresql. An attacker having permission to create non-temporary objects in at least one schema can execute arbitrary SQL functions under the identity of a superuser. The highest threat from this vulnerability is to data confidentiality and integrity as well as system availability.
Clone Of:
Environment:
Last Closed:


Attachments (Terms of Use)

Description Michael Kaplan 2020-11-04 09:06:40 UTC
An attacker having permission to create non-temporary objects in at least one
schema can execute arbitrary SQL functions under the identity of a superuser.
While promptly updating PostgreSQL is the best remediation for most users, a
user unable to do that can work around the vulnerability by disabling
autovacuum and not manually running ANALYZE, CLUSTER, REINDEX, CREATE INDEX,
VACUUM FULL, REFRESH MATERIALIZED VIEW, or a restore from output of the
pg_dump command.  Performance may degrade quickly under this workaround.
VACUUM, without the FULL option, is safe, and all commands are fine when a
trusted user owns the target object.

Comment 1 Michael Kaplan 2020-11-04 09:06:54 UTC
Acknowledgments:

Name: Etienne Stalmans

Comment 7 Eric Christensen 2020-11-09 18:32:45 UTC
Mitigation:

While promptly updating PostgreSQL is the best remediation for most users, a user unable to do that can work around the vulnerability by disabling autovacuum and not manually running ANALYZE, CLUSTER, REINDEX, CREATE INDEX, VACUUM FULL, REFRESH MATERIALIZED VIEW, or a restore from output of the pg_dump command. Performance may degrade quickly under this workaround.

Comment 10 msiddiqu 2020-11-12 15:19:29 UTC
Created mingw-postgresql tracking bugs for this issue:

Affects: fedora-all [bug 1897232]


Created postgresql tracking bugs for this issue:

Affects: fedora-all [bug 1897229]


Created postgresql:10/postgresql tracking bugs for this issue:

Affects: fedora-all [bug 1897226]


Created postgresql:11/postgresql tracking bugs for this issue:

Affects: fedora-all [bug 1897223]


Created postgresql:12/postgresql tracking bugs for this issue:

Affects: fedora-all [bug 1897220]


Created postgresql:9.6/postgresql tracking bugs for this issue:

Affects: fedora-all [bug 1897217]

Comment 13 Stoyan Nikolov 2020-11-17 08:06:46 UTC
Statement:

In Red Hat Gluster Storage 3, PostgreSQL (embedded in rhevm-dependencies) 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.
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.

Comment 14 Mauro Matteo Cascella 2020-11-17 08:17:39 UTC
External References:

https://www.postgresql.org/about/news/postgresql-131-125-1110-1015-9620-and-9524-released-2111/


Note You need to log in before you can comment on or make changes to this bug.