Home page logo

fulldisclosure logo Full Disclosure mailing list archives

Re: Antitoxin for "SQL Injection" (?)
From: Marco Ermini <markoer () markoer org>
Date: Tue, 3 Jan 2006 18:38:50 +0100

On 1/3/06, Jan Muenther <jan.muenther () nruns com> wrote:
As a general rule - if you find yourself concatenating strings
containing user input to create your SQL query, you're doing something
substantially wrong.
I'd still advise you to filter input generically using a whitelist
(blacklisting is fairly dangerous with databases, see e.g. the
CHAR(0xXX) thingy), and also to use stored procedures, simply since it's
best practice and may help to prevent clusterf**cks deriving from
combinations of smaller issues.

Hope that helps,
Cheers, j.

Agreed, I would also like to suggest to use database views whenever
possible. Creating read only views (these are generally read only
already) for each tabular data which has to be displayed on a web site
is generally a good practice - depending on the environment you are
on, it is also generally faster because it accomodates better when
used in combination with EJBs or other sort of
caching/Model-View-Controller mechanisms.

Marco Ermini
Dubium sapientiae initium. (Descartes)
root () human # mount -t life -o ro /dev/dna /genetic/research
(This message is for the designated recipient only and may contain
privileged or confidential information. If you have received it in
error, please notify the sender immediately and delete the original.)
Full-Disclosure - We believe in it.
Charter: http://lists.grok.org.uk/full-disclosure-charter.html
Hosted and sponsored by Secunia - http://secunia.com/

  By Date           By Thread  

Current thread:
[ Nmap | Sec Tools | Mailing Lists | Site News | About/Contact | Advertising | Privacy ]