aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorTom Lane <tgl@sss.pgh.pa.us>2012-02-23 17:48:18 -0500
committerTom Lane <tgl@sss.pgh.pa.us>2012-02-23 17:48:18 -0500
commitecabae5af98d2b238e82cb59b4fd9b00aad1e63d (patch)
tree35a1be0cf419cdb31b2b4cc0144ab942e6166ece
parenta7f6cb85486b1f3eacd86155af2fdc20a1dc2bec (diff)
downloadpostgresql-ecabae5af98d2b238e82cb59b4fd9b00aad1e63d.tar.gz
postgresql-ecabae5af98d2b238e82cb59b4fd9b00aad1e63d.zip
Last-minute release note updates.
Security: CVE-2012-0866, CVE-2012-0867, CVE-2012-0868
-rw-r--r--doc/src/sgml/release-8.3.sgml30
1 files changed, 30 insertions, 0 deletions
diff --git a/doc/src/sgml/release-8.3.sgml b/doc/src/sgml/release-8.3.sgml
index e80743f463b..09f867b527d 100644
--- a/doc/src/sgml/release-8.3.sgml
+++ b/doc/src/sgml/release-8.3.sgml
@@ -36,6 +36,36 @@
<listitem>
<para>
+ Require execute permission on the trigger function for
+ <command>CREATE TRIGGER</> (Robert Haas)
+ </para>
+
+ <para>
+ This missing check could allow another user to execute a trigger
+ function with forged input data, by installing it on a table he owns.
+ This is only of significance for trigger functions marked
+ <literal>SECURITY DEFINER</>, since otherwise trigger functions run
+ as the table owner anyway. (CVE-2012-0866)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Convert newlines to spaces in names written in <application>pg_dump</>
+ comments (Robert Haas)
+ </para>
+
+ <para>
+ <application>pg_dump</> was incautious about sanitizing object names
+ that are emitted within SQL comments in its output script. A name
+ containing a newline would at least render the script syntactically
+ incorrect. Maliciously crafted object names could present a SQL
+ injection risk when the script is reloaded. (CVE-2012-0868)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
Fix btree index corruption from insertions concurrent with vacuuming
(Tom Lane)
</para>