Skip to content

Commit 8ff2825

Browse files
tglsfdctglsfdc
committed
Last-minute updates for release notes.
Security: CVE-2023-5868, CVE-2023-5869, CVE-2023-5870
1 parent d267cea commit 8ff2825

File tree

1 file changed

+114
-1
lines changed

1 file changed

+114
-1
lines changed

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

Lines changed: 114 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -24,7 +24,7 @@
2424

2525
<para>
2626
However, if you use GiST indexes, it may be advisable to reindex them;
27-
see the first changelog entry below.
27+
see the fourth changelog entry below.
2828
</para>
2929

3030
<para>
@@ -40,6 +40,119 @@
4040

4141
<listitem>
4242
<!--
43+
Author: Tom Lane <tgl@sss.pgh.pa.us>
44+
Branch: master [3b0776fde] 2023-11-06 10:38:00 -0500
45+
Branch: REL_16_STABLE [d3d1e2509] 2023-11-06 10:38:00 -0500
46+
Branch: REL_15_STABLE [4f4a422fb] 2023-11-06 10:38:00 -0500
47+
Branch: REL_14_STABLE [9146d0d65] 2023-11-06 10:38:00 -0500
48+
Branch: REL_13_STABLE [d3de70fdb] 2023-11-06 10:38:00 -0500
49+
Branch: REL_12_STABLE [e911afd09] 2023-11-06 10:38:00 -0500
50+
Branch: REL_11_STABLE [8c6633f4d] 2023-11-06 10:38:00 -0500
51+
-->
52+
<para>
53+
Fix handling of unknown-type arguments
54+
in <literal>DISTINCT</literal> <type>"any"</type> aggregate
55+
functions (Tom Lane)
56+
</para>
57+
58+
<para>
59+
This error led to a <type>text</type>-type value being interpreted
60+
as an <type>unknown</type>-type value (that is, a zero-terminated
61+
string) at runtime. This could result in disclosure of server
62+
memory following the <type>text</type> value.
63+
</para>
64+
65+
<para>
66+
The <productname>PostgreSQL</productname> Project thanks Jingzhou Fu
67+
for reporting this problem.
68+
(CVE-2023-5868)
69+
</para>
70+
</listitem>
71+
72+
<listitem>
73+
<!--
74+
Author: Tom Lane <tgl@sss.pgh.pa.us>
75+
Branch: master [18b585155] 2023-11-06 10:56:43 -0500
76+
Branch: REL_16_STABLE [e24daa94b] 2023-11-06 10:56:43 -0500
77+
Branch: REL_15_STABLE [3bc6bc3ee] 2023-11-06 10:56:43 -0500
78+
Branch: REL_14_STABLE [edc0a8d82] 2023-11-06 10:56:43 -0500
79+
Branch: REL_13_STABLE [26c599beb] 2023-11-06 10:56:43 -0500
80+
Branch: REL_12_STABLE [d267cea24] 2023-11-06 10:56:43 -0500
81+
Branch: REL_11_STABLE [c48008f59] 2023-11-06 10:56:43 -0500
82+
-->
83+
<para>
84+
Detect integer overflow while computing new array dimensions
85+
(Tom Lane)
86+
</para>
87+
88+
<para>
89+
When assigning new elements to array subscripts that are outside the
90+
current array bounds, an undetected integer overflow could occur in
91+
edge cases. Memory stomps that are potentially exploitable for
92+
arbitrary code execution are possible, and so is disclosure of
93+
server memory.
94+
</para>
95+
96+
<para>
97+
The <productname>PostgreSQL</productname> Project thanks Pedro
98+
Gallegos for reporting this problem.
99+
(CVE-2023-5869)
100+
</para>
101+
</listitem>
102+
103+
<listitem>
104+
<!--
105+
Author: Noah Misch <noah@leadboat.com>
106+
Branch: master [3a9b18b30] 2023-11-06 06:14:13 -0800
107+
Branch: REL_16_STABLE [785412731] 2023-11-06 06:14:16 -0800
108+
Branch: REL_15_STABLE [595c988c9] 2023-11-06 06:14:16 -0800
109+
Branch: REL_14_STABLE [508acb901] 2023-11-06 06:14:17 -0800
110+
Branch: REL_13_STABLE [28b609550] 2023-11-06 06:14:17 -0800
111+
Branch: REL_12_STABLE [2893f2f40] 2023-11-06 06:14:17 -0800
112+
Branch: REL_11_STABLE [e082734c8] 2023-11-06 06:14:18 -0800
113+
Author: Noah Misch <noah@leadboat.com>
114+
Branch: master [b72de09a1] 2023-11-06 06:14:13 -0800
115+
Branch: REL_16_STABLE [2c3c5ec49] 2023-11-06 06:14:16 -0800
116+
Branch: REL_15_STABLE [fbc371909] 2023-11-06 06:14:16 -0800
117+
Branch: REL_14_STABLE [ecd5d240c] 2023-11-06 06:14:17 -0800
118+
Branch: REL_13_STABLE [2c7a2a00a] 2023-11-06 06:14:17 -0800
119+
Branch: REL_12_STABLE [7bbf4d037] 2023-11-06 06:14:17 -0800
120+
Branch: REL_11_STABLE [a27be40c1] 2023-11-06 06:14:18 -0800
121+
-->
122+
<para>
123+
Prevent the <literal>pg_signal_backend</literal> role from
124+
signalling background workers and autovacuum processes
125+
(Noah Misch, Jelte Fennema-Nio)
126+
</para>
127+
128+
<para>
129+
The documentation says that <literal>pg_signal_backend</literal>
130+
cannot issue signals to superuser-owned processes. It was able to
131+
signal these background processes, though, because they advertise a
132+
role OID of zero. Treat that as indicating superuser ownership.
133+
The security implications of cancelling one of these process types
134+
are fairly small so far as the core code goes (we'll just start
135+
another one), but extensions might add background workers that are
136+
more vulnerable.
137+
</para>
138+
139+
<para>
140+
Also ensure that the <varname>is_superuser</varname> parameter is
141+
set correctly in such processes. No specific security consequences
142+
are known for that oversight, but it might be significant for some
143+
extensions.
144+
</para>
145+
146+
<para>
147+
The <productname>PostgreSQL</productname> Project thanks
148+
Hemanth Sandrana and Mahendrakar Srinivasarao
149+
for reporting this problem.
150+
(CVE-2023-5870)
151+
</para>
152+
</listitem>
153+
154+
<listitem>
155+
<!--
43156
Author: Heikki Linnakangas <heikki.linnakangas@iki.fi>
44157
Branch: master [28d3c2ddc] 2023-09-26 14:14:49 +0300
45158
Branch: REL_16_STABLE [d7f521325] 2023-09-26 14:15:01 +0300

0 commit comments

Comments
 (0)