database/postgres
database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-05-02 11:44:50 +03:00
Code

Last-minute updates for release notes.

Browse Source 
Security: CVE-2018-1115
This commit is contained in:
Tom Lane 2018-05-07 11:50:05 -04:00
parent 20f01fc459
commit 27a6585180
2 changed files with 76 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

44
doc/src/sgml/release-10.sgml
View File

@ -23,9 +23,14 @@
</para>
<para>
However, if the function marking mistakes mentioned in the first two
changelog entries below affect you, you will want to take steps to
correct your database catalogs.
However, if you use the <filename>adminpack</filename> extension,
you should update it as per the first changelog entry below.
</para>
<para>
Also, if the function marking mistakes mentioned in the second and
third changelog entries below affect you, you will want to take steps
to correct your database catalogs.
</para>
<para>
@ -41,6 +46,39 @@
<listitem>
<!--
Author: Stephen Frost <sfrost@snowman.net>
Branch: master [7b347409f] 2018-05-07 10:10:33 -0400
Branch: REL_10_STABLE [20f01fc45] 2018-05-07 10:10:41 -0400
Branch: REL9_6_STABLE [53b79ab4f] 2018-05-07 10:10:45 -0400
-->
<para>
Remove public execute privilege
from <filename>contrib/adminpack</filename>'s
<function>pg_logfile_rotate()</function> function (Stephen Frost)
</para>
<para>
<function>pg_logfile_rotate()</function> is a deprecated wrapper
for the core function <function>pg_rotate_logfile()</function>.
When that function was changed to rely on SQL privileges for access
control rather than a hard-coded superuser
check, <function>pg_logfile_rotate()</function> should have been
updated as well, but the need for this was missed. Hence,
if <filename>adminpack</filename> is installed, any user could
request a logfile rotation, creating a minor security issue.
</para>
<para>
After installing this update, administrators should
update <filename>adminpack</filename> by performing
<literal>ALTER EXTENSION adminpack UPDATE</literal> in each
database in which <filename>adminpack</filename> is installed.
(CVE-2018-1115)
</para>
</listitem>
<listitem>
<!--
Author: Tom Lane <tgl@sss.pgh.pa.us>
Branch: master [11002f8af] 2018-03-30 18:14:51 -0400
Branch: REL_10_STABLE [283262cd9] 2018-03-30 18:14:51 -0400

38
doc/src/sgml/release-9.6.sgml
View File

@ -23,9 +23,14 @@
</para>
<para>
However, if the function marking mistakes mentioned in the first two
changelog entries below affect you, you will want to take steps to
correct your database catalogs.
However, if you use the <filename>adminpack</filename> extension,
you should update it as per the first changelog entry below.
</para>
<para>
Also, if the function marking mistakes mentioned in the second and
third changelog entries below affect you, you will want to take steps
to correct your database catalogs.
</para>
<para>
@ -39,6 +44,33 @@
<itemizedlist>
<listitem>
<para>
Remove public execute privilege
from <filename>contrib/adminpack</filename>'s
<function>pg_logfile_rotate()</function> function (Stephen Frost)
</para>
<para>
<function>pg_logfile_rotate()</function> is a deprecated wrapper
for the core function <function>pg_rotate_logfile()</function>.
When that function was changed to rely on SQL privileges for access
control rather than a hard-coded superuser
check, <function>pg_logfile_rotate()</function> should have been
updated as well, but the need for this was missed. Hence,
if <filename>adminpack</filename> is installed, any user could
request a logfile rotation, creating a minor security issue.
</para>
<para>
After installing this update, administrators should
update <filename>adminpack</filename> by performing
<literal>ALTER EXTENSION adminpack UPDATE</literal> in each
database in which <filename>adminpack</filename> is installed.
(CVE-2018-1115)
</para>
</listitem>
<listitem>
<para>
Fix incorrect volatility markings on a few built-in functions