Ethical Hacking Learn to find vulnerabilities before the bad guys do! Gain real world hands on hacking experience in our state of the art hacking lab. Course designed and taught by expert instructors with years of penetration testing experience. 12 student maximum in every class. Certification attempt included in every package. | Computer Forensics Training at InfoSec Institute Gain the in-demand skills of a certified computer examiner, learn to recover trace data left behind by fraud, theft, and cybercrime perpetrators. Discover the source of computer crime and abuse at your organization so that it never happens again. All of our class sizes are guaranteed to be 12 students or less to facilitate one-on-one interaction with one of our expert instructors. |

| Subject: | RE: Blind SQL Injection / Stored procedures |
|---|---|
| Date: | Fri, 18 Nov 2005 11:55:00 +0100 |
Hi phillip, The first thing I can tell on PHP since I don't much about it, is the use of the magic quotes option. You should find valuable information on this topic on google. However you have to know that there are some problems with it. Read it carefully. Now the problem with PHP is that under the version 5 (not sure at 100%) there is nothing that prevents SQL injection since the SQL is inline in the code. Even with magic quotes it's dangerous since you can achieve SQL injection without a single quote (when there is an integer argument for instance). There is another option that I found was a database abstraction layer package made by PEAR, it works on PHP 4 and 5 and should be free (pear.php.net/package/DB). Now I don't know if it's a good product or not, or really secure but you can always try. I just know they use their own prepared statement and quote stripping. Good luck! François Larouche P.S. It's not a good idea to talk openly of your architecture on the net, not all people in this list are pure of heart :) Nasa is a attractive place... ______________________________________________________________________________________________________________________________ This email, the information contained within and any files transmitted with it (herein after referred as "the message") are confidential. It is intended solely for the addressees and access to this message by any other person is not permitted. If you are not the named addressee, please send it back immediately to the sender and delete it. Unauthorized disclosure, publication, use, dissemination, forwarding, printing or copying of this message, either in whole or in part, is strictly prohibited. Emails are susceptible to alteration and their integrity cannot be guaranteed. Our company shall not be liable for this message if modified or falsified.
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: Software liability, Jonathan Angliss |
|---|---|
| Next by Date: | Re: Blind SQL Injection / Stored procedures, ascii |
| Previous by Thread: | Re: [WEB SECURITY] RE: Blind SQL Injection / Stored procedures, Frederic Charpentier |
| Next by Thread: | Re: Blind SQL Injection / Stored procedures, ascii |
| Indexes: | [Date] [Thread] [Top] [All Lists] |