Re: SQL Injection prevention
From: Jeff Cochran (jeff.nospam_at_zina.com)
Date: 06/22/04
- Next message: Jon Jones: "Granting Permissions on Multiple Tables"
- Previous message: Stephen Armbrust MCSD: "Re: application rolls and ADO.Net"
- In reply to: Dan Avni: "Re: SQL Injection prevention"
- Next in thread: Dan Avni: "Re: SQL Injection prevention"
- Reply: Dan Avni: "Re: SQL Injection prevention"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Tue, 22 Jun 2004 18:57:17 GMT
On Mon, 21 Jun 2004 10:19:40 -0700, Dan Avni <danavni@officecore.com>
wrote:
>Jeff Hi,
>
>thanks for the quick response. in reality i am more of a development
>company than a hosting company. this client is a long time client of
>ours so we wanted to do him a favor and help him a bit in hosting his
>site on our servers. of course i will not do that is his site poses any
>danger to my sites/DB's on the server.
>
>the only things the developers did for my client is make sure that the
>single qoute (') symbol is replaced into a double qoute '' in order to
>prevent sql injection. i as a developer know this is not the only way to
>do sql injection and therefor concerned about the site going live on my
>server.
>
>however, my question still remains. if i set up a SQL server user who
>has access only to a specific DB. will hackers be able to use SQL
>injection to do harm to any other DB on the server or to the server
>itself?
Maybe, but not guaranteed. For example, if XP_CMDSHELL can be run,
the entire box is at risk even if the user has access only to a single
database. The analogy is having a kitchen door with an insecure lock.
Instead of fixing the lock, you put good locks on the door to the
dining room from the kitchen and the door to the hall. That way, even
if a thief gets in, he's limited to the kitchen and can only steal
your beer.
But if the kitchen has a stove, he can also use it to set the house on
fire. :)
SQL injection is always tough to deal with. You can mitigate many
pieces, reducing your exposure to damage, but unless the app is
designed from the ground up to prevent injection there may always be
some hole an attack can slip through.
Jeff
- Next message: Jon Jones: "Granting Permissions on Multiple Tables"
- Previous message: Stephen Armbrust MCSD: "Re: application rolls and ADO.Net"
- In reply to: Dan Avni: "Re: SQL Injection prevention"
- Next in thread: Dan Avni: "Re: SQL Injection prevention"
- Reply: Dan Avni: "Re: SQL Injection prevention"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|