🌐 AI搜索 & 代理 主页
Skip to content

Commit 9a219bb

Browse files
committed
Last-minute updates for release notes.
Security: CVE-2025-12817, CVE-2025-12818
1 parent 8a2530e commit 9a219bb

File tree

1 file changed

+61
-0
lines changed

1 file changed

+61
-0
lines changed

doc/src/sgml/release-13.sgml

Lines changed: 61 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -41,6 +41,67 @@
4141

4242
<listitem>
4343
<!--
44+
Author: Nathan Bossart <nathan@postgresql.org>
45+
Branch: master [5e4fcbe53] 2025-11-10 09:00:00 -0600
46+
Branch: REL_18_STABLE [00eb646ea] 2025-11-10 09:00:00 -0600
47+
Branch: REL_17_STABLE [e2fb3dfa8] 2025-11-10 09:00:00 -0600
48+
Branch: REL_16_STABLE [d20abb587] 2025-11-10 09:00:00 -0600
49+
Branch: REL_15_STABLE [2393d374a] 2025-11-10 09:00:00 -0600
50+
Branch: REL_14_STABLE [95cce5669] 2025-11-10 09:00:00 -0600
51+
Branch: REL_13_STABLE [8a2530ebc] 2025-11-10 09:00:00 -0600
52+
-->
53+
<para>
54+
Check for <literal>CREATE</literal> privileges on the schema
55+
in <command>CREATE STATISTICS</command> (Jelte Fennema-Nio)
56+
<ulink url="&commit_baseurl;8a2530ebc">&sect;</ulink>
57+
</para>
58+
59+
<para>
60+
This omission allowed table owners to create statistics in any
61+
schema, potentially leading to unexpected naming conflicts.
62+
</para>
63+
64+
<para>
65+
The <productname>PostgreSQL</productname> Project thanks
66+
Jelte Fennema-Nio for reporting this problem.
67+
(CVE-2025-12817)
68+
</para>
69+
</listitem>
70+
71+
<listitem>
72+
<!--
73+
Author: Jacob Champion <jchampion@postgresql.org>
74+
Branch: master [600086f47] 2025-11-10 06:20:33 -0800
75+
Branch: REL_18_STABLE [7eb8fcad8] 2025-11-10 06:03:01 -0800
76+
Branch: REL_17_STABLE [f5999f018] 2025-11-10 06:03:03 -0800
77+
Branch: REL_16_STABLE [585fd9b3c] 2025-11-10 06:03:04 -0800
78+
Branch: REL_15_STABLE [91421565f] 2025-11-10 06:03:05 -0800
79+
Branch: REL_14_STABLE [96d2c7e96] 2025-11-10 06:03:05 -0800
80+
Branch: REL_13_STABLE [d6f0c0d6d] 2025-11-10 06:03:06 -0800
81+
-->
82+
<para>
83+
Avoid integer overflow in allocation-size calculations
84+
within <application>libpq</application> (Jacob Champion)
85+
<ulink url="&commit_baseurl;d6f0c0d6d">&sect;</ulink>
86+
</para>
87+
88+
<para>
89+
Several places in <application>libpq</application> were not
90+
sufficiently careful about computing the required size of a memory
91+
allocation. Sufficiently large inputs could cause integer overflow,
92+
resulting in an undersized buffer, which would then lead to writing
93+
past the end of the buffer.
94+
</para>
95+
96+
<para>
97+
The <productname>PostgreSQL</productname> Project thanks Aleksey
98+
Solovev of Positive Technologies for reporting this problem.
99+
(CVE-2025-12818)
100+
</para>
101+
</listitem>
102+
103+
<listitem>
104+
<!--
44105
Author: Tom Lane <tgl@sss.pgh.pa.us>
45106
Branch: master [cdf7feb96] 2025-09-13 16:55:51 -0400
46107
Branch: REL_18_STABLE Release: REL_18_0 [802308693] 2025-09-13 16:55:51 -0400

0 commit comments

Comments
 (0)