Need to rectify Sql Injection issue in whole application

Question

0.00/5 (No votes)

See more:

Hi,

I have an application which is prone to sql injection.while forming the queries, its taking inputs directly from the controls or query string etc

Now I have to remove the risk of sql injection from the whole application. I know there are two ways to do that:

1. make the query parameterized
2. or make the stored procedures

But the problem is that, there are around 12000 instances where I have to make the changes, if I follow any of the above two methods.

My question here is:

Is there any other way to do this when the instance count is too big?

Posted 7-Feb-13 18:12pm

RajpootRohan

Add a Solution

Comments

RDBurmon 8-Feb-13 0:16am

There is no such functionality available.
you have to make it manually

RajpootRohan 8-Feb-13 0:25am

Rahul,

I mean to say there is any other way so that I can reduce the effort. I mean at the database side or somewhere else

2 solutions

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Tadit Dash (ତଡିତ୍ କୁମାର ଦାଶ) · Answer 1 · 2013-02-07T20:41:00

You can "Filter Input And Escape Output".

That means you need to be 100% sure of what you are saving to your database by proper validations and restrictions while storing the data.

Refer -
1. Hack-Proofing Your ASP.NET Applications[^].
2. Securing Your ASP.NET Applications[^].

But, still I suggest you to go for parameterized query and Stored Procedures.
It will take time to build, but will secure your application for sure.

Thanks...

Bernhard Hiller · Answer 2 · 2013-02-07T21:45:00

Solution 2

You are right that it is a terrible amount of stupid work to do. I know that myself: I changed all our code from simple string concatenation to parameterized queries...

Posted 7-Feb-13 21:45pm

Bernhard Hiller