SAP /sap/bc/soap/rfc SOAP Service RFC_PING Function Service Discovery - Metasploit
This page contains detailed information about how to use the auxiliary/scanner/sap/sap_soap_rfc_ping metasploit module. For list of all metasploit modules, visit the Metasploit Module Library.
Module Overview
Name: SAP /sap/bc/soap/rfc SOAP Service RFC_PING Function Service Discovery
Module: auxiliary/scanner/sap/sap_soap_rfc_ping
Source code: modules/auxiliary/scanner/sap/sap_soap_rfc_ping.rb
Disclosure date: -
Last modification time: 2017-07-24 06:26:21 +0000
Supported architecture(s): -
Supported platform(s): -
Target service / protocol: http, https
Target network port(s): 80, 443, 3000, 8000, 8008, 8080, 8443, 8880, 8888
List of CVEs: -
This module makes use of the RFC_PING function, through the /sap/bc/soap/rfc SOAP service, to test connectivity to remote RFC destinations.
Module Ranking and Traits
Module Ranking:
- normal: The exploit is otherwise reliable, but depends on a specific version and can't (or doesn't) reliably autodetect. More information about ranking can be found here.
Basic Usage
This module is a scanner module, and is capable of testing against multiple hosts.
msf > use auxiliary/scanner/sap/sap_soap_rfc_ping
msf auxiliary(sap_soap_rfc_ping) > show options
... show and set options ...
msf auxiliary(sap_soap_rfc_ping) > set RHOSTS ip-range
msf auxiliary(sap_soap_rfc_ping) > exploit
Other examples of setting the RHOSTS option:
Example 1:
msf auxiliary(sap_soap_rfc_ping) > set RHOSTS 192.168.1.3-192.168.1.200
Example 2:
msf auxiliary(sap_soap_rfc_ping) > set RHOSTS 192.168.1.1/24
Example 3:
msf auxiliary(sap_soap_rfc_ping) > set RHOSTS file:/tmp/ip_list.txt
Required Options
- RHOSTS: The target host(s), range CIDR identifier, or hosts file with syntax 'file:<path>'
Go back to menu.
Msfconsole Usage
Here is how the scanner/sap/sap_soap_rfc_ping auxiliary module looks in the msfconsole:
msf6 > use auxiliary/scanner/sap/sap_soap_rfc_ping
msf6 auxiliary(scanner/sap/sap_soap_rfc_ping) > show info
Name: SAP /sap/bc/soap/rfc SOAP Service RFC_PING Function Service Discovery
Module: auxiliary/scanner/sap/sap_soap_rfc_ping
License: Metasploit Framework License (BSD)
Rank: Normal
Provided by:
Agnivesh Sathasivam
nmonkee
Check supported:
No
Basic options:
Name Current Setting Required Description
---- --------------- -------- -----------
CLIENT 001 yes Client
HttpPassword 06071992 yes Password
HttpUsername SAP* yes Username
Proxies no A proxy chain of format type:host:port[,type:host:port][...]
RHOSTS yes The target host(s), range CIDR identifier, or hosts file with syntax 'file:<path>'
RPORT 8000 yes The target port (TCP)
SSL false no Negotiate SSL/TLS for outgoing connections
THREADS 1 yes The number of concurrent threads (max one per host)
VHOST no HTTP server virtual host
Description:
This module makes use of the RFC_PING function, through the
/sap/bc/soap/rfc SOAP service, to test connectivity to remote RFC
destinations.
References:
http://labs.mwrinfosecurity.com/tools/2012/04/27/sap-metasploit-modules/
Module Options
This is a complete list of options available in the scanner/sap/sap_soap_rfc_ping auxiliary module:
msf6 auxiliary(scanner/sap/sap_soap_rfc_ping) > show options
Module options (auxiliary/scanner/sap/sap_soap_rfc_ping):
Name Current Setting Required Description
---- --------------- -------- -----------
CLIENT 001 yes Client
HttpPassword 06071992 yes Password
HttpUsername SAP* yes Username
Proxies no A proxy chain of format type:host:port[,type:host:port][...]
RHOSTS yes The target host(s), range CIDR identifier, or hosts file with syntax 'file:<path>'
RPORT 8000 yes The target port (TCP)
SSL false no Negotiate SSL/TLS for outgoing connections
THREADS 1 yes The number of concurrent threads (max one per host)
VHOST no HTTP server virtual host
Advanced Options
Here is a complete list of advanced options supported by the scanner/sap/sap_soap_rfc_ping auxiliary module:
msf6 auxiliary(scanner/sap/sap_soap_rfc_ping) > show advanced
Module advanced options (auxiliary/scanner/sap/sap_soap_rfc_ping):
Name Current Setting Required Description
---- --------------- -------- -----------
DOMAIN WORKSTATION yes The domain to use for Windows authentication
DigestAuthIIS true no Conform to IIS, should work for most servers. Only set to false for non-IIS servers
FingerprintCheck true no Conduct a pre-exploit fingerprint verification
HttpClientTimeout no HTTP connection and receive timeout
HttpRawHeaders no Path to ERB-templatized raw headers to append to existing headers
HttpTrace false no Show the raw HTTP requests and responses
HttpTraceColors red/blu no HTTP request and response colors for HttpTrace (unset to disable)
HttpTraceHeadersOnly false no Show HTTP headers only in HttpTrace
SSLVersion Auto yes Specify the version of SSL/TLS to be used (Auto, TLS and SSL23 are auto-negotiate) (Accepted: Auto, TLS, SSL23, SSL3, TLS1, TLS1.1, TLS1.2)
ShowProgress true yes Display progress messages during a scan
ShowProgressPercent 10 yes The interval in percent that progress should be shown
UserAgent Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1) no The User-Agent header to use for all requests
VERBOSE false no Enable detailed status messages
WORKSPACE no Specify the workspace for this module
Auxiliary Actions
This is a list of all auxiliary actions that the scanner/sap/sap_soap_rfc_ping module can do:
msf6 auxiliary(scanner/sap/sap_soap_rfc_ping) > show actions
Auxiliary actions:
Name Description
---- -----------
Evasion Options
Here is the full list of possible evasion options supported by the scanner/sap/sap_soap_rfc_ping auxiliary module in order to evade defenses (e.g. Antivirus, EDR, Firewall, NIDS etc.):
msf6 auxiliary(scanner/sap/sap_soap_rfc_ping) > show evasion
Module evasion options:
Name Current Setting Required Description
---- --------------- -------- -----------
HTTP::header_folding false no Enable folding of HTTP headers
HTTP::method_random_case false no Use random casing for the HTTP method
HTTP::method_random_invalid false no Use a random invalid, HTTP method for request
HTTP::method_random_valid false no Use a random, but valid, HTTP method for request
HTTP::pad_fake_headers false no Insert random, fake headers into the HTTP request
HTTP::pad_fake_headers_count 0 no How many fake headers to insert into the HTTP request
HTTP::pad_get_params false no Insert random, fake query string variables into the request
HTTP::pad_get_params_count 16 no How many fake query string variables to insert into the request
HTTP::pad_method_uri_count 1 no How many whitespace characters to use between the method and uri
HTTP::pad_method_uri_type space no What type of whitespace to use between the method and uri (Accepted: space, tab, apache)
HTTP::pad_post_params false no Insert random, fake post variables into the request
HTTP::pad_post_params_count 16 no How many fake post variables to insert into the request
HTTP::pad_uri_version_count 1 no How many whitespace characters to use between the uri and version
HTTP::pad_uri_version_type space no What type of whitespace to use between the uri and version (Accepted: space, tab, apache)
HTTP::uri_dir_fake_relative false no Insert fake relative directories into the uri
HTTP::uri_dir_self_reference false no Insert self-referential directories into the uri
HTTP::uri_encode_mode hex-normal no Enable URI encoding (Accepted: none, hex-normal, hex-noslashes, hex-random, hex-all, u-normal, u-all, u-random)
HTTP::uri_fake_end false no Add a fake end of URI (eg: /%20HTTP/1.0/../../)
HTTP::uri_fake_params_start false no Add a fake start of params to the URI (eg: /%3fa=b/../)
HTTP::uri_full_url false no Use the full URL for all HTTP requests
HTTP::uri_use_backslashes false no Use back slashes instead of forward slashes in the uri
HTTP::version_random_invalid false no Use a random invalid, HTTP version for request
HTTP::version_random_valid false no Use a random, but valid, HTTP version for request
Go back to menu.
Error Messages
This module may fail with the following error messages:
Check for the possible causes from the code snippets below found in the module source code. This can often times help in identifying the root cause of the problem.
[SAP] <IP>:<RPORT> - login failed!
Here is a relevant code snippet related to the "[SAP] <IP>:<RPORT> - login failed!" error message:
74: 'sap-language' => 'EN'
75: }
76: })
77: if res and res.code != 500 and res.code != 200
78: if res and res.body =~ /<h1>Logon failed<\/h1>/
79: print_error("[SAP] #{ip}:#{rport} - login failed!")
80: else
81: print_error("[SAP] #{ip}:#{rport} - something went wrong!")
82: end
83: return
84: elsif res and res.body =~ /Response/
[SAP] <IP>:<RPORT> - something went wrong!
Here is a relevant code snippet related to the "[SAP] <IP>:<RPORT> - something went wrong!" error message:
76: })
77: if res and res.code != 500 and res.code != 200
78: if res and res.body =~ /<h1>Logon failed<\/h1>/
79: print_error("[SAP] #{ip}:#{rport} - login failed!")
80: else
81: print_error("[SAP] #{ip}:#{rport} - something went wrong!")
82: end
83: return
84: elsif res and res.body =~ /Response/
85: print_good("[SAP] #{ip}:#{rport} - RFC service is alive")
86: report_note(
[SAP] <IP>:<RPORT> - RFC service is not alive
Here is a relevant code snippet related to the "[SAP] <IP>:<RPORT> - RFC service is not alive" error message:
91: :type => 'sap.services.available',
92: :data => "The Remote Function Call (RFC) Service is available through the SOAP service."
93: )
94: return
95: else
96: print_status("[SAP] #{ip}:#{rport} - RFC service is not alive")
97: return
98: end
99: rescue ::Rex::ConnectionError
100: print_error("[SAP] #{ip}:#{rport} - Unable to connect")
101: return
[SAP] <IP>:<RPORT> - Unable to connect
Here is a relevant code snippet related to the "[SAP] <IP>:<RPORT> - Unable to connect" error message:
94: return
95: else
96: print_status("[SAP] #{ip}:#{rport} - RFC service is not alive")
97: return
98: end
99: rescue ::Rex::ConnectionError
100: print_error("[SAP] #{ip}:#{rport} - Unable to connect")
101: return
102: end
103: end
104: end
Go back to menu.
Related Pull Requests
- #8716 Merged Pull Request: Print_Status -> Print_Good (And OCD bits 'n bobs)
- #8338 Merged Pull Request: Fix msf/core and self.class msftidy warnings
- #6921 Merged Pull Request: Fix #4885, Support basic and form auth at the same time
- #6655 Merged Pull Request: use MetasploitModule as a class name
- #6648 Merged Pull Request: Change metasploit class names
- #5181 Merged Pull Request: Fix #5103, Revert unwanted URI encoding
- #3391 Merged Pull Request: Resolved all msftidy vars_get warnings
- #2597 Merged Pull Request: chmod -x .rb files without #! in modules and lib
- #2525 Merged Pull Request: Change module boilerplate
- #1786 Merged Pull Request: Fix SAP modules, mainly to make a better use of send_request_cgi
- #1031 Merged Pull Request: Calls the RFC_PING RFC module via SOAP
References
See Also
Check also the following modules related to this module:
- auxiliary/admin/sap/cve_2020_6207_solman_rce
- auxiliary/admin/sap/cve_2020_6287_ws_add_user
- auxiliary/admin/sap/sap_configservlet_exec_noauth
- auxiliary/admin/sap/sap_igs_xmlchart_xxe
- auxiliary/admin/sap/sap_mgmt_con_osexec
- auxiliary/dos/sap/sap_soap_rfc_eps_delete_file
- auxiliary/scanner/sap/sap_ctc_verb_tampering_user_mgmt
- auxiliary/scanner/sap/sap_hostctrl_getcomputersystem
- auxiliary/scanner/sap/sap_icf_public_info
- auxiliary/scanner/sap/sap_icm_urlscan
- auxiliary/scanner/sap/sap_mgmt_con_abaplog
- auxiliary/scanner/sap/sap_mgmt_con_brute_login
- auxiliary/scanner/sap/sap_mgmt_con_extractusers
- auxiliary/scanner/sap/sap_mgmt_con_getaccesspoints
- auxiliary/scanner/sap/sap_mgmt_con_getenv
- auxiliary/scanner/sap/sap_mgmt_con_getlogfiles
- auxiliary/scanner/sap/sap_mgmt_con_getprocesslist
- auxiliary/scanner/sap/sap_mgmt_con_getprocessparameter
- auxiliary/scanner/sap/sap_mgmt_con_instanceproperties
- auxiliary/scanner/sap/sap_mgmt_con_listconfigfiles
- auxiliary/scanner/sap/sap_mgmt_con_listlogfiles
- auxiliary/scanner/sap/sap_mgmt_con_startprofile
- auxiliary/scanner/sap/sap_mgmt_con_version
- auxiliary/scanner/sap/sap_router_info_request
- auxiliary/scanner/sap/sap_router_portscanner
- auxiliary/scanner/sap/sap_service_discovery
- auxiliary/scanner/sap/sap_smb_relay
- auxiliary/scanner/sap/sap_soap_bapi_user_create1
- auxiliary/scanner/sap/sap_soap_rfc_brute_login
- auxiliary/scanner/sap/sap_soap_rfc_dbmcli_sxpg_call_system_command_exec
- auxiliary/scanner/sap/sap_soap_rfc_dbmcli_sxpg_command_exec
- auxiliary/scanner/sap/sap_soap_rfc_eps_get_directory_listing
- auxiliary/scanner/sap/sap_soap_rfc_pfl_check_os_file_existence
- auxiliary/scanner/sap/sap_soap_rfc_read_table
- auxiliary/scanner/sap/sap_soap_rfc_rzl_read_dir
- auxiliary/scanner/sap/sap_soap_rfc_susr_rfc_user_interface
- auxiliary/scanner/sap/sap_soap_rfc_sxpg_call_system_exec
- auxiliary/scanner/sap/sap_soap_rfc_sxpg_command_exec
- auxiliary/scanner/sap/sap_soap_rfc_system_info
- auxiliary/scanner/sap/sap_soap_th_saprel_disclosure
- auxiliary/scanner/sap/sap_web_gui_brute_login
- exploit/multi/sap/cve_2020_6207_solman_rs
- exploit/multi/sap/sap_mgmt_con_osexec_payload
- exploit/multi/sap/sap_soap_rfc_sxpg_call_system_exec
- exploit/multi/sap/sap_soap_rfc_sxpg_command_exec
- post/multi/sap/smdagent_get_properties
- auxiliary/admin/http/netgear_soap_password_extractor
- auxiliary/admin/upnp/soap_portmapping
- auxiliary/scanner/http/soap_xml
- exploit/freebsd/misc/citrix_netscaler_soap_bof
- exploit/linux/http/apache_ofbiz_deserialization_soap
- exploit/linux/ids/alienvault_centerd_soap_exec
- exploit/linux/upnp/miniupnpd_soap_bof
- exploit/multi/http/ibm_openadmin_tool_soap_welcomeserver_exec
- exploit/multi/http/vtiger_soap_upload
- exploit/multi/misc/indesign_server_soap
- auxiliary/scanner/http/rfcode_reader_enum
- auxiliary/scanner/discovery/ipv6_multicast_ping
- auxiliary/scanner/mssql/mssql_ping
- auxiliary/scanner/nessus/nessus_xmlrpc_ping
- auxiliary/scanner/http/epmp1000_ping_cmd_exec
- auxiliary/scanner/http/wordpress_pingback_access
Authors
- Agnivesh Sathasivam
- nmonkee
Version
This page has been produced using Metasploit Framework version 6.1.27-dev. For more modules, visit the Metasploit Module Library.
Go back to menu.