|
35 | 35 |
|
36 | 36 | <listitem> |
37 | 37 | <!-- |
| 38 | +Author: Michael Paquier <michael@paquier.xyz> |
| 39 | +Branch: master [09ec55b93] 2019-06-17 21:48:17 +0900 |
| 40 | +Branch: REL_11_STABLE [4c779ce32] 2019-06-17 21:48:25 +0900 |
| 41 | +Branch: REL_10_STABLE [90adc16ea] 2019-06-17 21:48:34 +0900 |
| 42 | +Author: Michael Paquier <michael@paquier.xyz> |
| 43 | +Branch: master [b67421178] 2019-06-17 22:13:57 +0900 |
| 44 | +Branch: REL_11_STABLE [27c464e42] 2019-06-17 22:14:04 +0900 |
| 45 | +Branch: REL_10_STABLE [d72a7e4da] 2019-06-17 22:14:09 +0900 |
| 46 | +--> |
| 47 | + <para> |
| 48 | + Fix buffer-overflow hazards in SCRAM verifier parsing |
| 49 | + (Jonathan Katz, Heikki Linnakangas, Michael Paquier) |
| 50 | + </para> |
| 51 | + |
| 52 | + <para> |
| 53 | + Any authenticated user could cause a stack-based buffer overflow by |
| 54 | + changing their own password to a purpose-crafted value. In addition |
| 55 | + to the ability to crash the <productname>PostgreSQL</productname> |
| 56 | + server, this could suffice for executing arbitrary code as |
| 57 | + the <productname>PostgreSQL</productname> operating system account. |
| 58 | + </para> |
| 59 | + |
| 60 | + <para> |
| 61 | + A similar overflow hazard existed |
| 62 | + in <application>libpq</application>, which could allow a rogue |
| 63 | + server to crash a client or perhaps execute arbitrary code as the |
| 64 | + client's operating system account. |
| 65 | + </para> |
| 66 | + |
| 67 | + <para> |
| 68 | + The <productname>PostgreSQL</productname> Project thanks Alexander |
| 69 | + Lakhin for reporting this problem. (CVE-2019-10164) |
| 70 | + </para> |
| 71 | + </listitem> |
| 72 | + |
| 73 | + <listitem> |
| 74 | +<!-- |
38 | 75 | Author: Tom Lane <tgl@sss.pgh.pa.us> |
39 | 76 | Branch: master [6630ccad7] 2019-05-17 19:44:34 -0400 |
40 | 77 | Branch: REL_11_STABLE [592d5d75b] 2019-05-17 19:44:19 -0400 |
@@ -128,20 +165,6 @@ Branch: REL_11_STABLE [9fea0b0e2] 2019-05-19 18:16:41 -0700 |
128 | 165 |
|
129 | 166 | <listitem> |
130 | 167 | <!-- |
131 | | -Author: Alvaro Herrera <alvherre@alvh.no-ip.org> |
132 | | -Branch: master [de87a084c] 2019-06-13 17:28:24 -0400 |
133 | | -Branch: REL_11_STABLE [85600b7b5] 2019-06-13 17:28:24 -0400 |
134 | | -Branch: REL_10_STABLE [14a91a8fc] 2019-06-13 17:28:24 -0400 |
135 | | -Branch: REL9_6_STABLE [cb2398d80] 2019-06-13 17:28:24 -0400 |
136 | | ---> |
137 | | - <para> |
138 | | - Avoid spurious deadlock failures when upgrading a tuple lock (Oleksii |
139 | | - Kliukin) |
140 | | - </para> |
141 | | - </listitem> |
142 | | - |
143 | | - <listitem> |
144 | | -<!-- |
145 | 168 | Author: Tom Lane <tgl@sss.pgh.pa.us> |
146 | 169 | Branch: master [24c19e9f6] 2019-05-09 16:53:05 -0400 |
147 | 170 | Branch: REL_11_STABLE [e7eed0baa] 2019-05-09 16:52:49 -0400 |
|