SQL Injection, Database Error, CWE-89, CAPEC-66, DORK, GHDB, www2.idexpertscorp.com

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

Report generated by XSS.CX at Mon May 02 15:47:47 CDT 2011.


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

Loading

1. SQL injection

1.1. http://www2.idexpertscorp.com/blog [exp_super_search_history cookie]

1.2. http://www2.idexpertscorp.com/blog/ [exp_super_search_history cookie]

1.3. http://www2.idexpertscorp.com/contact [exp_super_search_history cookie]

2. Cookie without HttpOnly flag set

2.1. http://www2.idexpertscorp.com/contact/

2.2. http://www2.idexpertscorp.com/

2.3. http://www2.idexpertscorp.com/blog/

2.4. http://www2.idexpertscorp.com/page-not-found/

2.5. http://www2.idexpertscorp.com/site/404/

3. Cross-site scripting (reflected)

3.1. http://www2.idexpertscorp.com/blog [exp_super_search_history cookie]

3.2. http://www2.idexpertscorp.com/blog/ [exp_super_search_history cookie]

3.3. http://www2.idexpertscorp.com/contact [exp_super_search_history cookie]

3.4. http://www2.idexpertscorp.com/contact/ [exp_super_search_history cookie]

4. Cross-domain script include

4.1. http://www2.idexpertscorp.com/

4.2. http://www2.idexpertscorp.com/blog/

4.3. http://www2.idexpertscorp.com/contact/

4.4. http://www2.idexpertscorp.com/page-not-found/

5. Email addresses disclosed

5.1. http://www2.idexpertscorp.com/

5.2. http://www2.idexpertscorp.com/blog/

5.3. http://www2.idexpertscorp.com/contact/

5.4. http://www2.idexpertscorp.com/js/hoverintent.js

5.5. http://www2.idexpertscorp.com/js/innerfade.js

5.6. http://www2.idexpertscorp.com/page-not-found/

6. Robots.txt file

7. Content type incorrectly stated



1. SQL injection  next
There are 3 instances of this issue:

Issue background

SQL injection vulnerabilities arise when user-controllable data is incorporated into database SQL queries in an unsafe manner. An attacker can supply crafted input to break out of the data context in which their input appears and interfere with the structure of the surrounding query.

Various attacks can be delivered via SQL injection, including reading or modifying critical application data, interfering with application logic, escalating privileges within the database and executing operating system commands.

Remediation background

The most effective way to prevent SQL injection attacks is to use parameterised queries (also known as prepared statements) for all database access. This method uses two steps to incorporate potentially tainted data into SQL queries: first, the application specifies the structure of the query, leaving placeholders for each item of user input; second, the application specifies the contents of each placeholder. Because the structure of the query has already defined in the first step, it is not possible for malformed data in the second step to interfere with the query structure. You should review the documentation for your database and application platform to determine the appropriate APIs which you can use to perform parameterised queries. It is strongly recommended that you parameterise every variable data item that is incorporated into database queries, even if it is not obviously tainted, to prevent oversights occurring and avoid vulnerabilities being introduced by changes elsewhere within the code base of the application.

You should be aware that some commonly employed and recommended mitigations for SQL injection vulnerabilities are not always effective:



1.1. http://www2.idexpertscorp.com/blog [exp_super_search_history cookie]  next

Summary

Severity:   High
Confidence:   Firm
Host:   http://www2.idexpertscorp.com
Path:   /blog

Issue detail

The exp_super_search_history cookie appears to be vulnerable to SQL injection attacks. The payload ' was submitted in the exp_super_search_history cookie, and a database error message was returned. You should review the contents of the error message, and the application's handling of other input, to confirm whether a vulnerability is present.

The database appears to be MySQL.

Remediation detail

The application should handle errors gracefully and prevent SQL error messages from being returned in responses.

Request

GET /blog HTTP/1.1
Host: www2.idexpertscorp.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.60 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: ubvt=173.193.214.243.1304349963666894; exp_last_visit=989015581; exp_super_search_history=797022'; __switchTo5x=58; __utmz=1.1304368386.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utmz=8236212.1304368386.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); exp_last_activity=1304375596; exp_tracker=a%3A2%3A%7Bi%3A0%3Bs%3A9%3A%22%2Fcontact%2F%22%3Bi%3A1%3Bs%3A5%3A%22index%22%3B%7D; PHPSESSID=jfnbk4r5pvilc331tug96gdad0; __unam=440469-12fb26a1110-5868adc8-3; __utma=1.843288026.1304368386.1304368386.1304368386.1; __utmc=1; __utmb=1.3.10.1304368386; __utma=8236212.1025446137.1304368386.1304368386.1304368386.1; __utmc=8236212; __utmb=8236212.3.10.1304368386

Response (redirected)

HTTP/1.1 500 Internal Server Error
Date: Mon, 02 May 2011 15:41:22 GMT
Server: Apache/2.2.3 (CentOS)
X-Powered-By: PHP/5.2.6
Set-Cookie: exp_last_activity=1304376082; expires=Tue, 01-May-2012 15:41:22 GMT; path=/
Set-Cookie: exp_tracker=a%3A3%3A%7Bi%3A0%3Bs%3A6%3A%22%2Fblog%2F%22%3Bi%3A1%3Bs%3A9%3A%22%2Fcontact%2F%22%3Bi%3A2%3Bs%3A5%3A%22index%22%3B%7D; path=/
Cache-Control: public
Expires: Sat, 07 May 2011 15:41:22 GMT
imagetoolbar: no
Content-Length: 1026
Connection: close
Content-Type: text/html

<html>
<head>
<title>Database Error</title>
<style type="text/css">

