From: | tgl(at)svr1(dot)postgresql(dot)org (Tom Lane) |
---|---|
To: | pgsql-committers(at)postgresql(dot)org |
Subject: | pgsql: array_in() and array_recv() need to be more paranoid about |
Date: | 2005-08-15 19:41:07 |
Message-ID: | 20050815194107.87EE652F25@svr1.postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers |
Log Message:
-----------
array_in() and array_recv() need to be more paranoid about validating
their OID parameter. It was possible to crash the backend with
select array_in('{123}',0,0); because that would bypass the needed step
of initializing the workspace. These seem to be the only two places
with a problem, though (record_in and record_recv don't have the issue,
and the other array functions aren't depending on user-supplied input).
Back-patch as far as 7.4; 7.3 does not have the bug.
Tags:
----
REL7_4_STABLE
Modified Files:
--------------
pgsql/src/backend/utils/adt:
arrayfuncs.c (r1.100.2.3 -> r1.100.2.4)
(http://developer.postgresql.org/cvsweb.cgi/pgsql/src/backend/utils/adt/arrayfuncs.c.diff?r1=1.100.2.3&r2=1.100.2.4)
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2005-08-15 21:02:26 | pgsql: Make createlang and droplang proof against weird search_path |
Previous Message | Tom Lane | 2005-08-15 19:40:43 | pgsql: array_in() and array_recv() need to be more paranoid about |