Because the DBI methods have no way of knowing the diffrence between what you should and shouldn't do (much like open), there is no way for it to dissallow multiple statements in one prepare. On that note, if
$baz = "'a'; DROP TABLE blah" is acceptable SQL to the server, it is allowed by prepare.
And, here is a bit of a fix, look at the following :
## Badd
my $sth = $dbh->prepare('SELECT * FROM foo WHERE bar = ?');
$sth->execute($baz)
## Good
my $sth = $dbh->prepare("SELECT * FROM foo WHERE bar = '?'");
$sth->execute($baz)
The extra quotes would prevent the baz from getting out unless something was passed which was like
$baz = "foo'; DROP TABLE blah; SELECT * FROM foo WHERE a = 'B"
In short, there is not definite fix, which goes back to using regexes to validate user entries before touching them to your database/system.
OH, a sarcasm detector, that’s
really useful
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.