|
1 | 1 | <!-- doc/src/sgml/release-15.sgml --> |
2 | 2 | <!-- See header comment in release.sgml about typical markup --> |
3 | 3 |
|
| 4 | + <sect1 id="release-15-12"> |
| 5 | + <title>Release 15.12</title> |
| 6 | + |
| 7 | + <formalpara> |
| 8 | + <title>Release date:</title> |
| 9 | + <para>2025-02-20</para> |
| 10 | + </formalpara> |
| 11 | + |
| 12 | + <para> |
| 13 | + This release contains a few fixes from 15.11. |
| 14 | + For information about new features in major release 15, see |
| 15 | + <xref linkend="release-15"/>. |
| 16 | + </para> |
| 17 | + |
| 18 | + <sect2> |
| 19 | + <title>Migration to Version 15.12</title> |
| 20 | + |
| 21 | + <para> |
| 22 | + A dump/restore is not required for those running 15.X. |
| 23 | + </para> |
| 24 | + |
| 25 | + <para> |
| 26 | + However, if you are upgrading from a version earlier than 15.9, |
| 27 | + see <xref linkend="release-15-9"/>. |
| 28 | + </para> |
| 29 | + </sect2> |
| 30 | + |
| 31 | + <sect2> |
| 32 | + <title>Changes</title> |
| 33 | + |
| 34 | + <itemizedlist> |
| 35 | + |
| 36 | + <listitem> |
| 37 | +<!-- |
| 38 | +Author: Andres Freund <andres@anarazel.de> |
| 39 | +Branch: master [efdadeb22] 2025-02-14 18:09:19 -0500 |
| 40 | +Branch: REL_17_STABLE [a92db3d02] 2025-02-14 18:09:21 -0500 |
| 41 | +Branch: REL_16_STABLE [111f4dd27] 2025-02-14 18:09:23 -0500 |
| 42 | +Branch: REL_15_STABLE [22ffbbf24] 2025-02-14 18:09:24 -0500 |
| 43 | +Branch: REL_14_STABLE [985908df1] 2025-02-14 18:09:25 -0500 |
| 44 | +Branch: REL_13_STABLE [1f7a05324] 2025-02-14 18:09:27 -0500 |
| 45 | +Author: Tom Lane <tgl@sss.pgh.pa.us> |
| 46 | +Branch: master [9f45e6a91] 2025-02-15 16:20:21 -0500 |
| 47 | +Branch: REL_17_STABLE [3abe6e04c] 2025-02-15 16:20:21 -0500 |
| 48 | +Branch: REL_16_STABLE [991a60a9f] 2025-02-15 16:20:21 -0500 |
| 49 | +Branch: REL_15_STABLE [e782a63cc] 2025-02-15 16:20:21 -0500 |
| 50 | +Branch: REL_14_STABLE [c08309584] 2025-02-15 16:20:21 -0500 |
| 51 | +Branch: REL_13_STABLE [d6d29b213] 2025-02-15 16:20:21 -0500 |
| 52 | +Author: Tom Lane <tgl@sss.pgh.pa.us> |
| 53 | +Branch: master [a7f95859e] 2025-02-16 12:46:35 -0500 |
| 54 | +Branch: REL_17_STABLE [3977bd298] 2025-02-16 12:46:35 -0500 |
| 55 | +Branch: REL_16_STABLE [644b7d686] 2025-02-16 12:46:35 -0500 |
| 56 | +Branch: REL_15_STABLE [2226a2e26] 2025-02-16 12:46:35 -0500 |
| 57 | +Branch: REL_14_STABLE [f864a4cdf] 2025-02-16 12:46:35 -0500 |
| 58 | +Branch: REL_13_STABLE [9f052613e] 2025-02-16 12:46:35 -0500 |
| 59 | +--> |
| 60 | + <para> |
| 61 | + Improve behavior of <application>libpq</application>'s quoting |
| 62 | + functions (Andres Freund, Tom Lane) |
| 63 | + <ulink url="&commit_baseurl;22ffbbf24">§</ulink> |
| 64 | + <ulink url="&commit_baseurl;e782a63cc">§</ulink> |
| 65 | + <ulink url="&commit_baseurl;2226a2e26">§</ulink> |
| 66 | + </para> |
| 67 | + |
| 68 | + <para> |
| 69 | + The changes made for CVE-2025-1094 had one serious oversight: |
| 70 | + <function>PQescapeLiteral()</function> |
| 71 | + and <function>PQescapeIdentifier()</function> failed to honor their |
| 72 | + string length parameter, instead always reading to the input |
| 73 | + string's trailing null. This resulted in including unwanted text in |
| 74 | + the output, if the caller intended to truncate the string via the |
| 75 | + length parameter. With very bad luck it could cause a crash due to |
| 76 | + reading off the end of memory. |
| 77 | + </para> |
| 78 | + |
| 79 | + <para> |
| 80 | + In addition, modify all these quoting functions so that when invalid |
| 81 | + encoding is detected, an invalid sequence is substituted for just |
| 82 | + the first byte of the presumed character, not all of it. This |
| 83 | + reduces the risk of problems if a calling application performs |
| 84 | + additional processing on the quoted string. |
| 85 | + </para> |
| 86 | + </listitem> |
| 87 | + |
| 88 | + </itemizedlist> |
| 89 | + |
| 90 | + </sect2> |
| 91 | + </sect1> |
| 92 | + |
4 | 93 | <sect1 id="release-15-11"> |
5 | 94 | <title>Release 15.11</title> |
6 | 95 |
|
|