From da21a3a7d5d37e34f2adef07b1f2f6231d61c3cc Mon Sep 17 00:00:00 2001
From: Tom Lane
Date: Mon, 5 Feb 2024 11:51:11 -0500
Subject: Last-minute updates for release notes.
Security: CVE-2024-0985 (not CVE-2023-5869 as claimed in prior commit msg)
---
doc/src/sgml/release-16.sgml | 44 ++++++++++++++++++++++++++++++++++++++++++++
1 file changed, 44 insertions(+)
(limited to 'doc/src')
diff --git a/doc/src/sgml/release-16.sgml b/doc/src/sgml/release-16.sgml
index a380b7d4fad..fa6dae79b9f 100644
--- a/doc/src/sgml/release-16.sgml
+++ b/doc/src/sgml/release-16.sgml
@@ -41,6 +41,50 @@
+
+ Tighten security restrictions within REFRESH MATERIALIZED
+ VIEW CONCURRENTLY (Heikki Linnakangas)
+
+
+
+ One step of a concurrent refresh command was run under weak security
+ restrictions. If a materialized view's owner could persuade a
+ superuser or other high-privileged user to perform a concurrent
+ refresh on that view, the view's owner could control code executed
+ with the privileges of the user running REFRESH.
+ Fix things so that all user-determined code is run as the view's
+ owner, as expected.
+
+
+
+ The only known exploit for this error does not work
+ in PostgreSQL 16.0 and later, so it may
+ be that v16 is not vulnerable in practice.
+
+
+
+ The PostgreSQL Project thanks Pedro
+ Gallegos for reporting this problem.
+ (CVE-2024-0985)
+
+
+
+
+