8000 Last-minute updates for release notes. · shawn712/postgres@e7bae63 · GitHub
[go: up one dir, main page]
Skip to content

Commit e7bae63

Browse files
tglsfdctglsfdc
committed
Last-minute updates for release notes.
Security: CVE-2017-12172, CVE-2017-15098, CVE-2017-15099
1 parent 70846ee commit e7bae63

File tree

3 files changed

+109
-0
lines changed

3 files changed

+109
-0
lines changed

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

Lines changed: 25 additions & 0 deletions
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

Lines changed: 42 additions & 0 deletions
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

Lines changed: 42 additions & 0 deletions
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,

0 commit comments

Comments
 (0)
0