connect.sungard.com, XSS, Cross Site Scripting, CWE-79, CAPEC-86

XSS in connect.sungardhe.com | Vulnerability Crawler Report

Report generated by XSS.CX at Sun Jan 02 08:58:30 CST 2011.

Contents

Loading

1. Cross-site scripting (reflected)

2. SSL cookie without secure flag set

3. Cookie without HttpOnly flag set

4. HTML does not specify charset


1. Cross-site scripting (reflected)  next

Summary

Severity:   High
Confidence:   Certain
Host:   https://connect.sungardhe.com
Path:   /customer_support/start.swe

Issue detail

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

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.

Issue remediation

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.

Request

GET /customer_support/start.swe?3d156"><img%20src%3da%20onerror%3dalert(1)>6c8308f0bc9=1 HTTP/1.1
Host: connect.sungardhe.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
Connection: close
Date: Sun, 02 Jan 2011 14:39:16 GMT
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
content-language: en
cache-control: no-cache
pragma: no-cache
content-type: text/html;charset=UTF-8
content-length: 540
set-cookie: _sn=Y8o9naQNYUqfBJfBr3FspfYnlv.96bNAJF9UtoHvTLI_; Version=1; Path=/customer_support

<html><body><form action="/customer_support/start.swe" method="GET" name="RedirectForHost"><input type = "hidden" name="_sn" value="Y8o9naQNYUqfBJfBr3FspfYnlv.96bNAJF9UtoHvTLI_">
<input type = "hidde
...[SNIP]...
<input type = "hidden" name="3d156"><img src=a onerror=alert(1)>6c8308f0bc9" value="1">
...[SNIP]...
2. SSL cookie without secure flag set  previous  next

Summary

Severity:   Information
Confidence:   Certain
Host:   https://connect.sungardhe.com
Path:   /customer_support/start.swe

Issue detail

The following cookie was issued by the application and does not have the secure flag set:The cookie does not appear to contain a session token, which may reduce the risk associated with this issue. You should review the contents of the cookie to determine its function.

Issue background

If the secure flag is set on a cookie, then browsers will not submit the cookie in any requests that use an unencrypted HTTP connection, thereby preventing the cookie from being trivially intercepted by an attacker monitoring network traffic. If the secure flag is not set, then the cookie will be transmitted in clear-text if the user visits any HTTP URLs within the cookie's scope. An attacker may be able to induce this event by feeding a user suitable links, either directly or via another web site. Even if the domain which issued the cookie does not host any content that is accessed over HTTP, an attacker may be able to use links of the form http://example.com:443/ to perform the same attack.

Issue remediation

The secure flag should be set on all cookies that are used for transmitting sensitive data when accessing content over HTTPS. If cookies are used to transmit session tokens, then areas of the application that are accessed over HTTPS should employ their own session handling mechanism, and the session tokens used should never be transmitted over unencrypted communications.

Request

GET /customer_support/start.swe HTTP/1.1
Host: connect.sungardhe.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
Connection: close
Date: Sun, 02 Jan 2011 14:38:10 GMT
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
cache-control: no-cache, must-revalidate
pragma: no-cache
content-language: en
cache-control: no-cache
pragma: no-cache
content-type: text/html;charset=UTF-8
content-length: 581
set-cookie: _sn=81vr7fJb8id45S9Tn2s5x5wIFUdOH4BgUniKcMQuww4_; Version=1; Path=/customer_support

<html><body><form action="/customer_support/start.swe" method="GET" name="RedirectForHost"><input type = "hidden" name="SWECmd" value="GotoView">
<input type = "hidden" name="_sn" value="81vr7fJb8id4
...[SNIP]...
3. Cookie without HttpOnly flag set  previous  next

Summary

Severity:   Information
Confidence:   Certain
Host:   https://connect.sungardhe.com
Path:   /customer_support/start.swe

Issue detail

The following cookie was issued by the application and does not have the HttpOnly flag set:The cookie does not appear to contain a session token, which may reduce the risk associated with this issue. You should review the contents of the cookie to determine its function.

Issue background

If the HttpOnly attribute is set on a cookie, then the cookie's value cannot be read or set by client-side JavaScript. This measure can prevent certain client-side attacks, such as cross-site scripting, from trivially capturing the cookie's value via an injected script.

Issue remediation

There is usually no good reason not to set the HttpOnly flag on all cookies. Unless you specifically require legitimate client-side scripts within your application to read or set a cookie's value, you should set the HttpOnly flag by including this attribute within the relevant Set-cookie directive.

You should be aware that the restrictions imposed by the HttpOnly flag can potentially be circumvented in some circumstances, and that numerous other serious attacks can be delivered by client-side script injection, aside from simple cookie stealing.

Request

GET /customer_support/start.swe HTTP/1.1
Host: connect.sungardhe.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
Connection: close
Date: Sun, 02 Jan 2011 14:38:10 GMT
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
cache-control: no-cache, must-revalidate
pragma: no-cache
content-language: en
cache-control: no-cache
pragma: no-cache
content-type: text/html;charset=UTF-8
content-length: 581
set-cookie: _sn=81vr7fJb8id45S9Tn2s5x5wIFUdOH4BgUniKcMQuww4_; Version=1; Path=/customer_support

<html><body><form action="/customer_support/start.swe" method="GET" name="RedirectForHost"><input type = "hidden" name="SWECmd" value="GotoView">
<input type = "hidden" name="_sn" value="81vr7fJb8id4
...[SNIP]...
4. HTML does not specify charset  previous

Summary

Severity:   Information
Confidence:   Certain
Host:   https://connect.sungardhe.com
Path:   /

Issue description

If a web response states that it contains HTML content but does not specify a character set, then the browser may analyse the HTML and attempt to determine which character set it appears to be using. Even if the majority of the HTML actually employs a standard character set such as UTF-8, the presence of non-standard characters anywhere in the response may cause the browser to interpret the content using a different character set. This can have unexpected results, and can lead to cross-site scripting vulnerabilities in which non-standard encodings like UTF-7 can be used to bypass the application's defensive filters.

In most cases, the absence of a charset directive does not constitute a security flaw, particularly if the response contains static content. You should review the contents of the response and the context in which it appears to determine whether any vulnerability exists.

Issue remediation

For every response containing HTML content, the application should include within the Content-type header a directive specifying a standard recognised character set, for example charset=ISO-8859-1.

Request

GET / HTTP/1.1
Host: connect.sungardhe.com
Connection: keep-alive
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.10 (KHTML, like Gecko) Chrome/8.0.552.224 Safari/534.10
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

Response

HTTP/1.1 200 OK
Content-Type: text/html
Content-Location: http://connect.sungardhe.com/index.htm
Last-Modified: Mon, 26 Jul 2010 20:14:38 GMT
Accept-Ranges: bytes
ETag: "98f9b12cff2ccb1:f02"
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
Date: Sun, 02 Jan 2011 14:41:31 GMT
Vary: Accept-Encoding
Content-Length: 1451

<HTML>
<HEAD>
<HEAD>
<META HTTP-EQUIV="cache-control" CONTENT="no-cache">
<META HTTP-EQUIV="pragma" CONTENT="no-cache">
<META HTTP-EQUIV="expires" CONTENT="Sat, 01 Jan 2000 05:00:00 GMT">
<TITLE
...[SNIP]...
Report generated by XSS.CX at Sun Jan 02 08:58:30 CST 2011.