body {
background-color:    #fff;
margin:                40px;
font-family:        Lucida Grande, Verdana, Sans-serif;
font-size:            12px;
color:                #000
...[SNIP]...
<p>You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '\' AND saved = 'n' ORDER BY search_date DESC LIMIT 1' at line 3</p>
...[SNIP]...

1.2. http://www2.idexpertscorp.com/blog/ [exp_super_search_history cookie]  previous  next

Summary

Severity:   High
Confidence:   Firm
Host:   http://www2.idexpertscorp.com
Path:   /blog/

Issue detail

The exp_super_search_history cookie appears to be vulnerable to SQL injection attacks. The payload ' was submitted in the exp_super_search_history cookie, and a database error message was returned. You should review the contents of the error message, and the application's handling of other input, to confirm whether a vulnerability is present.

The database appears to be MySQL.

Remediation detail

The application should handle errors gracefully and prevent SQL error messages from being returned in responses.

Request

GET /blog/ HTTP/1.1
Host: www2.idexpertscorp.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.60 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: ubvt=173.193.214.243.1304349963666894; exp_last_visit=989015581; exp_super_search_history=797022'; __switchTo5x=58; __utmz=1.1304368386.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utmz=8236212.1304368386.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); exp_last_activity=1304375596; exp_tracker=a%3A2%3A%7Bi%3A0%3Bs%3A9%3A%22%2Fcontact%2F%22%3Bi%3A1%3Bs%3A5%3A%22index%22%3B%7D; PHPSESSID=jfnbk4r5pvilc331tug96gdad0; __unam=440469-12fb26a1110-5868adc8-3; __utma=1.843288026.1304368386.1304368386.1304368386.1; __utmc=1; __utmb=1.3.10.1304368386; __utma=8236212.1025446137.1304368386.1304368386.1304368386.1; __utmc=8236212; __utmb=8236212.3.10.1304368386

Response

HTTP/1.1 500 Internal Server Error
Date: Mon, 02 May 2011 15:41:59 GMT
Server: Apache/2.2.3 (CentOS)
X-Powered-By: PHP/5.2.6
Set-Cookie: exp_last_activity=1304376119; expires=Tue, 01-May-2012 15:41:59 GMT; path=/
Set-Cookie: exp_tracker=a%3A3%3A%7Bi%3A0%3Bs%3A6%3A%22%2Fblog%2F%22%3Bi%3A1%3Bs%3A9%3A%22%2Fcontact%2F%22%3Bi%3A2%3Bs%3A5%3A%22index%22%3B%7D; path=/
Cache-Control: public
Expires: Sat, 07 May 2011 15:41:59 GMT
imagetoolbar: no
Content-Length: 1026
Connection: close
Content-Type: text/html

<html>
<head>
<title>Database Error</title>
<style type="text/css">

body {
background-color:    #fff;
margin:                40px;
font-family:        Lucida Grande, Verdana, Sans-serif;
font-size:            12px;
color:                #000
...[SNIP]...
<p>You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '\' AND saved = 'n' ORDER BY search_date DESC LIMIT 1' at line 3</p>
...[SNIP]...

1.3. http://www2.idexpertscorp.com/contact [exp_super_search_history cookie]  previous  next

Summary

Severity:   High
Confidence:   Firm
Host:   http://www2.idexpertscorp.com
Path:   /contact

Issue detail

The exp_super_search_history cookie appears to be vulnerable to SQL injection attacks. The payload ' was submitted in the exp_super_search_history cookie, and a database error message was returned. You should review the contents of the error message, and the application's handling of other input, to confirm whether a vulnerability is present.

The database appears to be MySQL.

Remediation detail

The application should handle errors gracefully and prevent SQL error messages from being returned in responses.

Request

GET /contact HTTP/1.1
Host: www2.idexpertscorp.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.60 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: ubvt=173.193.214.243.1304349963666894; exp_last_visit=989015581; exp_last_activity=1304375581; exp_tracker=a%3A1%3A%7Bi%3A0%3Bs%3A5%3A%22index%22%3B%7D; exp_super_search_history=797022'; __switchTo5x=58; __utmz=1.1304368386.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utmz=8236212.1304368386.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __unam=440469-12fb26a1110-5868adc8-2; __utma=1.843288026.1304368386.1304368386.1304368386.1; __utmc=1; __utmb=1.2.10.1304368386; __utma=8236212.1025446137.1304368386.1304368386.1304368386.1; __utmc=8236212; __utmb=8236212.2.10.1304368386

Response (redirected)

HTTP/1.1 500 Internal Server Error
Date: Mon, 02 May 2011 15:42:05 GMT
Server: Apache/2.2.3 (CentOS)
X-Powered-By: PHP/5.2.6
Set-Cookie: exp_last_activity=1304376125; expires=Tue, 01-May-2012 15:42:05 GMT; path=/
Set-Cookie: exp_tracker=a%3A2%3A%7Bi%3A0%3Bs%3A9%3A%22%2Fcontact%2F%22%3Bi%3A1%3Bs%3A5%3A%22index%22%3B%7D; path=/
Set-Cookie: PHPSESSID=lbchnsd618s1qle9mcv7v84hq4; path=/
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: public
Pragma: no-cache
imagetoolbar: no
Content-Length: 1026
Connection: close
Content-Type: text/html

<html>
<head>
<title>Database Error</title>
<style type="text/css">

body {
background-color:    #fff;
margin:                40px;
font-family:        Lucida Grande, Verdana, Sans-serif;
font-size:            12px;
color:                #000
...[SNIP]...
<p>You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '\' AND saved = 'n' ORDER BY search_date DESC LIMIT 1' at line 3</p>
...[SNIP]...

2. Cookie without HttpOnly flag set  previous  next
There are 5 instances of this issue:

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.



2.1. http://www2.idexpertscorp.com/contact/  previous  next

Summary

Severity:   Low
Confidence:   Firm
Host:   http://www2.idexpertscorp.com
Path:   /contact/

Issue detail

The following cookies were issued by the application and do not have the HttpOnly flag set: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.

Request

GET /contact/ HTTP/1.1
Host: www2.idexpertscorp.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.60 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: ubvt=173.193.214.243.1304349963666894; exp_last_visit=989015581; exp_last_activity=1304375581; exp_tracker=a%3A1%3A%7Bi%3A0%3Bs%3A5%3A%22index%22%3B%7D; exp_super_search_history=797022; __switchTo5x=58; __utmz=1.1304368386.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utmz=8236212.1304368386.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __unam=440469-12fb26a1110-5868adc8-2; __utma=1.843288026.1304368386.1304368386.1304368386.1; __utmc=1; __utmb=1.2.10.1304368386; __utma=8236212.1025446137.1304368386.1304368386.1304368386.1; __utmc=8236212; __utmb=8236212.2.10.1304368386

Response

HTTP/1.1 200 OK
Date: Mon, 02 May 2011 15:40:11 GMT
Server: Apache/2.2.3 (CentOS)
X-Powered-By: PHP/5.2.6
Set-Cookie: exp_last_activity=1304376011; expires=Tue, 01-May-2012 15:40:11 GMT; path=/
Set-Cookie: exp_tracker=a%3A2%3A%7Bi%3A0%3Bs%3A9%3A%22%2Fcontact%2F%22%3Bi%3A1%3Bs%3A5%3A%22index%22%3B%7D; path=/
Set-Cookie: PHPSESSID=40n55sb8ve3v3kejrdj5579bq0; path=/
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: public
Pragma: no-cache
Vary: Accept-Encoding
imagetoolbar: no
Content-Type: text/html; charset=utf-8
Content-Length: 24096

<!DOCTYPE html>

<html>
<head>

<link rel="stylesheet" type="text/css" media="all" href="/css/base.css" />
<link rel="stylesheet" type="text/css" media="all" href="/css/type-image.css" />
<lin
...[SNIP]...

2.2. http://www2.idexpertscorp.com/  previous  next

Summary

Severity:   Information
Confidence:   Certain
Host:   http://www2.idexpertscorp.com
Path:   /

Issue detail

The following cookies were issued by the application and do not have the HttpOnly flag set:The cookies do not appear to contain session tokens, which may reduce the risk associated with this issue. You should review the contents of the cookies to determine their function.

Request

GET / HTTP/1.1
Host: www2.idexpertscorp.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.60 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: ubvt=173.193.214.243.1304349963666894

Response

HTTP/1.1 200 OK
Date: Mon, 02 May 2011 15:38:34 GMT
Server: Apache/2.2.3 (CentOS)
X-Powered-By: PHP/5.2.6
Set-Cookie: exp_last_visit=989015914; expires=Tue, 01-May-2012 15:38:34 GMT; path=/
Set-Cookie: exp_last_activity=1304375914; expires=Tue, 01-May-2012 15:38:34 GMT; path=/
Set-Cookie: exp_tracker=a%3A1%3A%7Bi%3A0%3Bs%3A5%3A%22index%22%3B%7D; path=/
Set-Cookie: exp_super_search_history=151186; expires=Tue, 03-May-2011 15:40:14 GMT; path=/
Vary: Accept-Encoding
Cache-Control: public
Expires: Sat, 07 May 2011 15:38:34 GMT
imagetoolbar: no
Content-Type: text/html; charset=utf-8
Content-Length: 36977

<!DOCTYPE html>

<html>
<head>

<link rel="stylesheet" type="text/css" media="all" href="/css/base.css" />
<link rel="stylesheet" type="text/css" media="all" href="/css/type-image.css" />
<link
...[SNIP]...

2.3. http://www2.idexpertscorp.com/blog/  previous  next

Summary

Severity:   Information
Confidence:   Certain
Host:   http://www2.idexpertscorp.com
Path:   /blog/

Issue detail

The following cookies were issued by the application and do not have the HttpOnly flag set:The cookies do not appear to contain session tokens, which may reduce the risk associated with this issue. You should review the contents of the cookies to determine their function.

Request

GET /blog/ HTTP/1.1
Host: www2.idexpertscorp.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.60 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: ubvt=173.193.214.243.1304349963666894; exp_last_visit=989015581; exp_super_search_history=797022; __switchTo5x=58; __utmz=1.1304368386.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utmz=8236212.1304368386.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); exp_last_activity=1304375596; exp_tracker=a%3A2%3A%7Bi%3A0%3Bs%3A9%3A%22%2Fcontact%2F%22%3Bi%3A1%3Bs%3A5%3A%22index%22%3B%7D; PHPSESSID=jfnbk4r5pvilc331tug96gdad0; __unam=440469-12fb26a1110-5868adc8-3; __utma=1.843288026.1304368386.1304368386.1304368386.1; __utmc=1; __utmb=1.3.10.1304368386; __utma=8236212.1025446137.1304368386.1304368386.1304368386.1; __utmc=8236212; __utmb=8236212.3.10.1304368386

Response

HTTP/1.1 200 OK
Date: Mon, 02 May 2011 15:40:36 GMT
Server: Apache/2.2.3 (CentOS)
X-Powered-By: PHP/5.2.6
Set-Cookie: exp_last_activity=1304376036; expires=Tue, 01-May-2012 15:40:36 GMT; path=/
Set-Cookie: exp_tracker=a%3A3%3A%7Bi%3A0%3Bs%3A6%3A%22%2Fblog%2F%22%3Bi%3A1%3Bs%3A9%3A%22%2Fcontact%2F%22%3Bi%3A2%3Bs%3A5%3A%22index%22%3B%7D; path=/
Vary: Accept-Encoding
Cache-Control: public
Expires: Sat, 07 May 2011 15:40:36 GMT
imagetoolbar: no
Content-Type: text/html; charset=utf-8
Content-Length: 39977


<!DOCTYPE html>

<html>
<head>

<link rel="stylesheet" type="text/css" media="all" href="/css/base.css" />
<link rel="stylesheet" type="text/css" media="all" href="/css/type-image.css" />
<link
...[SNIP]...

2.4. http://www2.idexpertscorp.com/page-not-found/  previous  next

Summary

Severity:   Information
Confidence:   Certain
Host:   http://www2.idexpertscorp.com
Path:   /page-not-found/

Issue detail

The following cookies were issued by the application and do not have the HttpOnly flag set:The cookies do not appear to contain session tokens, which may reduce the risk associated with this issue. You should review the contents of the cookies to determine their function.

Request

GET /page-not-found/ HTTP/1.1
Accept: */*
Accept-Language: en-US
Accept-Encoding: gzip, deflate
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.1; WOW64; Trident/5.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 1.1.4322; .NET CLR 3.5.30729; .NET CLR 3.0.30729; .NET4.0C; .NET4.0E)
Proxy-Connection: Keep-Alive
Host: www2.idexpertscorp.com

Response

HTTP/1.1 200 OK
Date: Mon, 02 May 2011 15:45:24 GMT
Server: Apache/2.2.3 (CentOS)
X-Powered-By: PHP/5.2.6
Set-Cookie: exp_last_visit=989016324; expires=Tue, 01-May-2012 15:45:24 GMT; path=/
Set-Cookie: exp_last_activity=1304376324; expires=Tue, 01-May-2012 15:45:24 GMT; path=/
Set-Cookie: exp_tracker=a%3A1%3A%7Bi%3A0%3Bs%3A16%3A%22%2Fpage-not-found%2F%22%3B%7D; path=/
Set-Cookie: exp_super_search_history=813764; expires=Tue, 03-May-2011 15:47:09 GMT; path=/
Vary: Accept-Encoding
Cache-Control: public
Expires: Sat, 07 May 2011 15:45:24 GMT
imagetoolbar: no
Content-Type: text/html; charset=utf-8
Content-Length: 21076


<!DOCTYPE html>

<html>
<head>

<link rel="stylesheet" type="text/css" media="all" href="/css/base.css" />
<link rel="stylesheet" type="text/css" media="all" href="/css/type-image.css" />
<lin
...[SNIP]...

2.5. http://www2.idexpertscorp.com/site/404/  previous  next

Summary

Severity:   Information
Confidence:   Certain
Host:   http://www2.idexpertscorp.com
Path:   /site/404/

Issue detail

The following cookies were issued by the application and do not have the HttpOnly flag set:The cookies do not appear to contain session tokens, which may reduce the risk associated with this issue. You should review the contents of the cookies to determine their function.

Request

GET /site/404/ HTTP/1.1
Accept: */*
Accept-Language: en-US
Accept-Encoding: gzip, deflate
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.1; WOW64; Trident/5.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 1.1.4322; .NET CLR 3.5.30729; .NET CLR 3.0.30729; .NET4.0C; .NET4.0E)
Host: www2.idexpertscorp.com
Proxy-Connection: Keep-Alive

Response

HTTP/1.1 302 Found
Date: Mon, 02 May 2011 15:45:18 GMT
Server: Apache/2.2.3 (CentOS)
X-Powered-By: PHP/5.2.6
Set-Cookie: exp_last_visit=989016318; expires=Tue, 01-May-2012 15:45:18 GMT; path=/
Set-Cookie: exp_last_activity=1304376318; expires=Tue, 01-May-2012 15:45:18 GMT; path=/
Set-Cookie: exp_tracker=a%3A1%3A%7Bi%3A0%3Bs%3A10%3A%22%2Fsite%2F404%2F%22%3B%7D; path=/
Set-Cookie: exp_super_search_history=192856; expires=Tue, 03-May-2011 15:46:59 GMT; path=/
Location: http://www2.idexpertscorp.com/page-not-found/
Cache-Control: public
Expires: Sat, 07 May 2011 15:45:18 GMT
imagetoolbar: no
Content-Length: 0
Content-Type: text/html


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

Issue background

Reflected cross-site scripting vulnerabilities arise when data is copied from a request and echoed into the application's immediate response in an unsafe way. An attacker can use the vulnerability to construct a request which, if issued by another application user, will cause JavaScript code supplied by the attacker to execute within the user's browser in the context of that user's session with the application.

The attacker-supplied code can perform a wide variety of actions, such as stealing the victim's session token or login credentials, performing arbitrary actions on the victim's behalf, and logging their keystrokes.

Users can be induced to issue the attacker's crafted request in various ways. For example, the attacker can send a victim a link containing a malicious URL in an email or instant message. They can submit the link to popular web sites that allow content authoring, for example in blog comments. And they can create an innocuous looking web site which causes anyone viewing it to make arbitrary cross-domain requests to the vulnerable application (using either the GET or the POST method).

The security impact of cross-site scripting vulnerabilities is dependent upon the nature of the vulnerable application, the kinds of data and functionality which it contains, and the other applications which belong to the same domain and organisation. If the application is used only to display non-sensitive public content, with no authentication or access control functionality, then a cross-site scripting flaw may be considered low risk. However, if the same application resides on a domain which can access cookies for other more security-critical applications, then the vulnerability could be used to attack those other applications, and so may be considered high risk. Similarly, if the organisation which owns the application is a likely target for phishing attacks, then the vulnerability could be leveraged to lend credibility to such attacks, by injecting Trojan functionality into the vulnerable application, and exploiting users' trust in the organisation in order to capture credentials for other applications which it owns. In many kinds of application, such as those providing online banking functionality, cross-site scripting should always be considered high risk.

Issue remediation

In most situations where user-controllable data is copied into application responses, cross-site scripting attacks can be prevented using two layers of defences:In cases where the application's functionality allows users to author content using a restricted subset of HTML tags and attributes (for example, blog comments which allow limited formatting and linking), it is necessary to parse the supplied HTML to validate that it does not use any dangerous syntax; this is a non-trivial task.


3.1. http://www2.idexpertscorp.com/blog [exp_super_search_history cookie]  previous  next

Summary

Severity:   Information
Confidence:   Firm
Host:   http://www2.idexpertscorp.com
Path:   /blog

Issue detail

The value of the exp_super_search_history cookie is copied into the HTML document as plain text between tags. The payload 5a3d3<a>6ca4c3adbac was submitted in the exp_super_search_history cookie. This input was echoed unmodified in the application's response.

This behaviour demonstrates that it is possible to inject new HTML tags into the returned document. An attempt was made to identify a full proof-of-concept attack for injecting arbitrary JavaScript but this was not successful. You should manually examine the application's behaviour and attempt to identify any unusual input validation or other obstacles that may be in place.

Note that a redirection occurred between the attack request and the response containing the echoed input. It is necessary to follow this redirection for the attack to succeed. When the attack is carried out via a browser, the redirection will be followed automatically.

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 /blog HTTP/1.1
Host: www2.idexpertscorp.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.60 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: ubvt=173.193.214.243.1304349963666894; exp_last_visit=989015581; exp_super_search_history=7970225a3d3<a>6ca4c3adbac; __switchTo5x=58; __utmz=1.1304368386.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utmz=8236212.1304368386.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); exp_last_activity=1304375596; exp_tracker=a%3A2%3A%7Bi%3A0%3Bs%3A9%3A%22%2Fcontact%2F%22%3Bi%3A1%3Bs%3A5%3A%22index%22%3B%7D; PHPSESSID=jfnbk4r5pvilc331tug96gdad0; __unam=440469-12fb26a1110-5868adc8-3; __utma=1.843288026.1304368386.1304368386.1304368386.1; __utmc=1; __utmb=1.3.10.1304368386; __utma=8236212.1025446137.1304368386.1304368386.1304368386.1; __utmc=8236212; __utmb=8236212.3.10.1304368386

