Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Commit d69c071

Browse files
tglsfdctglsfdc
committed
Last-minute updates for release notes.
Security: CVE-2017-12172, CVE-2017-15098, CVE-2017-15099
1 parent 38e8256 commit d69c071

File tree

5 files changed

+257
-2
lines changed

5 files changed

+257
-2
lines changed

‎doc/src/sgml/release-9.2.sgml

+25
Original file line numberDiff line numberDiff line change
@@ -40,6 +40,31 @@
4040

4141
<itemizedlist>
4242

43+
<listitem>
44+
<para>
45+
Fix sample server-start scripts to become <literal>$PGUSER</literal>
46+
before opening <literal>$PGLOG</literal> (Noah Misch)
47+
</para>
48+
49+
<para>
50+
Previously, the postmaster log file was opened while still running as
51+
root. The database owner could therefore mount an attack against
52+
another system user by making <literal>$PGLOG</literal> be a symbolic
53+
link to some other file, which would then become corrupted by appending
54+
log messages.
55+
</para>
56+
57+
<para>
58+
By default, these scripts are not installed anywhere. Users who have
59+
made use of them will need to manually recopy them, or apply the same
60+
changes to their modified versions. If the
61+
existing <literal>$PGLOG</literal> file is root-owned, it will need to
62+
be removed or renamed out of the way before restarting the server with
63+
the corrected script.
64+
(CVE-2017-12172)
65+
</para>
66+
</listitem>
67+
4368
<listitem>
4469
<para>
4570
Properly reject attempts to convert infinite float values to

‎doc/src/sgml/release-9.3.sgml

+42
Original file line numberDiff line numberDiff line change
@@ -34,6 +34,48 @@
3434

3535
<itemizedlist>
3636

37+
<listitem>
38+
<para>
39+
Fix crash due to rowtype mismatch
40+
in <function>json{b}_populate_recordset()</function>
41+
(Michael Paquier, Tom Lane)
42+
</para>
43+
44+
<para>
45+
These functions used the result rowtype specified in the <literal>FROM
46+
... AS</literal> clause without checking that it matched the actual
47+
rowtype of the supplied tuple value. If it didn't, that would usually
48+
result in a crash, though disclosure of server memory contents seems
49+
possible as well.
50+
(CVE-2017-15098)
51+
</para>
52+
</listitem>
53+
54+
<listitem>
55+
<para>
56+
Fix sample server-start scripts to become <literal>$PGUSER</literal>
57+
before opening <literal>$PGLOG</literal> (Noah Misch)
58+
</para>
59+
60+
<para>
61+
Previously, the postmaster log file was opened while still running as
62+
root. The database owner could therefore mount an attack against
63+
another system user by making <literal>$PGLOG</literal> be a symbolic
64+
link to some other file, which would then become corrupted by appending
65+
log messages.
66+
</para>
67+
68+
<para>
69+
By default, these scripts are not installed anywhere. Users who have
70+
made use of them will need to manually recopy them, or apply the same
71+
changes to their modified versions. If the
72+
existing <literal>$PGLOG</literal> file is root-owned, it will need to
73+
be removed or renamed out of the way before restarting the server with
74+
the corrected script.
75+
(CVE-2017-12172)
76+
</para>
77+
</listitem>
78+
3779
<listitem>
3880
<para>
3981
Properly reject attempts to convert infinite float values to

‎doc/src/sgml/release-9.4.sgml

+42
Original file line numberDiff line numberDiff line change
@@ -33,6 +33,48 @@
3333

3434
<itemizedlist>
3535

