Re: Question concerning backport of CVE-2022-2625

2022-11-23 Thread Roberto C . Sánchez
Hi Tom, On Sun, Nov 20, 2022 at 11:43:41AM -0500, Tom Lane wrote: > > It'd likely be a good idea to reproduce this with a gdb breakpoint > set at errfinish, and see exactly what's leading up to the error. > So, I did as you suggested. The top few frames of the backtrace were: #0 errfinish

Re: Question concerning backport of CVE-2022-2625

2022-11-20 Thread Roberto C . Sánchez
Hi Tom, On Sun, Nov 20, 2022 at 11:43:41AM -0500, Tom Lane wrote: > Roberto =?iso-8859-1?Q?C=2E_S=E1nchez?= writes: > > -- this makes a shell "point <<@@ polygon" operator too > > CREATE OPERATOR @@>> ( PROCEDURE = poly_contain_pt, > >LEFTARG = polygon, RIGHTARG = point, > >COMMUTATOR

Re: Question concerning backport of CVE-2022-2625

2022-11-20 Thread Tom Lane
Roberto =?iso-8859-1?Q?C=2E_S=E1nchez?= writes: > -- this makes a shell "point <<@@ polygon" operator too > CREATE OPERATOR @@>> ( PROCEDURE = poly_contain_pt, >LEFTARG = polygon, RIGHTARG = point, >COMMUTATOR = <<@@ ); > CREATE EXTENSION test_ext_cor; -- fail > ERROR: operator

Question concerning backport of CVE-2022-2625

2022-11-20 Thread Roberto C . Sánchez
Greetings PGSQL hackers, I am working on a backport of CVE-2022-2625 to PostgreSQL 9.6 and 9.4. I am starting from commit 5919bb5a5989cda232ac3d1f8b9d90f337be2077. The backport to 9.6 was relatively straightforward, the principal change being to omit some of the hunks related to commands in 9.6