Response (redirected)

HTTP/1.1 500 Internal Server Error
Date: Mon, 02 May 2011 15:41:12 GMT
Server: Apache/2.2.3 (CentOS)
X-Powered-By: PHP/5.2.6
Set-Cookie: exp_last_activity=1304376072; expires=Tue, 01-May-2012 15:41:12 GMT; path=/
Set-Cookie: exp_tracker=a%3A3%3A%7Bi%3A0%3Bs%3A6%3A%22%2Fblog%2F%22%3Bi%3A1%3Bs%3A9%3A%22%2Fcontact%2F%22%3Bi%3A2%3Bs%3A5%3A%22index%22%3B%7D; path=/
Cache-Control: public
Expires: Sat, 07 May 2011 15:41:12 GMT
imagetoolbar: no
Content-Length: 891
Connection: close
Content-Type: text/html

<html>
<head>
<title>Database Error</title>
<style type="text/css">

body {
background-color:    #fff;
margin:                40px;
font-family:        Lucida Grande, Verdana, Sans-serif;
font-size:            12px;
color:                #000
...[SNIP]...
ars */ SELECT history_id AS search_id, search_date AS super_search_date, search_name AS name, results, saved, query
                   FROM exp_super_search_history
                   WHERE site_id IN ( 1 ) AND cookie_id = 7970225a3d3<a>6ca4c3adbac AND saved = 'n' ORDER BY search_date DESC LIMIT 1</p>
...[SNIP]...

3.2. http://www2.idexpertscorp.com/blog/ [exp_super_search_history cookie]  previous  next

Summary

Severity:   Information
Confidence:   Firm
Host:   http://www2.idexpertscorp.com
Path:   /blog/

Issue detail

The value of the exp_super_search_history cookie is copied into the HTML document as plain text between tags. The payload 81b42<a>b585e06ed59 was submitted in the exp_super_search_history cookie. This input was echoed unmodified in the application's response.

This behaviour demonstrates that it is possible to inject new HTML tags into the returned document. An attempt was made to identify a full proof-of-concept attack for injecting arbitrary JavaScript but this was not successful. You should manually examine the application's behaviour and attempt to identify any unusual input validation or other obstacles that may be in place.

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 /blog/ HTTP/1.1
Host: www2.idexpertscorp.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.60 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: ubvt=173.193.214.243.1304349963666894; exp_last_visit=989015581; exp_super_search_history=79702281b42<a>b585e06ed59; __switchTo5x=58; __utmz=1.1304368386.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utmz=8236212.1304368386.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); exp_last_activity=1304375596; exp_tracker=a%3A2%3A%7Bi%3A0%3Bs%3A9%3A%22%2Fcontact%2F%22%3Bi%3A1%3Bs%3A5%3A%22index%22%3B%7D; PHPSESSID=jfnbk4r5pvilc331tug96gdad0; __unam=440469-12fb26a1110-5868adc8-3; __utma=1.843288026.1304368386.1304368386.1304368386.1; __utmc=1; __utmb=1.3.10.1304368386; __utma=8236212.1025446137.1304368386.1304368386.1304368386.1; __utmc=8236212; __utmb=8236212.3.10.1304368386

