Nmap http-cross-domain-policy NSE Script
This page contains detailed information about how to use the http-cross-domain-policy NSE script. For list of all NSE scripts, visit the Nmap NSE Library.
Script Overview
Script source code: https://github.com/nmap/nmap/tree/master/scripts/http-cross-domain-policy.nse
Script categories: safe, external, vuln
Target service / protocol: http, https
Target network port(s): 80, 443, 631, 7080, 8080, 8443, 8088, 5800, 3872, 8180, 8000
List of CVEs: -
Script Description
The http-cross-domain-policy.nse script checks the cross-domain policy file (/crossdomain.xml) and the client-acces-policy file (/clientaccesspolicy.xml) in web applications and lists the trusted domains. Overly permissive settings enable Cross Site Request Forgery attacks and may allow attackers to access sensitive data. This script is useful to detect permissive configurations and possible domain names available for purchase to exploit the application.
The script queries instantdomainsearch.com to lookup the domains. This functionality is turned off by default, to enable it set the script argument http-cross-domain-policy.domain-lookup.
References:
- http://sethsec.blogspot.com/2014/03/exploiting-misconfigured-crossdomainxml.html
- http://gursevkalra.blogspot.com/2013/08/bypassing-same-origin-policy-with-flash.html
- https://www.adobe.com/devnet/articles/crossdomain_policy_file_spec.html
- https://www.adobe.com/devnet-docs/acrobatetk/tools/AppSec/CrossDomain_PolicyFile_Specification.pdf
- https://www.owasp.org/index.php/Test_RIA_cross_domain_policy_%28OTG-CONFIG-008%29
- http://acunetix.com/vulnerabilities/web/insecure-clientaccesspolicy-xml-file
Http-cross-domain-policy NSE Script Arguments
This is a full list of arguments supported by the http-cross-domain-policy.nse script:
http-cross-domain-policy.domain-lookupBoolean to check domain availability. Default:false
smbdomainThe domain to log in with. If you aren't in a domain environment, then anything will (should?) be accepted by the server.
smbhashA password hash to use when logging in. This is given as a single hex string (32 characters) or a pair of hex strings (both 32 characters, optionally separated by a single character). These hashes are the LanMan or NTLM hash of the user's password, and are stored on disk or in memory. They can be retrieved from memory using the fgdump or pwdump tools.
smbnoguestUse to disable usage of the 'guest' account.
smbpasswordThe password to connect with. Be cautious with this, since some servers will lock accounts if the incorrect password is given. Although it's rare that the Administrator account can be locked out, in the off chance that it can, you could get yourself in trouble. To use a blank password, leave this parameter off altogether.
smbtypeThe type of SMB authentication to use. These are the possible options:
v1
: Sends LMv1 and NTLMv1.LMv1
: Sends LMv1 only.NTLMv1
: Sends NTLMv1 only (default).v2
: Sends LMv2 and NTLMv2.LMv2
: Sends LMv2 only.NTLMv2
: Doesn't exist; the protocol doesn't support NTLMv2 alone. The default,NTLMv1
, is a pretty decent compromise between security and compatibility. If you are paranoid, you might want to usev2
orlmv2
for this. (Actually, if you're paranoid, you should be avoiding this protocol altogether!). If you're using an extremely old system, you might need to set this tov1
orlm
, which are less secure but more compatible. For information, seesmbauth.lua
.
The SMB username to log in with. The forms "DOMAIN\username" and "username@DOMAIN" are not understood. To set a domain, use the smbdomain
argument.
Debug level at which default callbacks will print detailed parsing info. Default: 3
http.host
The value to use in the Host header of all requests unless otherwise set. By default, the Host header uses the output of stdnse.get_hostname()
.
Limit the received body to specific number of bytes. An oversized body results in an error unless script argument http.truncated-ok
or request option truncated_ok
is set to true. The default is 2097152 (2MB). Use value -1 to disable the limit altogether. This argument can be overridden case-by-case with request option max_body_size
.
The maximum memory size (in bytes) of the cache.
http.max-pipeline
If set, it represents the number of outstanding HTTP requests that should be sent together in a single burst. Defaults to http.pipeline
(if set), or to what function get_pipeline_limit
returns.
If set, it represents the number of HTTP requests that'll be sent on one connection. This can be set low to make debugging easier, or it can be set high to test how a server reacts (its chosen max is ignored).
http.truncated-ok
Do not treat oversized body as error. (Use response object flag truncated
to check if the returned body has been truncated.) This argument can be overridden case-by-case with request option truncated_ok
.
The value of the User-Agent header field sent with requests. By default it is "Mozilla/5.0 (compatible; Nmap Scripting Engine; https://nmap.org/book/nse.html)"
. A value of the empty string disables sending the User-Agent header field.
If set, vulnerabilities will be output in short format, a single line consisting of the host's target name or IP, the state, and either the CVE ID or the title of the vulnerability. Does not affect XML output.
vulns.showall
If set, the library will show and report all the registered vulnerabilities which includes the NOT VULNERABLE
ones. By default the library will only report the VULNERABLE
entries: VULNERABLE
, LIKELY VULNERABLE
, VULNERABLE (DoS)
and VULNERABLE (Exploitable)
. This argument affects the following functions: vulns.Report.make_output(): the default output function for portule/hostrule scripts. vulns.make_output(): the default output function for postrule scripts. vulns.format_vuln() and vulns.format_vuln_table() functions.
- - -
To use these script arguments, add them to the Nmap command line using the --script-args arg1=value,[arg2=value,..]
syntax. For example:
nmap --script=http-cross-domain-policy --script-args http-cross-domain-policy.domain-lookup=value,smbdomain=value <target>
Http-cross-domain-policy NSE Script Example Usage
Here's an example of how to use the http-cross-domain-policy.nse script:
nmap --script http-cross-domain-policy <target>
nmap -p 80 --script http-cross-domain-policy --script-args http-cross-domain-policy.domain-lookup=true <target>
Http-cross-domain-policy NSE Script Example Output
Here's a sample output from the http-cross-domain-policy.nse script:
PORT STATE SERVICE REASON
8080/tcp open http-proxy syn-ack
| http-cross-domain-policy:
| VULNERABLE:
| Cross-domain policy file (crossdomain.xml)
| State: VULNERABLE
| A cross-domain policy file specifies the permissions that a web client such as Java, Adobe Flash, Adobe Reader,
| etc. use to access data across different domains. A client acces policy file is similar to cross-domain policy
| but is used for M$ Silverlight applications. Overly permissive configurations enables Cross-site Request
| Forgery attacks, and may allow third parties to access sensitive data meant for the user.
| Check results:
| /crossdomain.xml:
| <cross-domain-policy>
| <allow-access-from domain="*.example.com"/>
| <allow-access-from domain="*.exampleobjects.com"/>
| <allow-access-from domain="*.example.co.in"/>'
| </cross-domain-policy>
| /clientaccesspolicy.xml:
| <?xml version="1.0" encoding="utf8"?>
| </accesspolicy>
| <crossdomainaccess>
| <policy>
| <allowfrom httprequestheaders="SOAPAction">
| <domain uri="*"/>
| <domain uri="*.example.me"/>
| <domain uri="*.exampleobjects.me"/>
| </allowfrom>
| <granto>
| <resource path="/" includesubpaths="true"/>
| </granto>
| </policy>
| </crossdomainaccess>
| </accesspolicy>
| Extra information:
| Trusted domains:example.com, exampleobjects.com, example.co.in, *, example.me, exampleobjects.me
| Use the script argument 'domain-lookup' to find trusted domains available for purchase
| References:
| http://gursevkalra.blogspot.com/2013/08/bypassing-same-origin-policy-with-flash.html
| http://sethsec.blogspot.com/2014/03/exploiting-misconfigured-crossdomainxml.html
| https://www.owasp.org/index.php/Test_RIA_cross_domain_policy_%28OTG-CONFIG-008%29
| http://acunetix.com/vulnerabilities/web/insecure-clientaccesspolicy-xml-file
| https://www.adobe.com/devnet-docs/acrobatetk/tools/AppSec/CrossDomain_PolicyFile_Specification.pdf
|_ https://www.adobe.com/devnet/articles/crossdomain_policy_file_spec.html
Http-cross-domain-policy NSE Script Example XML Output
Here's a sample XML output from the http-cross-domain-policy.nse script produced by providing the -oX <file>
Nmap option:
<elem key="title">Cross-domain and Client Access policies.</elem>
<elem key="state">VULNERABLE</elem>
<table key="description">
<elem>A cross-domain policy file specifies the permissions that a
web client such as Java, Adobe Flash, Adobe Reader, etc. use to
access data across different domains. A client acces policy file
is similar to cross-domain policy but is used for M$ Silverlight
applications. Overly permissive configurations enables Cross-site
Request Forgery attacks, and may allow third parties to access
sensitive data meant for the user.</elem>
</table>
<table key="check_results">
<table>
<elem key="name">/crossdomain.xml</elem>
<elem key="body"><cross-domain-policy>
<allow-access-from domain="*.example.com"/>
<allow-access-from domain="*.exampleobjects.com"/>
<allow-access-from domain="*.example.co.in"/>'
</cross-domain-policy></elem>
</table>
<table>
<elem key="name">/clientaccesspolicy.xml</elem>
<elem key="body"><?xml version="1.0" encoding="utf8"?>
</accesspolicy> <crossdomainaccess> <policy>
<allowfrom httprequestheaders="SOAPAction"> <domain
uri="*"/> <domain uri="*.example.me"/> <domain
uri="*.exampleobjects.me"/> </allowfrom> <granto>
<resource path="/" includesubpaths="true"/>
</granto> </policy> </crossdomainaccess>
</accesspolicy></elem>
</table>
</table>
<table key="extra_info">
<elem>Trusted domains:example.com, exampleobjects.com,
example.co.in, *, example.me, exampleobjects.me Use the script argument
'domain-lookup' to find trusted domains available for
purchase</elem>
</table>
<table key="refs">
<elem>
https://www.adobe.com/devnet/articles/crossdomain_policy_file_spec.html</elem>
<elem>
https://www.owasp.org/index.php/Test_RIA_cross_domain_policy_%28OTG-CONFIG-008%29</elem>
<elem>
http://sethsec.blogspot.com/2014/03/exploiting-misconfigured-crossdomainxml.html</elem>
<elem>
https://www.adobe.com/devnet-docs/acrobatetk/tools/AppSec/CrossDomain_PolicyFile_Specification.pdf</elem>
<elem>
http://acunetix.com/vulnerabilities/web/insecure-clientaccesspolicy-xml-file</elem>
<elem>
http://gursevkalra.blogspot.com/2013/08/bypassing-same-origin-policy-with-flash.html</elem>
</table>
Authors
- Seth Art <sethsec()gmail>
- Paulino Calderon <calderon()websec.mx>
- Gyanendra Mishra
References
- https://nmap.org/nsedoc/scripts/http-cross-domain-policy.html
- https://github.com/nmap/nmap/tree/master/scripts/http-cross-domain-policy.nse
- http://sethsec.blogspot.com/2014/03/exploiting-misconfigured-crossdomainxml.html
- http://gursevkalra.blogspot.com/2013/08/bypassing-same-origin-policy-with-flash.html
- https://www.adobe.com/devnet/articles/crossdomain_policy_file_spec.html
- https://www.adobe.com/devnet-docs/acrobatetk/tools/AppSec/CrossDomain_PolicyFile_Specification.pdf
- https://www.owasp.org/index.php/Test_RIA_cross_domain_policy_%28OTG-CONFIG-008%29
- http://acunetix.com/vulnerabilities/web/insecure-clientaccesspolicy-xml-file
- https://www.adobe.com/devnet/articles/crossdomain_policy_file_spec.html</elem>
- https://www.owasp.org/index.php/Test_RIA_cross_domain_policy_%28OTG-CONFIG-008%29</elem>
- http://sethsec.blogspot.com/2014/03/exploiting-misconfigured-crossdomainxml.html</elem>
- https://www.adobe.com/devnet-docs/acrobatetk/tools/AppSec/CrossDomain_PolicyFile_Specification.pdf</elem>
- http://acunetix.com/vulnerabilities/web/insecure-clientaccesspolicy-xml-file</elem>
- http://gursevkalra.blogspot.com/2013/08/bypassing-same-origin-policy-with-flash.html</elem>
See Also
Visit Nmap NSE Library for more scripts.
Version
This page has been created based on Nmap version 7.92.