full-disclosure - Question: is this exploitable?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <1066531479.6483.27.camel@tantor.nuclearelephant.com>
From: jonathan at nuclearelephant.com (Jonathan A. Zdziarski)
Subject: Question: is this exploitable?

Escaping quote characters might work OK in MySQL, but it is at best only
a database-dependent solution.  Take a look at Oracle, instead of
double-quotes, single-quotes are used.  And instead of being escaped,
they are simply doubled (e.g. ' becomes '').  You'd have to write an
entirely different mechanism to untaint data bound for Oracle...and
another one for other different database implementations.

This is why placeholders are a better solution.  For one, they keep you
in a database-independent environment (which makes sense, since you're
using DBI).  For another, they insure you don't have to worry about
accidentally missing the escaping of some data.

On Sat, 2003-10-18 at 22:36, Paul Tinsley wrote:
> I don't believe this is a true statement.