Response

HTTP/1.1 500 Internal Server Error
Date: Mon, 02 May 2011 15:41:49 GMT
Server: Apache/2.2.3 (CentOS)
X-Powered-By: PHP/5.2.6
Set-Cookie: exp_last_activity=1304376109; expires=Tue, 01-May-2012 15:41:49 GMT; path=/
Set-Cookie: exp_tracker=a%3A3%3A%7Bi%3A0%3Bs%3A6%3A%22%2Fblog%2F%22%3Bi%3A1%3Bs%3A9%3A%22%2Fcontact%2F%22%3Bi%3A2%3Bs%3A5%3A%22index%22%3B%7D; path=/
Cache-Control: public
Expires: Sat, 07 May 2011 15:41:49 GMT
imagetoolbar: no
Content-Length: 891
Connection: close
Content-Type: text/html

<html>
<head>
<title>Database Error</title>
<style type="text/css">

body {
background-color:    #fff;
margin:                40px;
font-family:        Lucida Grande, Verdana, Sans-serif;
font-size:            12px;
color:                #000
...[SNIP]...
ars */ SELECT history_id AS search_id, search_date AS super_search_date, search_name AS name, results, saved, query
                   FROM exp_super_search_history
                   WHERE site_id IN ( 1 ) AND cookie_id = 79702281b42<a>b585e06ed59 AND saved = 'n' ORDER BY search_date DESC LIMIT 1</p>
...[SNIP]...

3.3. http://www2.idexpertscorp.com/contact [exp_super_search_history cookie]  previous  next

Summary

Severity:   Information
Confidence:   Firm
Host:   http://www2.idexpertscorp.com
Path:   /contact

Issue detail

The value of the exp_super_search_history cookie is copied into the HTML document as plain text between tags. The payload c0de3<a>bcf3551774d was submitted in the exp_super_search_history cookie. This input was echoed unmodified in the application's response.

This behaviour demonstrates that it is possible to inject new HTML tags into the returned document. An attempt was made to identify a full proof-of-concept attack for injecting arbitrary JavaScript but this was not successful. You should manually examine the application's behaviour and attempt to identify any unusual input validation or other obstacles that may be in place.

Note that a redirection occurred between the attack request and the response containing the echoed input. It is necessary to follow this redirection for the attack to succeed. When the attack is carried out via a browser, the redirection will be followed automatically.

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 /contact HTTP/1.1
Host: www2.idexpertscorp.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.60 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: ubvt=173.193.214.243.1304349963666894; exp_last_visit=989015581; exp_last_activity=1304375581; exp_tracker=a%3A1%3A%7Bi%3A0%3Bs%3A5%3A%22index%22%3B%7D; exp_super_search_history=797022c0de3<a>bcf3551774d; __switchTo5x=58; __utmz=1.1304368386.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utmz=8236212.1304368386.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __unam=440469-12fb26a1110-5868adc8-2; __utma=1.843288026.1304368386.1304368386.1304368386.1; __utmc=1; __utmb=1.2.10.1304368386; __utma=8236212.1025446137.1304368386.1304368386.1304368386.1; __utmc=8236212; __utmb=8236212.2.10.1304368386

Response (redirected)

HTTP/1.1 500 Internal Server Error
Date: Mon, 02 May 2011 15:41:56 GMT
Server: Apache/2.2.3 (CentOS)
X-Powered-By: PHP/5.2.6
Set-Cookie: exp_last_activity=1304376116; expires=Tue, 01-May-2012 15:41:56 GMT; path=/
Set-Cookie: exp_tracker=a%3A2%3A%7Bi%3A0%3Bs%3A9%3A%22%2Fcontact%2F%22%3Bi%3A1%3Bs%3A5%3A%22index%22%3B%7D; path=/
Set-Cookie: PHPSESSID=qto52m8imfp5rf5ds45hghbcv5; path=/
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: public
Pragma: no-cache
imagetoolbar: no
Content-Length: 891
Connection: close
Content-Type: text/html

<html>
<head>
<title>Database Error</title>
<style type="text/css">

body {
background-color:    #fff;
margin:                40px;
font-family:        Lucida Grande, Verdana, Sans-serif;
font-size:            12px;
color:                #000
...[SNIP]...
ars */ SELECT history_id AS search_id, search_date AS super_search_date, search_name AS name, results, saved, query
                   FROM exp_super_search_history
                   WHERE site_id IN ( 1 ) AND cookie_id = 797022c0de3<a>bcf3551774d AND saved = 'n' ORDER BY search_date DESC LIMIT 1</p>
...[SNIP]...

3.4. http://www2.idexpertscorp.com/contact/ [exp_super_search_history cookie]  previous  next

Summary

Severity:   Information
Confidence:   Firm
Host:   http://www2.idexpertscorp.com
Path:   /contact/

Issue detail

The value of the exp_super_search_history cookie is copied into the HTML document as plain text between tags. The payload 22076<a>d08a9486a08 was submitted in the exp_super_search_history cookie. This input was echoed unmodified in the application's response.

This behaviour demonstrates that it is possible to inject new HTML tags into the returned document. An attempt was made to identify a full proof-of-concept attack for injecting arbitrary JavaScript but this was not successful. You should manually examine the application's behaviour and attempt to identify any unusual input validation or other obstacles that may be in place.

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 /contact/ HTTP/1.1
Host: www2.idexpertscorp.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.60 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: ubvt=173.193.214.243.1304349963666894; exp_last_visit=989015581; exp_last_activity=1304375581; exp_tracker=a%3A1%3A%7Bi%3A0%3Bs%3A5%3A%22index%22%3B%7D; exp_super_search_history=79702222076<a>d08a9486a08; __switchTo5x=58; __utmz=1.1304368386.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utmz=8236212.1304368386.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __unam=440469-12fb26a1110-5868adc8-2; __utma=1.843288026.1304368386.1304368386.1304368386.1; __utmc=1; __utmb=1.2.10.1304368386; __utma=8236212.1025446137.1304368386.1304368386.1304368386.1; __utmc=8236212; __utmb=8236212.2.10.1304368386

Response

HTTP/1.1 500 Internal Server Error
Date: Mon, 02 May 2011 15:43:09 GMT
Server: Apache/2.2.3 (CentOS)
X-Powered-By: PHP/5.2.6
Set-Cookie: exp_last_activity=1304376189; expires=Tue, 01-May-2012 15:43:09 GMT; path=/
Set-Cookie: exp_tracker=a%3A2%3A%7Bi%3A0%3Bs%3A9%3A%22%2Fcontact%2F%22%3Bi%3A1%3Bs%3A5%3A%22index%22%3B%7D; path=/
Set-Cookie: PHPSESSID=bgsq4cr4fhtafle4vprrespkh5; path=/
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: public
Pragma: no-cache
imagetoolbar: no
Content-Length: 881
Connection: close
Content-Type: text/html

<html>
<head>
<title>Database Error</title>
<style type="text/css">

body {
background-color:    #fff;
margin:                40px;
font-family:        Lucida Grande, Verdana, Sans-serif;
font-size:            12px;
color:                #000
...[SNIP]...
ars */ SELECT history_id AS search_id, search_date AS super_search_date, search_name AS name, results, saved, query
                   FROM exp_super_search_history
                   WHERE site_id IN ( 1 ) AND cookie_id = 79702222076<a>d08a9486a08 AND saved = 'n' ORDER BY search_date DESC LIMIT 1</p>
...[SNIP]...

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

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://www2.idexpertscorp.com/  previous  next

Summary

Severity:   Information
Confidence:   Certain
Host:   http://www2.idexpertscorp.com
Path:   /

Issue detail

The response dynamically includes the following script from another domain:

Request

GET / HTTP/1.1
Host: www2.idexpertscorp.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.60 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: ubvt=173.193.214.243.1304349963666894

Response

HTTP/1.1 200 OK
Date: Mon, 02 May 2011 15:38:34 GMT
Server: Apache/2.2.3 (CentOS)
X-Powered-By: PHP/5.2.6
Set-Cookie: exp_last_visit=989015914; expires=Tue, 01-May-2012 15:38:34 GMT; path=/
Set-Cookie: exp_last_activity=1304375914; expires=Tue, 01-May-2012 15:38:34 GMT; path=/
Set-Cookie: exp_tracker=a%3A1%3A%7Bi%3A0%3Bs%3A5%3A%22index%22%3B%7D; path=/
Set-Cookie: exp_super_search_history=151186; expires=Tue, 03-May-2011 15:40:14 GMT; path=/
Vary: Accept-Encoding
Cache-Control: public
Expires: Sat, 07 May 2011 15:38:34 GMT
imagetoolbar: no
Content-Type: text/html; charset=utf-8
Content-Length: 36977

<!DOCTYPE html>

<html>
<head>

<link rel="stylesheet" type="text/css" media="all" href="/css/base.css" />
<link rel="stylesheet" type="text/css" media="all" href="/css/type-image.css" />
<link
...[SNIP]...
</script>


<script type="text/javascript" src="http://w.sharethis.com/button/buttons.js"></script>
...[SNIP]...

4.2. http://www2.idexpertscorp.com/blog/  previous  next

Summary

Severity:   Information
Confidence:   Certain
Host:   http://www2.idexpertscorp.com
Path:   /blog/

Issue detail

The response dynamically includes the following script from another domain:

Request

GET /blog/ HTTP/1.1
Host: www2.idexpertscorp.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.60 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: ubvt=173.193.214.243.1304349963666894; exp_last_visit=989015581; exp_super_search_history=797022; __switchTo5x=58; __utmz=1.1304368386.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utmz=8236212.1304368386.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); exp_last_activity=1304375596; exp_tracker=a%3A2%3A%7Bi%3A0%3Bs%3A9%3A%22%2Fcontact%2F%22%3Bi%3A1%3Bs%3A5%3A%22index%22%3B%7D; PHPSESSID=jfnbk4r5pvilc331tug96gdad0; __unam=440469-12fb26a1110-5868adc8-3; __utma=1.843288026.1304368386.1304368386.1304368386.1; __utmc=1; __utmb=1.3.10.1304368386; __utma=8236212.1025446137.1304368386.1304368386.1304368386.1; __utmc=8236212; __utmb=8236212.3.10.1304368386

Response

HTTP/1.1 200 OK
Date: Mon, 02 May 2011 15:40:36 GMT
Server: Apache/2.2.3 (CentOS)
X-Powered-By: PHP/5.2.6
Set-Cookie: exp_last_activity=1304376036; expires=Tue, 01-May-2012 15:40:36 GMT; path=/
Set-Cookie: exp_tracker=a%3A3%3A%7Bi%3A0%3Bs%3A6%3A%22%2Fblog%2F%22%3Bi%3A1%3Bs%3A9%3A%22%2Fcontact%2F%22%3Bi%3A2%3Bs%3A5%3A%22index%22%3B%7D; path=/
Vary: Accept-Encoding
Cache-Control: public
Expires: Sat, 07 May 2011 15:40:36 GMT
imagetoolbar: no
Content-Type: text/html; charset=utf-8
Content-Length: 39977


<!DOCTYPE html>

<html>
<head>

<link rel="stylesheet" type="text/css" media="all" href="/css/base.css" />
<link rel="stylesheet" type="text/css" media="all" href="/css/type-image.css" />
<link
...[SNIP]...
</script>


<script type="text/javascript" src="http://w.sharethis.com/button/buttons.js"></script>
...[SNIP]...

4.3. http://www2.idexpertscorp.com/contact/  previous  next

Summary

Severity:   Information
Confidence:   Certain
Host:   http://www2.idexpertscorp.com
Path:   /contact/

Issue detail

The response dynamically includes the following script from another domain:

Request

GET /contact/ HTTP/1.1
Host: www2.idexpertscorp.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.60 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: ubvt=173.193.214.243.1304349963666894; exp_last_visit=989015581; exp_last_activity=1304375581; exp_tracker=a%3A1%3A%7Bi%3A0%3Bs%3A5%3A%22index%22%3B%7D; exp_super_search_history=797022; __switchTo5x=58; __utmz=1.1304368386.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utmz=8236212.1304368386.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __unam=440469-12fb26a1110-5868adc8-2; __utma=1.843288026.1304368386.1304368386.1304368386.1; __utmc=1; __utmb=1.2.10.1304368386; __utma=8236212.1025446137.1304368386.1304368386.1304368386.1; __utmc=8236212; __utmb=8236212.2.10.1304368386

Response

HTTP/1.1 200 OK
Date: Mon, 02 May 2011 15:40:11 GMT
Server: Apache/2.2.3 (CentOS)
X-Powered-By: PHP/5.2.6
Set-Cookie: exp_last_activity=1304376011; expires=Tue, 01-May-2012 15:40:11 GMT; path=/
Set-Cookie: exp_tracker=a%3A2%3A%7Bi%3A0%3Bs%3A9%3A%22%2Fcontact%2F%22%3Bi%3A1%3Bs%3A5%3A%22index%22%3B%7D; path=/
Set-Cookie: PHPSESSID=40n55sb8ve3v3kejrdj5579bq0; path=/
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: public
Pragma: no-cache
Vary: Accept-Encoding
imagetoolbar: no
Content-Type: text/html; charset=utf-8
Content-Length: 24096

<!DOCTYPE html>

<html>
<head>

<link rel="stylesheet" type="text/css" media="all" href="/css/base.css" />
<link rel="stylesheet" type="text/css" media="all" href="/css/type-image.css" />
<lin
...[SNIP]...
</script>


<script type="text/javascript" src="http://w.sharethis.com/button/buttons.js"></script>
...[SNIP]...

4.4. http://www2.idexpertscorp.com/page-not-found/  previous  next

Summary

Severity:   Information
Confidence:   Certain
Host:   http://www2.idexpertscorp.com
Path:   /page-not-found/

Issue detail

The response dynamically includes the following script from another domain:

Request

GET /page-not-found/ HTTP/1.1
Accept: */*
Accept-Language: en-US
Accept-Encoding: gzip, deflate
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.1; WOW64; Trident/5.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 1.1.4322; .NET CLR 3.5.30729; .NET CLR 3.0.30729; .NET4.0C; .NET4.0E)
Proxy-Connection: Keep-Alive
Host: www2.idexpertscorp.com

Response

HTTP/1.1 200 OK
Date: Mon, 02 May 2011 15:45:24 GMT
Server: Apache/2.2.3 (CentOS)
X-Powered-By: PHP/5.2.6
Set-Cookie: exp_last_visit=989016324; expires=Tue, 01-May-2012 15:45:24 GMT; path=/
Set-Cookie: exp_last_activity=1304376324; expires=Tue, 01-May-2012 15:45:24 GMT; path=/
Set-Cookie: exp_tracker=a%3A1%3A%7Bi%3A0%3Bs%3A16%3A%22%2Fpage-not-found%2F%22%3B%7D; path=/
Set-Cookie: exp_super_search_history=813764; expires=Tue, 03-May-2011 15:47:09 GMT; path=/
Vary: Accept-Encoding
Cache-Control: public
Expires: Sat, 07 May 2011 15:45:24 GMT
imagetoolbar: no
Content-Type: text/html; charset=utf-8
Content-Length: 21076


<!DOCTYPE html>

<html>
<head>

<link rel="stylesheet" type="text/css" media="all" href="/css/base.css" />
<link rel="stylesheet" type="text/css" media="all" href="/css/type-image.css" />
<lin
...[SNIP]...
</script>


<script type="text/javascript" src="http://w.sharethis.com/button/buttons.js"></script>
...[SNIP]...

5. Email addresses disclosed  previous  next
There are 6 instances of this issue:

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


5.1. http://www2.idexpertscorp.com/  previous  next

Summary

Severity:   Information
Confidence:   Certain
Host:   http://www2.idexpertscorp.com
Path:   /

Issue detail

The following email address was disclosed in the response:

Request

GET / HTTP/1.1
Host: www2.idexpertscorp.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.60 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: ubvt=173.193.214.243.1304349963666894

Response

HTTP/1.1 200 OK
Date: Mon, 02 May 2011 15:38:34 GMT
Server: Apache/2.2.3 (CentOS)
X-Powered-By: PHP/5.2.6
Set-Cookie: exp_last_visit=989015914; expires=Tue, 01-May-2012 15:38:34 GMT; path=/
Set-Cookie: exp_last_activity=1304375914; expires=Tue, 01-May-2012 15:38:34 GMT; path=/
Set-Cookie: exp_tracker=a%3A1%3A%7Bi%3A0%3Bs%3A5%3A%22index%22%3B%7D; path=/
Set-Cookie: exp_super_search_history=151186; expires=Tue, 03-May-2011 15:40:14 GMT; path=/
Vary: Accept-Encoding
Cache-Control: public
Expires: Sat, 07 May 2011 15:38:34 GMT
imagetoolbar: no
Content-Type: text/html; charset=utf-8
Content-Length: 36977

<!DOCTYPE html>

<html>
<head>

<link rel="stylesheet" type="text/css" media="all" href="/css/base.css" />
<link rel="stylesheet" type="text/css" media="all" href="/css/type-image.css" />
<link
...[SNIP]...
<input type=hidden name="notification" value="susan.rook@idexpertscorp.com" />
<input type=hidden name="contactemail" value="susan.rook@idexpertscorp.com" />
...[SNIP]...

5.2. http://www2.idexpertscorp.com/blog/  previous  next

Summary

Severity:   Information
Confidence:   Certain
Host:   http://www2.idexpertscorp.com
Path:   /blog/

Issue detail

The following email address was disclosed in the response:

Request

GET /blog/ HTTP/1.1
Host: www2.idexpertscorp.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.60 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: ubvt=173.193.214.243.1304349963666894; exp_last_visit=989015581; exp_super_search_history=797022; __switchTo5x=58; __utmz=1.1304368386.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utmz=8236212.1304368386.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); exp_last_activity=1304375596; exp_tracker=a%3A2%3A%7Bi%3A0%3Bs%3A9%3A%22%2Fcontact%2F%22%3Bi%3A1%3Bs%3A5%3A%22index%22%3B%7D; PHPSESSID=jfnbk4r5pvilc331tug96gdad0; __unam=440469-12fb26a1110-5868adc8-3; __utma=1.843288026.1304368386.1304368386.1304368386.1; __utmc=1; __utmb=1.3.10.1304368386; __utma=8236212.1025446137.1304368386.1304368386.1304368386.1; __utmc=8236212; __utmb=8236212.3.10.1304368386

Response

HTTP/1.1 200 OK
Date: Mon, 02 May 2011 15:40:36 GMT
Server: Apache/2.2.3 (CentOS)
X-Powered-By: PHP/5.2.6
Set-Cookie: exp_last_activity=1304376036; expires=Tue, 01-May-2012 15:40:36 GMT; path=/
Set-Cookie: exp_tracker=a%3A3%3A%7Bi%3A0%3Bs%3A6%3A%22%2Fblog%2F%22%3Bi%3A1%3Bs%3A9%3A%22%2Fcontact%2F%22%3Bi%3A2%3Bs%3A5%3A%22index%22%3B%7D; path=/
Vary: Accept-Encoding
Cache-Control: public
Expires: Sat, 07 May 2011 15:40:36 GMT
imagetoolbar: no
Content-Type: text/html; charset=utf-8
Content-Length: 39977


<!DOCTYPE html>

<html>
<head>

<link rel="stylesheet" type="text/css" media="all" href="/css/base.css" />
<link rel="stylesheet" type="text/css" media="all" href="/css/type-image.css" />
<link
...[SNIP]...
<input type=hidden name="notification" value="susan.rook@idexpertscorp.com" />
<input type=hidden name="contactemail" value="susan.rook@idexpertscorp.com" />
...[SNIP]...
<input type=hidden name="notification" value="susan.rook@idexpertscorp.com" />
<input type=hidden name="contactemail" value="susan.rook@idexpertscorp.com" />
...[SNIP]...

5.3. http://www2.idexpertscorp.com/contact/  previous  next

Summary

Severity:   Information
Confidence:   Certain
Host:   http://www2.idexpertscorp.com
Path:   /contact/

Issue detail

The following email address was disclosed in the response:

Request

GET /contact/ HTTP/1.1
Host: www2.idexpertscorp.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.60 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: ubvt=173.193.214.243.1304349963666894; exp_last_visit=989015581; exp_last_activity=1304375581; exp_tracker=a%3A1%3A%7Bi%3A0%3Bs%3A5%3A%22index%22%3B%7D; exp_super_search_history=797022; __switchTo5x=58; __utmz=1.1304368386.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utmz=8236212.1304368386.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __unam=440469-12fb26a1110-5868adc8-2; __utma=1.843288026.1304368386.1304368386.1304368386.1; __utmc=1; __utmb=1.2.10.1304368386; __utma=8236212.1025446137.1304368386.1304368386.1304368386.1; __utmc=8236212; __utmb=8236212.2.10.1304368386

Response

HTTP/1.1 200 OK
Date: Mon, 02 May 2011 15:40:11 GMT
Server: Apache/2.2.3 (CentOS)
X-Powered-By: PHP/5.2.6
Set-Cookie: exp_last_activity=1304376011; expires=Tue, 01-May-2012 15:40:11 GMT; path=/
Set-Cookie: exp_tracker=a%3A2%3A%7Bi%3A0%3Bs%3A9%3A%22%2Fcontact%2F%22%3Bi%3A1%3Bs%3A5%3A%22index%22%3B%7D; path=/
Set-Cookie: PHPSESSID=40n55sb8ve3v3kejrdj5579bq0; path=/
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: public
Pragma: no-cache
Vary: Accept-Encoding
imagetoolbar: no
Content-Type: text/html; charset=utf-8
Content-Length: 24096

<!DOCTYPE html>

<html>
<head>

<link rel="stylesheet" type="text/css" media="all" href="/css/base.css" />
<link rel="stylesheet" type="text/css" media="all" href="/css/type-image.css" />
<lin
...[SNIP]...
<input type=hidden name="notification" value="susan.rook@idexpertscorp.com" />
<input type=hidden name="contactemail" value="susan.rook@idexpertscorp.com" />
...[SNIP]...
<input type=hidden name="notification" value="susan.rook@idexpertscorp.com" />
<input type=hidden name="contactemail" value="susan.rook@idexpertscorp.com" />
...[SNIP]...

5.4. http://www2.idexpertscorp.com/js/hoverintent.js  previous  next

Summary

Severity:   Information
Confidence:   Certain
Host:   http://www2.idexpertscorp.com
Path:   /js/hoverintent.js

Issue detail

The following email address was disclosed in the response:

Request

GET /js/hoverintent.js HTTP/1.1
Host: www2.idexpertscorp.com
Proxy-Connection: keep-alive
Referer: http://www2.idexpertscorp.com/
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.60 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: ubvt=173.193.214.243.1304349963666894; exp_last_visit=989015581; exp_last_activity=1304375581; exp_tracker=a%3A1%3A%7Bi%3A0%3Bs%3A5%3A%22index%22%3B%7D; exp_super_search_history=797022

Response

HTTP/1.1 200 OK
Date: Mon, 02 May 2011 15:33:03 GMT
Server: Apache/2.2.3 (CentOS)
Last-Modified: Thu, 09 Sep 2010 19:23:30 GMT
ETag: "4c69abe-646-90aff080"
Accept-Ranges: bytes
Content-Length: 1606
Cache-Control: public
Expires: Sat, 07 May 2011 15:33:03 GMT
Content-Type: application/x-javascript

/**
* hoverIntent r5 // 2007.03.27 // jQuery 1.1.2+
* <http://cherne.net/brian/resources/jquery.hoverIntent.html>
*
* @param f onMouseOver function || An object with configuration options
* @param
...[SNIP]...
<brian@cherne.net>
...[SNIP]...

5.5. http://www2.idexpertscorp.com/js/innerfade.js  previous  next

Summary

Severity:   Information
Confidence:   Certain
Host:   http://www2.idexpertscorp.com
Path:   /js/innerfade.js

Issue detail

The following email address was disclosed in the response:

Request

GET /js/innerfade.js HTTP/1.1
Host: www2.idexpertscorp.com
Proxy-Connection: keep-alive
Referer: http://www2.idexpertscorp.com/
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.60 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: ubvt=173.193.214.243.1304349963666894; exp_last_visit=989015581; exp_last_activity=1304375581; exp_tracker=a%3A1%3A%7Bi%3A0%3Bs%3A5%3A%22index%22%3B%7D; exp_super_search_history=797022

Response

HTTP/1.1 200 OK
Date: Mon, 02 May 2011 15:33:04 GMT
Server: Apache/2.2.3 (CentOS)
Last-Modified: Mon, 02 Aug 2010 23:23:45 GMT
ETag: "4c6b02c-3da0-7deb2240"
Accept-Ranges: bytes
Content-Length: 15776
Cache-Control: public
Expires: Sat, 07 May 2011 15:33:04 GMT
Content-Type: application/x-javascript

/* =========================================================

// jquery.innerfade.js

// Datum: 2008-02-14
// Firma: Medienfreunde Hofmann & Baldes GbR
// Author: Torsten Baldes
// Mail: t.baldes@medienfreunde.com
// Web: http://medienfreunde.com

// based on the work of Matt Oakes http://portfolio.gizone.co.uk/applications/slideshow/
// and Ralf S. Engelschall http://trainofthoughts.org/

*
* <ul id=
...[SNIP]...

5.6. http://www2.idexpertscorp.com/page-not-found/  previous

Summary

Severity:   Information
Confidence:   Certain
Host:   http://www2.idexpertscorp.com
Path:   /page-not-found/

Issue detail

The following email address was disclosed in the response:

Request

GET /page-not-found/ HTTP/1.1
Accept: */*
Accept-Language: en-US
Accept-Encoding: gzip, deflate
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.1; WOW64; Trident/5.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 1.1.4322; .NET CLR 3.5.30729; .NET CLR 3.0.30729; .NET4.0C; .NET4.0E)
Proxy-Connection: Keep-Alive
Host: www2.idexpertscorp.com

Response

HTTP/1.1 200 OK
Date: Mon, 02 May 2011 15:45:24 GMT
Server: Apache/2.2.3 (CentOS)
X-Powered-By: PHP/5.2.6
Set-Cookie: exp_last_visit=989016324; expires=Tue, 01-May-2012 15:45:24 GMT; path=/
Set-Cookie: exp_last_activity=1304376324; expires=Tue, 01-May-2012 15:45:24 GMT; path=/
Set-Cookie: exp_tracker=a%3A1%3A%7Bi%3A0%3Bs%3A16%3A%22%2Fpage-not-found%2F%22%3B%7D; path=/
Set-Cookie: exp_super_search_history=813764; expires=Tue, 03-May-2011 15:47:09 GMT; path=/
Vary: Accept-Encoding
Cache-Control: public
Expires: Sat, 07 May 2011 15:45:24 GMT
imagetoolbar: no
Content-Type: text/html; charset=utf-8
Content-Length: 21076


<!DOCTYPE html>

<html>
<head>

<link rel="stylesheet" type="text/css" media="all" href="/css/base.css" />
<link rel="stylesheet" type="text/css" media="all" href="/css/type-image.css" />
<lin
...[SNIP]...
<input type=hidden name="notification" value="susan.rook@idexpertscorp.com" />
<input type=hidden name="contactemail" value="susan.rook@idexpertscorp.com" />
...[SNIP]...
<input type=hidden name="notification" value="susan.rook@idexpertscorp.com" />
<input type=hidden name="contactemail" value="susan.rook@idexpertscorp.com" />
...[SNIP]...

6. Robots.txt file  previous  next

Summary

Severity:   Information
Confidence:   Certain
Host:   http://www2.idexpertscorp.com
Path:   /

Issue detail

The web server contains a robots.txt file.

Issue background

The file robots.txt is used to give instructions to web robots, such as search engine crawlers, about locations within the web site which robots are allowed, or not allowed, to crawl and index.

The presence of the robots.txt does not in itself present any kind of security vulnerability. However, it is often used to identify restricted or private areas of a site's contents. The information in the file may therefore help an attacker to map out the site's contents, especially if some of the locations identified are not linked from elsewhere in the site. If the application relies on robots.txt to protect access to these areas, and does not enforce proper access control over them, then this presents a serious vulnerability.

Issue remediation

The robots.txt file is not itself a security threat, and its correct use can represent good practice for non-security reasons. You should not assume that all web robots will honour the file's instructions. Rather, assume that attackers will pay close attention to any locations identified in the file. Do not rely on robots.txt to provide any kind of protection over unauthorised access.

Request

GET /robots.txt HTTP/1.0
Host: www2.idexpertscorp.com

Response

HTTP/1.1 200 OK
Date: Mon, 02 May 2011 15:38:34 GMT
Server: Apache/2.2.3 (CentOS)
Last-Modified: Fri, 18 Mar 2011 00:53:23 GMT
ETag: "4a6b4ee-28-347306c0"
Accept-Ranges: bytes
Content-Length: 40
Cache-Control: public
Expires: Sat, 07 May 2011 15:38:34 GMT
Connection: close
Content-Type: text/plain

User-agent: *
Allow: /
Disallow: /brain/

7. Content type incorrectly stated  previous

Summary

Severity:   Information
Confidence:   Firm
Host:   http://www2.idexpertscorp.com
Path:   /favicon.ico

Issue detail

The response contains the following Content-type statement: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: www2.idexpertscorp.com
Proxy-Connection: keep-alive
Accept: */*
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/534.24 (KHTML, like Gecko) Chrome/11.0.696.60 Safari/534.24
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: ubvt=173.193.214.243.1304349963666894; exp_last_visit=989015581; exp_super_search_history=797022; __switchTo5x=58; __utmz=1.1304368386.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utmz=8236212.1304368386.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); PHPSESSID=jfnbk4r5pvilc331tug96gdad0; __unam=440469-12fb26a1110-5868adc8-4; __utma=1.843288026.1304368386.1304368386.1304368386.1; __utmc=1; __utmb=1.4.10.1304368386; __utma=8236212.1025446137.1304368386.1304368386.1304368386.1; __utmc=8236212; __utmb=8236212.4.10.1304368386; exp_last_activity=1304376082; exp_tracker=a%3A3%3A%7Bi%3A0%3Bs%3A6%3A%22%2Fblog%2F%22%3Bi%3A1%3Bs%3A9%3A%22%2Fcontact%2F%22%3Bi%3A2%3Bs%3A5%3A%22index%22%3B%7D

Response

HTTP/1.1 200 OK
Date: Mon, 02 May 2011 15:43:00 GMT
Server: Apache/2.2.3 (CentOS)
Last-Modified: Thu, 09 Sep 2010 21:35:24 GMT
ETag: "4a6b938-47e-6865ff00"
Accept-Ranges: bytes
Content-Length: 1150
Cache-Control: public
Expires: Sat, 07 May 2011 15:43:00 GMT
Content-Type: text/plain

............ .h.......(....... ..... .....@...#...#............P...P...P...P...G....c.......y..=...........................E..P...P...P...P...G....c.......x..E...........c3...u..........E..P...P...P
...[SNIP]...

Report generated by XSS.CX at Mon May 02 15:47:47 CDT 2011.