Test RIA cross domain policy (OTG-CONFIG-008)

Brief Summary
Rich Internet Applications (RIA) have adopted Adobe's crossdomain.xml policy files in order to allow for controlled cross domain access to data and service consumption using technologies such as Oracle Java, Silverlight, and Adobe Flash. Therefore, a domain can grant remote access to its services from a different domain. However, often the policy files that describe the access restrictions are poorly configured. Poor configuration of the policy files enables Cross-site Request Forgery attacks, and may allow third parties to access sensitive data meant for the user.

HTML5 also incorporates a new way of performing cross domain requests: Cross Origin Resource Sharing (CORS). These can also be improperly configured and enable an attacker to perform similar attacks.

What are cross-domain policy files
A cross-domain policy file specifies the permissions that a web client such as Java, Adobe Flash, Adobe Reader, etc. to access data across different domains. For Silverlight, Microsoft adopted a subset of the Adobe's crossdomain.xml, and additionally created it's own cross-domain policy file: clientaccesspolicy.xml.

Whenever a web client detects that a resource has to be requested from other domain, it will first look for a policy file in the target domain in order to determine if performing cross-domain requests, including headers, and socket-based connections are allowed.

Master policy files are located at the domain's root. A client may be instructed to load a different policy file, however, it will always check the master policy file first to ensure that the master policy file permits the requested policy file.

Crossdomain.xml vs. Clientaccesspolicy.xml
Most RIA applications support crossdomain.xml. However in the case of Silverlight, it will only work if the crossdomain.xml specifies that access is allowed from any domain. For more granular control with Silverlight, clientaccesspolicy.xml must be used.

Policy files grant several types of permissions:
 * Accepted policy files (Master policy files can disable or restrict specific policy files)
 * Sockets permissions
 * Header permissions
 * HTTP/HTTPS access permissions
 * Allowing access based on cryptographic credentials

An example of an overly permissive policy file:  <!DOCTYPE cross-domain-policy SYSTEM "http://www.adobe.com/xml/dtds/cross-domain-policy.dtd">     

What is CORS
CORS is HTML5's way of enabling web applications to perform cross-domain requests. CORS works by appending an "Origin" header to the HTTP request, then the server responds with a "Access-Control-Allow-Origin" header stating which website can issue cross domain requests. The server may answer with the Access-Control-Allow-Origin header set to * to indicate that it is a public resource.

How can cross domain policies can be abused

 * Overly permissive cross-domain policies
 * Generating server responses that may be treated as cross-domain policy files
 * Using file upload functionality to upload files that may be treated as cross-domain policy files.
 * Being able to set custom response headers to indicate cross domain access. (Access-Control-Allow-Origin: *)

Impact of abusing cross-domain access

 * Defeat CSRF protections
 * Read data restricted or otherwise protected by cross-origin policies.

Black Box testing and example
Testing for RIA policy files weakness: In order to test for RIA policy file weakness you should try to retrieve the policy files crossdomain.xml and clientaccesspolicy.xml from the application's root, and from every folder found. For example, if the application's URL is http://www.owasp.org, you should try to download the files http://www.owasp.org/crossdomain.xml and http://www.owasp.org/clientaccesspolicy.xml. After retrieving all the policy files, the permissions allowed should be be checked under the least privilege principle. Requests should only come from the domains, ports, or protocols that are necessary. Overly permissive policies should be avoided. Policies with "*" in them should be closely examined. Example:   

Result Expected: A list of policy files found. A weak settings in the policies.

Testing for CORS policy weakness: Issue an OPTIONS request to the server with the following headers set: A request will then look like this: OPTIONS /resources/target HTTP/1.1 Host: example.com Connection: keep-alive Access-Control-Request-Method: POST Origin: http://owasp.org User-Agent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/536.5 (KHTML, like Gecko) Chrome/19.0.1084.9 Safari/536.5 Access-Control-Request-Headers: x-extraheader, content-type Accept: */* Referer: http://example.com/page.html Accept-Encoding: gzip,deflate,sdch Accept-Language: en-US,en;q=0.8,es;q=0.6
 * Origin: Origin can be any URL other than the website you are testing on or null.
 * Access-Control-Request-Method: This can be GET, POST, PUT, DELETE, etc. You should try with different values.
 * Access-Control-Request-Headers: This can be almost any request header. You should try to with sensitive headers. (This is optional)

A successful response would look like this: HTTP/1.1 200 OK Date: Thu, 13 Mar 2014 10:18:45 GMT Server: Apache Access-Control-Allow-Origin: http://example.com Access-Control-Allow-Methods: POST, GET, OPTIONS Access-Control-Allow-Headers: X-EXTRAHEADER, CONTENT-TYPE Access-Control-Max-Age: 1728000 Vary: Accept-Encoding Content-Encoding: gzip Content-Length: 20 Keep-Alive: timeout=2, max=100 Connection: Keep-Alive Content-Type: text/plain

You should carefully inspect the "Access-Control-Allow-Origin", "Access-Control-Allow-Methods", "Access-Control-Allow-Credentials", "Access-Control-Allow-Headers", "Access-Control-Allow-Expose-Headers", and any other header that starts with "Access-Control-Allow-". The value of each of this headers should be set to the most restrictive setting. For example a specific domain for "Access-Control-Allow-Origin".