File tree Expand file tree Collapse file tree 2 files changed +67
-0
lines changed Expand file tree Collapse file tree 2 files changed +67
-0
lines changed Original file line number Diff line number Diff line change 40
40
41
41
<itemizedlist>
42
42
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
+
43
68
<listitem>
44
69
<para>
45
70
Properly reject attempts to convert infinite float values to
Original file line number Diff line number Diff line change 34
34
35
35
<itemizedlist>
36
36
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
+
37
79
<listitem>
38
80
<para>
39
81
Properly reject attempts to convert infinite float values to
You can’t perform that action at this time.
0 commit comments