Re: Preventing SQL Injection in PL/pgSQL in psql

Поиск
Список
Период
Сортировка
От Merlin Moncure
Тема Re: Preventing SQL Injection in PL/pgSQL in psql
Дата
Msg-id b42b73150605091727x4869e591y6de602e5c244cb78@mail.gmail.com
обсуждение исходный текст
Ответ на Preventing SQL Injection in PL/pgSQL in psql  ("Karen Hill" <karen_hill22@yahoo.com>)
Ответы Re: Preventing SQL Injection in PL/pgSQL in psql  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-general
On 9 May 2006 17:04:31 -0700, Karen Hill <karen_hill22@yahoo.com> wrote:
> Is my understanding correct that the following is vulnerable to SQL
> injection in psql:
>
> CREATE OR REPLACE FUNCTION fx ( my_var bchar)
> RETURNS void AS
> $$
> BEGIN
> INSERT INTO fx VALUES ( my_var ) ;
> END;
> $$
> LANGUAGE 'plpgsql' VOLATILE

no, IMO this is the safest and best option.  Quoting, etc is handled
by the plpgsql processor (this is one of the things that make it so
great).

> Where this is NOT subject to SQL injection:
>
> CREATE OR REPLACE FUNCTION fx ( my_var bpchar)
> RETURNS void AS
> $$
> BEGIN
> EXECUTE ' INSERT INTO fx VALUES ( ' || quote_literal( my_var) || ' ); '
> END;
> $$ LANGUAGE 'plpgsql' VOLATILE

If you are making dynamic sql statements this (quote_literal) is the
preferred way to do quotations...otherwise there is potential for
malformed statement.  My rule of thumb is to use static sql when you
can, dynamic when you have to.

Merlin

В списке pgsql-general по дате отправления:

Предыдущее
От: "Karen Hill"
Дата:
Сообщение: Preventing SQL Injection in PL/pgSQL in psql
Следующее
От: Bruce Momjian
Дата:
Сообщение: Re: [PERFORM] Arguments Pro/Contra Software Raid