A flaw was found in PostgreSQL. There is an issue with incomplete efforts to operate safely when a privileged user is maintaining another user's objects. The Autovacuum, REINDEX, CREATE INDEX, REFRESH MATERIALIZED VIEW, CLUSTER, and pg_amcheck commands activated relevant protections too late or not at all during the process. This flaw allows an attacker with permission to create non-temporary objects in at least one schema to execute arbitrary SQL functions under a superuser identity.
The product does not properly "clean up" and remove temporary or supporting resources after they have been used.
The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data.
Link | Tags |
---|---|
https://bugzilla.redhat.com/show_bug.cgi?id=2081126 | patch third party advisory issue tracking |
https://www.postgresql.org/about/news/postgresql-143-137-1211-1116-and-1021-released-2449/ | vendor advisory |
https://www.postgresql.org/support/security/CVE-2022-1552/ | vendor advisory |
https://access.redhat.com/security/cve/CVE-2022-1552 | third party advisory |
https://security.netapp.com/advisory/ntap-20221104-0005/ | third party advisory |
https://security.gentoo.org/glsa/202211-04 | third party advisory vendor advisory |