Overly Permissive Cross-Domain Policy File

A crossdomain.xml or clientaccesspolicy.xml file allows content from any domain to read the site's responses through browser plug-ins that are now obsolete.

SeverityLow
CVSS 3.13.1 CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:L/I:N/A:N Open in the calculator
CVSS 4.02.3 CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N Open in the calculator
CWECWE-942: Permissive Cross-domain Policy with Untrusted Domains
OWASP Top 10A02:2025 Security Misconfiguration
CategorySecurity Misconfiguration

Description

Adobe Flash Player and Microsoft Silverlight enforced their own cross-origin rules. Before content from one domain could read responses from another, the plug-in fetched a policy file from the target site: /crossdomain.xml for Flash, a format some other clients also adopted, and /clientaccesspolicy.xml for Silverlight. The site's policy file allows any domain, through an entry such as <allow-access-from domain="*" /> in crossdomain.xml or <domain uri="*" /> in clientaccesspolicy.xml, or it trusts a broad wildcard of domains.

Content hosted anywhere could then make requests to the site carrying the user's cookies and read the responses. For a user still running a client that honours the policy, a malicious site could read any content the user can access on the affected site, including personal data and anti-CSRF tokens, and so perform actions as the user. Both plug-ins have reached end of life and are not supported by current browsers, so the file has little practical effect for most users today and the realistic likelihood is low, although the impact is higher where specialised clients that honour the file are in use.

The finding remains worth reporting because it shows legacy configuration that has not been reviewed, because some older or specialised clients may still honour it, and because the same trust decisions are often repeated in other cross-origin settings. It is identified by requesting the two files from the site root and other directories and reviewing the domains they allow, and scanners report it from the presence of a wildcard entry.

Remediation

  • Delete crossdomain.xml and clientaccesspolicy.xml unless a supported client still needs them. Check the whole site, not just the root, and remove copies from other directories and from deployment templates.
  • Where a policy file must remain, list only specific trusted domains, never * or a broad wildcard, and do not allow request headers with a wildcard.
  • Send X-Permitted-Cross-Domain-Policies: none to tell clients that honour policy files not to use any on the site, or master-only where a single root policy is still needed.
  • Use CORS, with an explicit list of allowed origins, for any cross-origin access that current browsers need.
nginx: add_header X-Permitted-Cross-Domain-Policies "none" always; Apache httpd: Header always set X-Permitted-Cross-Domain-Policies "none" IIS (web.config, inside system.webServer): <httpProtocol> <customHeaders> <add name="X-Permitted-Cross-Domain-Policies" value="none" /> </customHeaders> </httpProtocol>

Confirm the fix by requesting both files and checking that they are no longer served.

References


Add This Finding to Your Library

In Pental this write-up is in Settings, Library. Add to my library copies it into your own, rated in your firm's CVSS version, ready to put in your own words.

Free trial  ·  No card required

Only need the reporting? Our reporting tool is free and open source, with the same library.


More Web Applications Findings

Every Web Applications finding