Back to bug 2207569
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| TEJ RATHI | 2023-05-16 10:13:38 UTC | CC | adudiak, caswilli, databases-maint, dffrench, fjansen, fjanus, gzaronik, hbraun, hhorak, hkataria, jburrell, jkoehler, jorton, kaycoth, kshier, ngough, nweather, pkubat, praiskup, psegedy, rgodfrey, stcannon, tsasak, yguenane | |
| TEJ RATHI | 2023-05-16 10:14:41 UTC | Blocks | 2203202 | |
| TEJ RATHI | 2023-05-16 10:17:42 UTC | Depends On | 2207587, 2207590, 2207582, 2207580, 2207584, 2207586, 2207588, 2207589 | |
| TEJ RATHI | 2023-05-16 10:19:12 UTC | Comment | 0 | updated |
| TEJ RATHI | 2023-05-16 10:31:33 UTC | CC | aazores, adupliak, aileenc, alampare, alazarot, anstephe, asoldano, ataylor, avibelli, bbaranow, bbuckingham, bcourt, bgeorges, bmaxwell, boliveir, brian.stansberry, cdewolf, chazlett, clement.escoffier, dandread, darran.lofthouse, dciabrin, dhanak, dkreling, dosoudil, drichtar, eaguilar, ebaron, eglynn, ehelms, emingora, eric.wittmann, fjuma, fmongiar, gjospin, gmalinko, gparvin, gsmet, hamadhan, ibek, ivassile, iweiss, janstey, jjoyce, jkang, jmartisk, jnethert, jpallich, jpavlik, jpechane, jpoth, jrokos, jross, jsherril, kverlaen, lbacciot, lgao, lhh, ljavorsk, lpeer, lpetrovi, lthon, lzap, max.andersen, mbayer, mburns, mgarciac, mhulan, michal.skrivanek, mkolesni, mmuzila, mnovotny, mosmerov, mperina, mschorm, msochure, msvehla, myarboro, nboldt, njean, nmoumoul, nwallace, orabin, owatkins, pahickey, pantinor, pcreech, pdelbell, pdrozd, peholase, pgallagh, pjindal, pmackay, probinso, pskopek, rchan, rguimara, rkieley, rowaters, rrajasek, rruss, rstancel, rsvoboda, rsynek, saroy, sbiarozk, sbonazzo, scohen, scorneli, sdouglas, sfroberg, smaestri, spower, sthorger, tcunning, teagle, tom.jenkinson, yfang, zmiklank | |
| TEJ RATHI | 2023-05-16 10:33:32 UTC | CC | dciabrin, eglynn, jjoyce, lhh, ljavorsk, lpeer, mbayer, mburns, mgarciac, michal.skrivanek, mkolesni, mmuzila, mperina, mschorm, sbonazzo, scohen, spower, zmiklank | |
| TEJ RATHI | 2023-05-17 11:32:46 UTC | CC | jkoehler | |
| Depends On | 2207933, 2207934, 2207932, 2207938, 2207935, 2207937, 2207936, 2207931 | |||
| RHEL Program Management Team | 2023-05-18 14:38:51 UTC | Depends On | 2208306 | |
| Sagar Navale | 2023-05-25 07:21:13 UTC | CC | snavale | |
| Red Hat Bugzilla | 2023-05-31 22:25:03 UTC | CC | rsynek | |
| RHEL Program Management Team | 2023-06-06 12:48:35 UTC | Depends On | 2212815 | |
| Chess Hazlett | 2023-06-06 21:05:54 UTC | Fixed In Version | PostgreSQL 15.3, PostgreSQL 14.8, PostgreSQL 13.11, PostgreSQL 12.15, PostgreSQL 11.20 | |
| Doc Text | PostgreSQL could permit incorrect policies to be applied in certain cases where role-specific policies are used and a given query is planned under one role and then executed under other roles. This scenario can happen under security definer functions or when a common user and query is planned initially and then re-used across multiple SET ROLEs. Applying an incorrect policy may permit a user to complete otherwise-forbidden reads and modifications. This affects only databases that have used CREATE POLICY to define a row security policy. | |||
| Paige Jung | 2023-06-07 16:42:53 UTC | Doc Text | PostgreSQL could permit incorrect policies to be applied in certain cases where role-specific policies are used and a given query is planned under one role and then executed under other roles. This scenario can happen under security definer functions or when a common user and query is planned initially and then re-used across multiple SET ROLEs. Applying an incorrect policy may permit a user to complete otherwise-forbidden reads and modifications. This affects only databases that have used CREATE POLICY to define a row security policy. | A flaw was found in PostgreSQL, which could permit incorrect policies being applied in certain cases where role-specific policies are used and a given query is planned under one role and executed under other roles. This scenario can happen under security definer functions, or when a common user and query is planned initially and then re-used across multiple SET ROLEs. Applying an incorrect policy may permit a user to complete otherwise forbidden reads and modifications. This only affects databases that have used CREATE POLICY to define a row security policy. |
| Dominik Rehák | 2023-06-09 17:08:38 UTC | CC | drehak | |
| RHEL Program Management Team | 2023-06-13 13:25:46 UTC | Depends On | 2214583 | |
| RHEL Program Management Team | 2023-06-14 01:41:29 UTC | Depends On | 2214875 | |
| errata-xmlrpc | 2023-06-21 14:38:59 UTC | Link ID | Red Hat Product Errata RHSA-2023:3714 | |
| Red Hat Bugzilla | 2023-07-07 08:35:16 UTC | Assignee | security-response-team | nobody |
| RHEL Program Management Team | 2023-07-20 11:13:15 UTC | Depends On | 2224309 | |
| Red Hat Bugzilla | 2023-07-21 22:26:26 UTC | CC | jpavlik | |
| errata-xmlrpc | 2023-07-27 13:32:50 UTC | Link ID | Red Hat Product Errata RHSA-2023:4313 | |
| errata-xmlrpc | 2023-07-31 09:19:41 UTC | Link ID | Red Hat Product Errata RHSA-2023:4327 | |
| RHEL Program Management Team | 2023-08-03 07:59:50 UTC | Depends On | 2228767 | |
| errata-xmlrpc | 2023-08-08 08:37:53 UTC | Link ID | Red Hat Product Errata RHSA-2023:4527 | |
| errata-xmlrpc | 2023-08-08 08:38:01 UTC | Link ID | Red Hat Product Errata RHSA-2023:4535 | |
| errata-xmlrpc | 2023-08-08 08:38:21 UTC | Link ID | Red Hat Product Errata RHSA-2023:4539 |
Back to bug 2207569