36+
<listitem>
37+
<para>
38+
Fix crash due to rowtype mismatch
39+
in <function>json{b}_populate_recordset()</function>
40+
(Michael Paquier, Tom Lane)
41+
</para>
42+
43+
<para>
44+
These functions used the result rowtype specified in the <literal>FROM
45+
... AS</literal> clause without checking that it matched the actual
46+
rowtype of the supplied tuple value. If it didn't, that would usually
47+
result in a crash, though disclosure of server memory contents seems
48+
possible as well.
49+
(CVE-2017-15098)
50+
</para>
51+
</listitem>
52+
53+
<listitem>
54+
<para>
55+
Fix sample server-start scripts to become <literal>$PGUSER</literal>
56+
before opening <literal>$PGLOG</literal> (Noah Misch)
57+
</para>
58+
59+
<para>
60+
Previously, the postmaster log file was opened while still running as
61+
root. The database owner could therefore mount an attack against
62+
another system user by making <literal>$PGLOG</literal> be a symbolic
63+
link to some other file, which would then become corrupted by appending
64+
log messages.
65+
</para>
66+
67+
<para>
68+
By default, these scripts are not installed anywhere. Users who have
69+
made use of them will need to manually recopy them, or apply the same
70+
changes to their modified versions. If the
71+
existing <literal>$PGLOG</literal> file is root-owned, it will need to
72+
be removed or renamed out of the way before restarting the server with
73+
the corrected script.
74+
(CVE-2017-12172)
75+
</para>
76+
</listitem>
77+
3678
<listitem>
3779
<para>
3880
Fix crash when logical decoding is invoked from a SPI-using function,

‎doc/src/sgml/release-9.5.sgml

+74-1
Original file line numberDiff line numberDiff line change
@@ -23,7 +23,7 @@
2323
</para>
2424

2525
<para>
26-
However, if you use BRIN indexes, see the first changelog entry below.
26+
However, if you use BRIN indexes, see the fourth changelog entry below.
2727
</para>
2828

2929
<para>
@@ -37,6 +37,66 @@
3737

3838
<itemizedlist>
3939

40+
<listitem>
41+
<para>
42+
Ensure that <literal>INSERT ... ON CONFLICT DO UPDATE</literal> checks
43+
table permissions and RLS policies in all cases (Dean Rasheed)
44+
</para>
45+
46+
<para>
47+
The update path of <literal>INSERT ... ON CONFLICT DO UPDATE</literal>
48+
requires <literal>SELECT</literal> permission on the columns of the
49+
arbiter index, but it failed to check for that in the case of an
50+
arbiter specified by constraint name.
51+
In addition, for a table with row level security enabled, it failed to
52+
check updated rows against the table's <literal>SELECT</literal>
53+
policies (regardless of how the arbiter index was specified).
54+
(CVE-2017-15099)
55+
</para>
56+
</listitem>
57+
58+
<listitem>
59+
<para>
60+
Fix crash due to rowtype mismatch
61+
in <function>json{b}_populate_recordset()</function>
62+
(Michael Paquier, Tom Lane)
63+
</para>
64+
65+
<para>
66+
These functions used the result rowtype specified in the <literal>FROM
67+
... AS</literal> clause without checking that it matched the actual
68+
rowtype of the supplied tuple value. If it didn't, that would usually
69+
result in a crash, though disclosure of server memory contents seems
70+
possible as well.
71+
(CVE-2017-15098)
72+
</para>
73+
</listitem>
74+
75+
<listitem>
76+
<para>
77+
Fix sample server-start scripts to become <literal>$PGUSER</literal>
78+
before opening <literal>$PGLOG</literal> (Noah Misch)
79+
</para>
80+
81+
<para>
82+
Previously, the postmaster log file was opened while still running as
83+
root. The database owner could therefore mount an attack against
84+
another system user by making <literal>$PGLOG</literal> be a symbolic
85+
link to some other file, which would then become corrupted by appending
86+
log messages.
87+
</para>
88+
89+
<para>
90+
By default, these scripts are not installed anywhere. Users who have
91+
made use of them will need to manually recopy them, or apply the same
92+
changes to their modified versions. If the
93+
existing <literal>$PGLOG</literal> file is root-owned, it will need to
94+
be removed or renamed out of the way before restarting the server with
95+
the corrected script.
96+
(CVE-2017-12172)
97+
</para>
98+
</listitem>
99+
40100
<listitem>
41101
<para>
42102
Fix BRIN index summarization to handle concurrent table extension
@@ -259,6 +319,19 @@
259319
</para>
260320
</listitem>
261321

