<a href="http://g.adspeed.net/ad.php?do=clk&zid=15220&wd=468&ht=60&pair=as" target="_blank"><img style="border:0px;" src="http://g.adspeed.net/ad.php?do=img&zid=15220&wd=468&ht=60&pair=as" alt="i" width="468" height="60"/></a>
Log in
::
Register
::
Not logged in
Home
Tags
Articles
Editorials
Stairways
Forums
Scripts
Videos
Blogs
QotD
Books
Ask SSC
SQL Jobs
Training
Authors
About us
Contact us
Newsletters
Write for us
<a href="http://g.adspeed.net/ad.php?do=clk&zid=15491&wd=120&ht=300&pair=as" target="_top"><img style="border:0px;" src="http://g.adspeed.net/ad.php?do=img&zid=15491&wd=120&ht=300&pair=as" alt="i" width="120" height="300"/></a>
Recent Posts
Recent Posts
Popular Topics
Popular Topics
Home
Search
Members
Calendar
Who's On
Home
»
Article Discussions
»
Article Discussions by Author
»
Discuss Content Posted by Brian Kelley
»
Stored Procedures and SQL Injection
19 posts, Page 1 of 2
1
2
»»
Stored Procedures and SQL Injection
Rate Topic
Display Mode
Topic Options
Author
Message
K. Brian Kelley
K. Brian Kelley
Posted Sunday, February 17, 2013 10:55 PM
Keeper of the Duck
Group: Moderators
Last Login: 2 days ago @ 1:55 PM
Points: 6,584,
Visits: 1,789
Comments posted to this topic are about the item
Stored Procedures and SQL Injection
K. Brian Kelley, CISA, MCSE, Security+, MVP - SQL Server
Regular Columnist (Security), SQLServerCentral.com
Author of
Introduction to SQL Server: Basic Skills for Any SQL Server User
|
Professional Development blog
|
Technical Blog
|
LinkedIn
|
Twitter
Post #1421035
David.Poole
David.Poole
Posted Monday, February 18, 2013 1:15 AM
SSCrazy
Group: General Forum Members
Last Login: Tuesday, May 21, 2013 9:35 AM
Points: 2,749,
Visits: 1,407
Not only are SQL Injection attacks still going on but also cross site scripting, response splitting and other nasties.
Let us suppose that your code is SQL Injection attack proof. Some enters Dave';WAITFOR('00:00:15'); into a form field and that is precisely what gets entered into the DB. The WAITFOR doesn't get treated as a SQL Statement but now you have a data quality problem.
OK, coding to look for strange syntax is quite a job but I've seen fields that, in theory, are populated from web form drop down boxes that have had this rubbish in them!!!
Cross site scripting is when enter JavaScript tags into a DB field and when the contents of these fields is rendered on the web page the JavaScript fires.
Then you have HTTP Response Splitting where some bright spark has worked out that injecting carriage returns and line feeds into the HTTP response fools the web server into to accepting more than it should from any single request.
At one time is was easy to spot illegitimate mechanical activity on a web stie by the HTTP_USER_AGENT. Now even the most basic mechanical attack will know to spoof a valid HTTP_USER_AGENT and probably rotate IP addresses to avoid rate alerts (too much traffic coming from one customer for it to be genuine).
From the malicious attack perspective the game has moved on.
SQL Injection attacks are the middle aged man with the high BMI in the Sunday pub football league compared to what else is out there in the European super league.
If SQL Injection attacks are still suceeding on your web site then you're way behind the curve.
LinkedIn Profile
Post #1421062
Question Guy
Question Guy
Posted Monday, February 18, 2013 7:06 AM
Valued Member
Group: General Forum Members
Last Login: Yesterday @ 3:03 PM
Points: 65,
Visits: 586
Once upon a time, we had some old code that did not account for SQL Injection attacks. And then it happend.
People could not understand why the titles on our external web pages were changing or being deleted.
These pages were database driven through the use of an administative front-end for the users.
I put a few insert and update triggers on a few tables, and what do you know, a couple days later we find out someone is passing SQL statements into a field that for some reason was aimed at changing the titles on our web pages.
These pages were changed to use stored procedures.
Now, if only everyone was on board for doing this on our Intranet as well....
Post #1421203
K. Brian Kelley
K. Brian Kelley
Posted Monday, February 18, 2013 9:12 AM
Keeper of the Duck
Group: Moderators
Last Login: 2 days ago @ 1:55 PM
Points: 6,584,
Visits: 1,789
David, I would agree with you that SQL injection attacks should be old news. The problem is they aren't. For instance, the discovery of serious SQL injection vulnerabilities for Ruby on Rails was reported last month (Jan 2013). Therefore, it behooves us to continue to remind folks of what can be done and why they should care.
K. Brian Kelley, CISA, MCSE, Security+, MVP - SQL Server
Regular Columnist (Security), SQLServerCentral.com
Author of
Introduction to SQL Server: Basic Skills for Any SQL Server User
|
Professional Development blog
|
Technical Blog
|
LinkedIn
|
Twitter
Post #1421258
JustMarie
JustMarie
Posted Monday, February 18, 2013 9:29 AM
SSC Journeyman
Group: General Forum Members
Last Login: Friday, April 26, 2013 10:09 AM
Points: 89,
Visits: 384
Just a thought but what about aliasing the columns returned by the stored procedure to give another level of protection? The real column names are hidden and the naming convention can't be extrapolated.
Post #1421271
mtassin
mtassin
Posted Monday, February 18, 2013 9:30 AM
Hall of Fame
Group: General Forum Members
Last Login: Today @ 12:39 AM
Points: 3,229,
Visits: 64,293
And the other thing to keep in mind is that if we don't occasionally mention SQL injection attacks and how to prevent them, we run the risk of developers in the future repeating the mistakes of the past.
--Mark Tassin
MCITP - SQL Server DBA
Proud member of the Anti-RBAR alliance.
For help with Performance click this link
For tips on how to post your problems
Post #1421272
David.Poole
David.Poole
Posted Monday, February 18, 2013 9:36 AM
SSCrazy
Group: General Forum Members
Last Login: Tuesday, May 21, 2013 9:35 AM
Points: 2,749,
Visits: 1,407
K. Brian Kelley (2/18/2013)
David, I would agree with you that SQL injection attacks should be old news. The problem is they aren't.
Boy do I know it! What is telling is that the majority of the SQL Dialect is for SQL Server and MySQL.
LinkedIn Profile
Post #1421278
K. Brian Kelley
K. Brian Kelley
Posted Monday, February 18, 2013 9:38 AM
Keeper of the Duck
Group: Moderators
Last Login: 2 days ago @ 1:55 PM
Points: 6,584,
Visits: 1,789
Marie, you could certainly do that, but if the app uses the stored procedure, then the attacker can use it to do what the stored procedure is capable of. The attacker still can't get to the table in question, so whether or not the parameters equal the columns, there's not really a risk. There is probably greater risk of developers and DBAs getting things confused because the names are different.
K. Brian Kelley, CISA, MCSE, Security+, MVP - SQL Server
Regular Columnist (Security), SQLServerCentral.com
Author of
Introduction to SQL Server: Basic Skills for Any SQL Server User
|
Professional Development blog
|
Technical Blog
|
LinkedIn
|
Twitter
Post #1421280
HildaJ
HildaJ
Posted Monday, February 18, 2013 10:03 AM
SSC Journeyman
Group: General Forum Members
Last Login: Yesterday @ 12:11 PM
Points: 96,
Visits: 268
SQL Injection attacks are very present and as the article mentions they are still around because developers either by lack of knowledge or experience are still programming to allow these loops. What drives me crazy is that some companies don't believe it's worth the effort the extra time and training required to prevent these type of attacks. I used to be a developer and in my case was lack of knowledge and experience in addtion to lack of training and our company suffered a sql attack. I was very upset and emberrased that this happened to us. Great article.
Post #1421286
Jonathan AC Roberts
Jonathan AC Roberts
Posted Monday, February 18, 2013 11:23 AM
Old Hand
Group: General Forum Members
Last Login: 2 days ago @ 9:15 AM
Points: 316,
Visits: 1,185
This made me laugh
Post #1421310
« Prev Topic
|
Next Topic »
19 posts, Page 1 of 2
1
2
»»
Permissions
You
cannot
post new topics.
You
cannot
post topic replies.
You
cannot
post new polls.
You
cannot
post replies to polls.
You
cannot
edit your own topics.
You
cannot
delete your own topics.
You
cannot
edit other topics.
You
cannot
delete other topics.
You
cannot
edit your own posts.
You
cannot
edit other posts.
You
cannot
delete your own posts.
You
cannot
delete other posts.
You
cannot
post events.
You
cannot
edit your own events.
You
cannot
edit other events.
You
cannot
delete your own events.
You
cannot
delete other events.
You
cannot
send private messages.
You
cannot
send emails.
You
may
read topics.
You
cannot
rate topics.
You
cannot
vote within polls.
You
cannot
upload attachments.
You
may
download attachments.
You
cannot
post HTML code.
You
cannot
edit HTML code.
You
cannot
post IFCode.
You
cannot
post JavaScript.
You
cannot
post EmotIcons.
You
cannot
post or upload images.
Copyright © 2002-2013 Simple Talk Publishing. All Rights Reserved.
Privacy Policy.
Terms of Use.
Report Abuse.
