Nmap and google are your best friends here, get the software version and search for known vuln and eventually you will find the right article
You may encounter some dependency issue, if you do use g*****-r**** c****** instead of r**** c******
User:
Enumerate, there are some pretty good scripts out there. Read the output carefully. if you can’t crack it, you can change it. Don’t forget to reset the machine if you choose to change it
Root:
More enumeration, there is a very interesting file read what it does and manipulate
Feel free to PM for nudges and to remove if too many spoiler
Can someone please help me … ?. I stuck for many days
I got a reverse shell (highly unstable one), but it’s just a dumb shell and there is nothing much I can do with that, I have tried several ways to upgrade to a full interactive shell but I have no luck with that. I need help to move forward
It kind of depends on what you mean by “dumb shell” vs “full interactive.”
If you can issue commands on the filesystem, read folder contents etc., then you have a shell good enough to find the information you need to get a stable shell on the box.
@TazWake The connection is highly unstable (keep getting 502 error), I tried several ways to get a more stable shell but so far no luck …
If you’ve leveraged the G***** vulnerabilities to obtain a shell, have a think about where you actually are. The “unstable” nature of the shell you’re talking about is - for me at least - a result of what it is you’ve actually landed a shell in.
As TazWake said though, don’t worry about trying to improve the quality of the shell, it’ll be sufficient. Just work out what you’re in and enumerate until you find a way out.
Got stuck in the process, can anyone give me a nudge in the right direction?
Found the G***** page
Started a reverse shell via g*****_***.py
Got a user g++ (added the plus instead of *, cause it changed it to bold)
Found out i’m in a c***r (probably dr)
Looked for the manual online for G*****
Found a user d***** with a command, the connection lost again
Started a new reverse shell via g*****_***.py
Tried to follow the instructions to G***** D++s Sy - H++ 2 r+++t **** pd (used the + symbol instead of * because of the markdown bold and italic options)
Did not get any feedback after following the instruction from the official documentation as mentioned in step 8…
So I was thinking, my reverse shell is not correct, or I am doing something wrong with following the instruction from the official documentation. Or another way is there to break out the freaking thing
Official discussion thread for Laboratory. Please do not post any spoilers or big hints.
Hi, I have the root ssh private key, id_rsa and autorized_keys. But i just cant get a ssh connection going?! Kinda stuck if anyone could give some advice I would really appreciate it.
I got a reverse shell and have given myself admin in the G***b and found the privkey , but I’m getting Load key "***": invalid format despite file saying it’s OpenSSH private key
Is the privkey a red herring or am I doing something wrong with it? Just looking for a small hint.
EDIT: hmm well I managed to get it to work… but I have no idea why the step that I did was needed
I got a reverse shell and have given myself admin in the G***b and found the privkey , but I’m getting Load key "***": invalid format despite file saying it’s OpenSSH private key
Is the privkey a red herring or am I doing something wrong with it? Just looking for a small hint.
EDIT: hmm well I managed to get it to work… but I have no idea why the step that I did was needed
Let me guess: You had to add a newline to the end of the file? For some reason, certain ssh clients require the key file to end with an empty line.
Rooted! I was able to gain foothold without spinning up my own thing, I found a R*** module and imported it into a framework and got rce that way. Getting user was new to me - and took me too long before getting it. Root was okay, did a little bit of RE in Ghidra and after that, owning the box was easy.
Initial Foothold
Others are saying they started their own instance of what’s running - I didn’t go down this road. I did a bit of research and found an exploit that I could import into a framework and after that, got a shell. Great, on the box.
User
This took me forever when it was right in front of me. Half my problem was I have never heard of this particular tool (look at where you land after getting a shell). Once I got a basic understanding and knew what I could do to someone, I am in as that person. He has a very sensitive file laying about - can you find it? Once you do, you will know what to do in order to get user. Go get your flag!
Root
This was pretty easy for me once I found it. Your off-the-shelf enum scripts should pick this up, but wont stick out with pretty colors. This kind of file is easily exploited if the person isn’t careful - you need to be absolutely, not relatively, sure what you’re doing when making these. I opened this thing in the NSAs favorite tool and right away found the way in. A little file here, adding it there, and running it and boom, popped root.
I can understand peoples frustrations around the difficulty of the box. From one side, it was beginning to lean on the medium side while at the same time being just within the easy marks.
I am not able to register a user with G******, I’m using the correct domain extension with email, however…I get an actual 422 error. Reset box numerous time now
I am not able to register a user with G******, I’m using the correct domain extension with email, however…I get an actual 422 error. Reset box numerous time now
I dont remember having this issue but I do remember it took a long time for all the services to spin up, waiting 5-10 minutes after a reset.
In general, on HTB if one reset doesn’t solve it, there is a good chance resetting the box will never solve it. Repeated resets, especially on a box with slow services, just makes the problem worse.
If two resets doesn’t solve the problem then consider one of the following:
Your approach is incorrect and you need to rethink it
You need to raise a helpdesk ticket (which can take 24+ hours to resolve)
MY GOD, all those 502, 422 and 429 errors made this machine 10 times harder than it should.
Because I was getting a strange 422 error when I attempted to register a user, I went down a rabbit hole and with no cool drugs to make the trip worthwhile, only my ever-increasing rage and frustration to help me power through.
I tried to brute force a user and that, of course, got me banned
After that I went on a graphql site seen trip, only to find out that I just needed to register regularly half a day later …
I thought that I was going to lose my mind with this machine, but then I found a french-omelette-cheese-recipe in the ■■■■ Gitlab and I knew that it had already happened.
Cherry on top, another user put the same root payload in the same place that mine at the right time to mind f*ck me one last time.
Ahhh this is going to leave a mental scar; I’ll probably get an eye twitch every time I see a Gitlab from now on.
Any way, jokes aside, I got root. PM if you need help. The tips here helped me a lot.