322+
<listitem>
323+
<para>
324+
Fix missing temp-install prerequisites
325+
for <literal>check</literal>-like Make targets (Noah Misch)
326+
</para>
327+
328+
<para>
329+
Some non-default test procedures that are meant to work
330+
like <literal>make check</literal> failed to ensure that the temporary
331+
installation was up to date.
332+
</para>
333+
</listitem>
334+
262335
<listitem>
263336
<para>
264337
Sync our copy of the timezone library with IANA release tzcode2017c

‎doc/src/sgml/release-9.6.sgml

+74-1
Original file line numberDiff line numberDiff line change
@@ -23,7 +23,7 @@
2323
</para>
2424

2525
<para>
26-
However, if you use BRIN indexes, see the first changelog entry below.
26+
However, if you use BRIN indexes, see the fourth changelog entry below.
2727
</para>
2828

2929
<para>
@@ -37,6 +37,66 @@
3737

3838
<itemizedlist>
3939

40+
<listitem>
41+
<para>
42+
Ensure that <literal>INSERT ... ON CONFLICT DO UPDATE</literal> checks
43+
table permissions and RLS policies in all cases (Dean Rasheed)
44+
</para>
45+
46+
<para>
47+
The update path of <literal>INSERT ... ON CONFLICT DO UPDATE</literal>
48+
requires <literal>SELECT</literal> permission on the columns of the
49+
arbiter index, but it failed to check for that in the case of an
50+
arbiter specified by constraint name.
51+
In addition, for a table with row level security enabled, it failed to
52+
check updated rows against the table's <literal>SELECT</literal>
53+
policies (regardless of how the arbiter index was specified).
54+
(CVE-2017-15099)
55+
</para>
56+
</listitem>
57+
58+
<listitem>
59+
<para>
60+
Fix crash due to rowtype mismatch
61+
in <function>json{b}_populate_recordset()</function>
62+
(Michael Paquier, Tom Lane)
63+
</para>
64+
65+
<para>
66+
These functions used the result rowtype specified in the <literal>FROM
67+
... AS</literal> clause without checking that it matched the actual
68+
rowtype of the supplied tuple value. If it didn't, that would usually
69+
result in a crash, though disclosure of server memory contents seems
70+
possible as well.
71+
(CVE-2017-15098)
72+
</para>
73+
</listitem>
74+
75+
<listitem>
76+
<para>
77+
Fix sample server-start scripts to become <literal>$PGUSER</literal>
78+
before opening <literal>$PGLOG</literal> (Noah Misch)
79+
</para>
80+
81+
<para>
82+
Previously, the postmaster log file was opened while still running as
83+
root. The database owner could therefore mount an attack against
84+
another system user by making <literal>$PGLOG</literal> be a symbolic
85+
link to some other file, which would then become corrupted by appending
86+
log messages.
87+
</para>
88+
89+
<para>
90+
By default, these scripts are not installed anywhere. Users who have
91+
made use of them will need to manually recopy them, or apply the same
92+
changes to their modified versions. If the
93+
existing <literal>$PGLOG</literal> file is root-owned, it will need to
94+
be removed or renamed out of the way before restarting the server with
95+
the corrected script.
96+
(CVE-2017-12172)
97+
</para>
98+
</listitem>
99+
40100
<listitem>
41101
<para>
42102
Fix BRIN index summarization to handle concurrent table extension
@@ -459,6 +519,19 @@ Branch: REL9_6_STABLE [407e66078] 2017-09-14 01:17:15 +0200
459519
</para>
460520
</listitem>
461521

522+
<listitem>
523+
<para>
524+
Fix missing temp-install prerequisites
525+
for <literal>check</literal>-like Make targets (Noah Misch)
526+
</para>
527+
528+
<para>
529+
Some non-default test procedures that are meant to work
530+
like <literal>make check</literal> failed to ensure that the temporary
531+
installation was up to date.
532+
</para>
533+
</listitem>
534+
462535
<listitem>
463536
<!--
464537
Author: Tom Lane <[email protected]>

0 commit comments

Comments
 (0)