Skip site navigation (1) Skip section navigation (2)

Re: Protection from SQL injection

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com>
Cc: "Thomas Kellerer" <spam_eater(at)gmx(dot)net>, pgsql-sql(at)postgresql(dot)org
Subject: Re: Protection from SQL injection
Date: 2008-04-27 03:42:14
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-sql
"Scott Marlowe" <scott(dot)marlowe(at)gmail(dot)com> writes:
> Wouldn't it be much simpler to have a version of the libpq client lib
> that only understands prepared queries?

You could do that, but there's still no way for it to know exactly how
the submitted query was constructed.  This would block off the types of
injections that want to add whole SQL commands, but not ones that just
subvert the current query (eg adding OR TRUE to see data you shouldn't).

This is really a client problem and only client-side solutions will
provide meaningful traction for it.  In perl, for instance, the "taint"
mechanism is a good way to notice whether any insecure strings are
getting into database queries.

			regards, tom lane

In response to


pgsql-sql by date

Next:From: Scott MarloweDate: 2008-04-27 03:50:10
Subject: Re: Protection from SQL injection
Previous:From: Scott MarloweDate: 2008-04-27 00:21:48
Subject: Re: Protection from SQL injection

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group