Last-minute updates for release notes.
authorTom Lane <[email protected]>
Mon, 17 Jun 2019 14:53:45 +0000 (10:53 -0400)
committerTom Lane <[email protected]>
Mon, 17 Jun 2019 14:53:45 +0000 (10:53 -0400)
Security: CVE-2019-10164

doc/src/sgml/release-10.sgml

index 5f5e6f4c4a67651f364e808c9683f7ce3aa286fb..126a89e407649ec2f4410758063aad55da7c7f81 100644 (file)
 
     <listitem>
 <!--
+Author: Michael Paquier <[email protected]>
+Branch: master [09ec55b93] 2019-06-17 21:48:17 +0900
+Branch: REL_11_STABLE [4c779ce32] 2019-06-17 21:48:25 +0900
+Branch: REL_10_STABLE [90adc16ea] 2019-06-17 21:48:34 +0900
+Author: Michael Paquier <[email protected]>
+Branch: master [b67421178] 2019-06-17 22:13:57 +0900
+Branch: REL_11_STABLE [27c464e42] 2019-06-17 22:14:04 +0900
+Branch: REL_10_STABLE [d72a7e4da] 2019-06-17 22:14:09 +0900
+-->
+     <para>
+      Fix buffer-overflow hazards in SCRAM verifier parsing
+      (Jonathan Katz, Heikki Linnakangas, Michael Paquier)
+     </para>
+
+     <para>
+      Any authenticated user could cause a stack-based buffer overflow by
+      changing their own password to a purpose-crafted value.  In addition
+      to the ability to crash the <productname>PostgreSQL</productname>
+      server, this could suffice for executing arbitrary code as
+      the <productname>PostgreSQL</productname> operating system account.
+     </para>
+
+     <para>
+      A similar overflow hazard existed
+      in <application>libpq</application>, which could allow a rogue
+      server to crash a client or perhaps execute arbitrary code as the
+      client's operating system account.
+     </para>
+
+     <para>
+      The <productname>PostgreSQL</productname> Project thanks Alexander
+      Lakhin for reporting this problem.  (CVE-2019-10164)
+     </para>
+    </listitem>
+
+    <listitem>
+<!--
 Author: Tom Lane <[email protected]>
 Branch: master [e76de8861] 2019-06-12 12:29:39 -0400
 Branch: REL_11_STABLE [0b6edb9fb] 2019-06-12 12:29:41 -0400
@@ -79,20 +116,6 @@ Branch: REL_10_STABLE [99efd8d72] 2019-05-23 15:39:17 +0100
 
     <listitem>
 <!--
-Author: Alvaro Herrera <[email protected]>
-Branch: master [de87a084c] 2019-06-13 17:28:24 -0400
-Branch: REL_11_STABLE [85600b7b5] 2019-06-13 17:28:24 -0400
-Branch: REL_10_STABLE [14a91a8fc] 2019-06-13 17:28:24 -0400
-Branch: REL9_6_STABLE [cb2398d80] 2019-06-13 17:28:24 -0400
--->
-     <para>
-      Avoid spurious deadlock failures when upgrading a tuple lock (Oleksii
-      Kliukin)
-     </para>
-    </listitem>
-
-    <listitem>
-<!--
 Author: Tom Lane <[email protected]>
 Branch: master [24c19e9f6] 2019-05-09 16:53:05 -0400
 Branch: REL_11_STABLE [e7eed0baa] 2019-05-09 16:52:49 -0400