Click here to Skip to main content
15,885,244 members
Please Sign up or sign in to vote.
5.00/5 (1 vote)
See more: , +
Blind SQL Injection
Severity: High
URL: https://10.161.9.120:8085/ind/online_regn_vgi.aspx
Entity: txtAdd2 (Parameter)
Risk: It is possible to view, modify or delete database entries and tables
Causes: Sanitation of hazardous characters was not performed correctly on user input
Fix: Review possible solutions for hazardous character injection
Difference: Parameter manipulated from: 1234 to: 1234%2F**%2Fand%2F**%2F7659%3D7659
Parameter manipulated from: 1234/**/and/**/0=7659 to: 1234%2F**%2Fand%2F**%2F0%3D7659
Parameter manipulated from: 1234/**/or/**/7659=7659 to: 1234%2F**%2For%2F**%2F7659%3D7659
Parameter manipulated from: 1234/**/and/**/0=0 to: 1234%2F**%2Fand%2F**%2F0%3D0
Reasoning: The test result seems to indicate a vulnerability because it shows that values can be appended to parameter values,
indicating that they were embedded in an SQL query. In this test, three (or sometimes four) requests are sent. The last is
11/13/2014 7
TOC
TOC
logically equal to the original, and the nexttolast
is different. Any others are for control purposes. A comparison of the last
two responses with the first (the last is similar to it, and the nexttolast
is different) indicates that the application is
vulnerable.
Posted
Comments
Have you parametrized the value of TextBox txtAdd2?
RajkumarGnanaraj 17-Mar-15 10:02am    
ya i parameterized that text box and also validated with regex..
ZurdoDev 17-Mar-15 7:58am    
What exactly is your question? We can't see any of your code so we have no idea what is going on.

1 solution

You have already posted the cause and the fix for the reported issue.

[quote]
Causes: Sanitation of hazardous characters was not performed correctly on user input
Fix: Review possible solutions for hazardous character injection
[/quote]

The issue here is about the lack of validation on your applications user input controls, in this specific instance, a control with an ID of txtAdd2.

For example, if this controls purpose is to accept an number, that is then passed to your store procedure, then you should validate the user has entered a number - before attempting to pass it's value to your procedure.

There are a few articles here that explain the different types of asp.net validation controls available, and examples of their usage ... This is a good example article.

... hope it helps.
 
Share this answer
 
Comments
RajkumarGnanaraj 17-Mar-15 10:09am    
I validated that text box with regex at server side and also parameterized..
hypermellow 17-Mar-15 10:31am    
What happens when you input the hazardous input text as described in the test. Does your validation catch this before you pass them as input to your procedure?

The test results indicate that the hazardous values are passed.

[quote]
Reasoning: The test result seems to indicate a vulnerability because it shows that values can be appended to parameter values, indicating that they were embedded in an SQL query
[/quote]

If you can demonstrate your validation routine stops these values being submitted to your procedure, then you can contest the result of this test.
... it would then be up to the tester to prove the potential vulnerability?

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



CodeProject, 20 Bay Street, 11th Floor Toronto, Ontario, Canada M5J 2N8 +1 (416) 849-8900