mirror of
https://github.com/postgres/postgres.git
synced 2025-05-21 15:54:08 +03:00
Last-minute updates for release notes.
Security: CVE-2018-1052, CVE-2018-1053
This commit is contained in:
Tom Lane
parent
dc6fb453a3
commit
cbe0dd581e
@ -41,6 +41,55 @@
|
|||||||
|
|
||||||
<listitem>
|
<listitem>
|
||||||
<!--
|
<!--
|
||||||
|
Author: Tom Lane <tgl@sss.pgh.pa.us>
|
||||||
|
Branch: master [3492a0af0] 2018-02-05 10:37:30 -0500
|
||||||
|
Branch: REL_10_STABLE [fe921a360] 2018-02-05 10:37:30 -0500
|
||||||
|
-->
|
||||||
|
<para>
|
||||||
|
Fix processing of partition keys containing multiple expressions
|
||||||
|
(Álvaro Herrera, David Rowley)
|
||||||
|
</para>
|
||||||
|
|
||||||
|
<para>
|
||||||
|
This error led to crashes or, with carefully crafted input, disclosure
|
||||||
|
of arbitrary backend memory.
|
||||||
|
(CVE-2018-1052)
|
||||||
|
</para>
|
||||||
|
</listitem>
|
||||||
|
|
||||||
|
<listitem>
|
||||||
|
<!--
|
||||||
|
Author: Tom Lane <tgl@sss.pgh.pa.us>
|
||||||
|
Branch: master [a926eb84e] 2018-02-05 10:58:27 -0500
|
||||||
|
Branch: REL_10_STABLE [6ba52aeb2] 2018-02-05 10:58:27 -0500
|
||||||
|
Branch: REL9_6_STABLE [1341e017d] 2018-02-05 10:58:27 -0500
|
||||||
|
Branch: REL9_5_STABLE [17aa02368] 2018-02-05 10:58:27 -0500
|
||||||
|
Branch: REL9_4_STABLE [c3456208d] 2018-02-05 10:58:27 -0500
|
||||||
|
Branch: REL9_3_STABLE [9c59e48a2] 2018-02-05 10:58:27 -0500
|
||||||
|
-->
|
||||||
|
<para>
|
||||||
|
Ensure that all temporary files made
|
||||||
|
by <application>pg_upgrade</application> are non-world-readable
|
||||||
|
(Tom Lane, Noah Misch)
|
||||||
|
</para>
|
||||||
|
|
||||||
|
<para>
|
||||||
|
<application>pg_upgrade</application> normally restricts its
|
||||||
|
temporary files to be readable and writable only by the calling user.
|
||||||
|
But the temporary file containing <literal>pg_dumpall -g</literal>
|
||||||
|
output would be group- or world-readable, or even writable, if the
|
||||||
|
user's <literal>umask</literal> setting allows. In typical usage on
|
||||||
|
multi-user machines, the <literal>umask</literal> and/or the working
|
||||||
|
directory's permissions would be tight enough to prevent problems;
|
||||||
|
but there may be people using <application>pg_upgrade</application>
|
||||||
|
in scenarios where this oversight would permit disclosure of database
|
||||||
|
passwords to unfriendly eyes.
|
||||||
|
(CVE-2018-1053)
|
||||||
|
</para>
|
||||||
|
</listitem>
|
||||||
|
|
||||||
|
<listitem>
|
||||||
|
<!--
|
||||||
Author: Andres Freund <andres@anarazel.de>
|
Author: Andres Freund <andres@anarazel.de>
|
||||||
Branch: master [9c2f0a6c3] 2017-12-14 18:20:47 -0800
|
Branch: master [9c2f0a6c3] 2017-12-14 18:20:47 -0800
|
||||||
Branch: REL_10_STABLE [1224383e8] 2017-12-14 18:20:48 -0800
|
Branch: REL_10_STABLE [1224383e8] 2017-12-14 18:20:48 -0800
|
||||||
|
|||||||
@ -33,6 +33,28 @@
|
|||||||
|
|
||||||
<itemizedlist>
|
<itemizedlist>
|
||||||
|
|
||||||
|
<listitem>
|
||||||
|
<para>
|
||||||
|
Ensure that all temporary files made
|
||||||
|
by <application>pg_upgrade</application> are non-world-readable
|
||||||
|
(Tom Lane, Noah Misch)
|
||||||
|
</para>
|
||||||
|
|
||||||
|
<para>
|
||||||
|
<application>pg_upgrade</application> normally restricts its
|
||||||
|
temporary files to be readable and writable only by the calling user.
|
||||||
|
But the temporary file containing <literal>pg_dumpall -g</literal>
|
||||||
|
output would be group- or world-readable, or even writable, if the
|
||||||
|
user's <literal>umask</literal> setting allows. In typical usage on
|
||||||
|
multi-user machines, the <literal>umask</literal> and/or the working
|
||||||
|
directory's permissions would be tight enough to prevent problems;
|
||||||
|
but there may be people using <application>pg_upgrade</application>
|
||||||
|
in scenarios where this oversight would permit disclosure of database
|
||||||
|
passwords to unfriendly eyes.
|
||||||
|
(CVE-2018-1053)
|
||||||
|
</para>
|
||||||
|
</listitem>
|
||||||
|
|
||||||
<listitem>
|
<listitem>
|
||||||
<para>
|
<para>
|
||||||
Fix vacuuming of tuples that were updated while key-share locked
|
Fix vacuuming of tuples that were updated while key-share locked
|
||||||
|
|||||||
@ -33,6 +33,28 @@
|
|||||||
|
|
||||||
<itemizedlist>
|
<itemizedlist>
|
||||||
|
|
||||||
|
<listitem>
|
||||||
|
<para>
|
||||||
|
Ensure that all temporary files made
|
||||||
|
by <application>pg_upgrade</application> are non-world-readable
|
||||||
|
(Tom Lane, Noah Misch)
|
||||||
|
</para>
|
||||||
|
|
||||||
|
<para>
|
||||||
|
<application>pg_upgrade</application> normally restricts its
|
||||||
|
temporary files to be readable and writable only by the calling user.
|
||||||
|
But the temporary file containing <literal>pg_dumpall -g</literal>
|
||||||
|
output would be group- or world-readable, or even writable, if the
|
||||||
|
user's <literal>umask</literal> setting allows. In typical usage on
|
||||||
|
multi-user machines, the <literal>umask</literal> and/or the working
|
||||||
|
directory's permissions would be tight enough to prevent problems;
|
||||||
|
but there may be people using <application>pg_upgrade</application>
|
||||||
|
in scenarios where this oversight would permit disclosure of database
|
||||||
|
passwords to unfriendly eyes.
|
||||||
|
(CVE-2018-1053)
|
||||||
|
</para>
|
||||||
|
</listitem>
|
||||||
|
|
||||||
<listitem>
|
<listitem>
|
||||||
<para>
|
<para>
|
||||||
Fix vacuuming of tuples that were updated while key-share locked
|
Fix vacuuming of tuples that were updated while key-share locked
|
||||||
|
|||||||
@ -33,6 +33,28 @@
|
|||||||
|
|
||||||
<itemizedlist>
|
<itemizedlist>
|
||||||
|
|
||||||
|
<listitem>
|
||||||
|
<para>
|
||||||
|
Ensure that all temporary files made
|
||||||
|
by <application>pg_upgrade</application> are non-world-readable
|
||||||
|
(Tom Lane, Noah Misch)
|
||||||
|
</para>
|
||||||
|
|
||||||
|
<para>
|
||||||
|
<application>pg_upgrade</application> normally restricts its
|
||||||
|
temporary files to be readable and writable only by the calling user.
|
||||||
|
But the temporary file containing <literal>pg_dumpall -g</literal>
|
||||||
|
output would be group- or world-readable, or even writable, if the
|
||||||
|
user's <literal>umask</literal> setting allows. In typical usage on
|
||||||
|
multi-user machines, the <literal>umask</literal> and/or the working
|
||||||
|
directory's permissions would be tight enough to prevent problems;
|
||||||
|
but there may be people using <application>pg_upgrade</application>
|
||||||
|
in scenarios where this oversight would permit disclosure of database
|
||||||
|
passwords to unfriendly eyes.
|
||||||
|
(CVE-2018-1053)
|
||||||
|
</para>
|
||||||
|
</listitem>
|
||||||
|
|
||||||
<listitem>
|
<listitem>
|
||||||
<para>
|
<para>
|
||||||
Fix vacuuming of tuples that were updated while key-share locked
|
Fix vacuuming of tuples that were updated while key-share locked
|
||||||
|
|||||||
@ -39,6 +39,28 @@
|
|||||||
|
|
||||||
<itemizedlist>
|
<itemizedlist>
|
||||||
|
|
||||||
|
<listitem>
|
||||||
|
<para>
|
||||||
|
Ensure that all temporary files made
|
||||||
|
by <application>pg_upgrade</application> are non-world-readable
|
||||||
|
(Tom Lane, Noah Misch)
|
||||||
|
</para>
|
||||||
|
|
||||||
|
<para>
|
||||||
|
<application>pg_upgrade</application> normally restricts its
|
||||||
|
temporary files to be readable and writable only by the calling user.
|
||||||
|
But the temporary file containing <literal>pg_dumpall -g</literal>
|
||||||
|
output would be group- or world-readable, or even writable, if the
|
||||||
|
user's <literal>umask</literal> setting allows. In typical usage on
|
||||||
|
multi-user machines, the <literal>umask</literal> and/or the working
|
||||||
|
directory's permissions would be tight enough to prevent problems;
|
||||||
|
but there may be people using <application>pg_upgrade</application>
|
||||||
|
in scenarios where this oversight would permit disclosure of database
|
||||||
|
passwords to unfriendly eyes.
|
||||||
|
(CVE-2018-1053)
|
||||||
|
</para>
|
||||||
|
</listitem>
|
||||||
|
|
||||||
<listitem>
|
<listitem>
|
||||||
<para>
|
<para>
|
||||||
Fix vacuuming of tuples that were updated while key-share locked
|
Fix vacuuming of tuples that were updated while key-share locked
|
||||||
|
|||||||
Loading…
x
Reference in New Issue
Block a user