pgsql: Further fixes to the pg_get_expr() security fix in back branches

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Further fixes to the pg_get_expr() security fix in back branches
Date: 2010-09-25 21:17:33
Message-ID: E1Ozc7h-0003NO-0J@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Further fixes to the pg_get_expr() security fix in back branches.

It now emerges that the JDBC driver expects to be able to use pg_get_expr()
on an output of a sub-SELECT. So extend the check logic to be able to recurse
into a sub-SELECT to see if the argument is ultimately coming from an
appropriate column. Per report from Thomas Kellerer.

Branch
------
REL9_0_STABLE

Details
-------
http://git.postgresql.org/gitweb?p=postgresql.git;a=commitdiff;h=3613d0893f526619471026b6b04bda70e31fe9e2

Modified Files
--------------
src/backend/parser/parse_func.c | 84 +++++++++++++++++++++++++++------------
1 files changed, 58 insertions(+), 26 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Tom Lane 2010-09-25 23:04:28 pgsql: Fix another join removal bug: the check on PlaceHolderVars was w
Previous Message Peter Eisentraut 2010-09-25 13:55:52 pgsql: Fix man page markup for <cmdsynopsis> with multiple variants