Security Issue Notification

Do not make this issue public.

This is a preliminary notification of a potential vulnerability under the accelerated "Triage Tracker" program introduced between Product Security and Engineering to allow deeper collaboration.

The in-depth analysis is ongoing, and details are expected to change until such time as it concludes.

Be aware that someone other than the analyst performing the Secondary Assessment will usually create the triage tracker. The best option is to comment in the tracker and wait for a reply. Based on your regular interactions, if you know the Incident Response Analyst for your offering, you can reach out to them directly or add a private comment in the triage tracker or in the flaw bug for their attention.

Please refer to the FAQ page for more information - https://source.redhat.com/departments/products_and_global_engineering/product_security/content/product_security_wiki/incident_response_coordination_faq
Impact: Important
Reported Date: 08-Feb-2024
Bug is not bound by a Security SLA. Use your own judgement.

Please see the Security Errata Policy for further details: https://docs.engineering.redhat.com/x/9kKpDw

Flaw:

CVE-2024-0985 postgresql: non-owner 'REFRESH MATERIALIZED VIEW CONCURRENTLY' executes arbitrary SQL
https://bugzilla.redhat.com/show_bug.cgi?id=2263384

Late privilege drop in REFRESH MATERIALIZED VIEW CONCURRENTLY in PostgreSQL allows an object creator to execute arbitrary SQL functions as the command issuer. The command intends to run SQL functions as the owner of the materialized view, enabling safe refresh of untrusted materialized views. The victim is a superuser or member of one of the attacker's roles. The attack requires luring the victim into running REFRESH MATERIALIZED VIEW CONCURRENTLY on the attacker's materialized view. As part of exploiting this vulnerability, the attacker creates functions that use CREATE RULE to convert the internally-built temporary table to a view. Versions before PostgreSQL 15.6, 14.11, 13.14, and 12.18 are affected. The only known exploit does not work in PostgreSQL 16 and later. For defense in depth, PostgreSQL 16.2 adds the protections that older branches are using to fix their vulnerability.

Affected Versions: 12, 13, 14, 15
Fixed in: 12.18, 13.14, 14.11, 15.6

References:
https://www.postgresql.org/support/security/CVE-2024-0985/