Chatterbox

HTB Content Machines
#30

@CtrlEsc said:

@bulbafett said:
One port per second? I used -T5 on my nmap and had full scan done in ~ few mins. and Yes this machine is set to filter almost every port

At the outset, I tried the standard set of nmap scans, a full UDP scan and some staggered TCP scans. I got literally nothing, hence the netcat approach - slow and steady. Not sure what the heck is going on here.

What is our mantra? “Try Harder”. So I guess that is what I will do. :+1:

For a machine like this, I’d recommend doing a quick scan for any responding port then go back and actually try to enumerate any responding ports will save you a TON of time

#31

The design of the machine i awful. The required resets and unstable shells makes Chatterbox unpleasant experience. By my opinion the box should be fixed and activated again.

#32

I scan Triple time then found the open ports… :frowning:

#33

So I’ve located the vulnerable service and identified an exploit. I’m just having trouble with choosing the right payload, as the default option doesn’t seem to be working.

Is this now a process of elimination for choosing the correct windows payload, or is there more information around that would help? Have been stuck at this point for a few hours

#34

try allports

#35

Ok scratch that I found a payload that works. It’s just very unstable!

#36

maybe if it’s unstable, you should try a different payload.

#37

@ice2004 said:
The design of the machine i awful. The required resets and unstable shells makes Chatterbox unpleasant experience. By my opinion the box should be fixed and activated again.

agreed.

#38

can i dm somebody?

#39

@h4x3r said:
can i dm somebody?

ok :slight_smile:

#40

Having just spent most of my day trying to maintain a shell and get this box, I’ve noticed a thing or two so I’ll share my experience.
Some tips to try and maintain a shell without spoilers:

  1. Don’t try to spawn a Meterpreter shell straight up, spawn a normal shell that you can then upgrade to a Meterpreter shell. My gut feeling is a Meterpreter shell may step on itself when spawning which is why it continuously crashed (Not once did my standard shell crash). This has the added benefit of another session you can change to if things go badly.

  2. Try your exploit from a fresh reset of the machine.

  3. Make sure your exploit code is correct, there’s no point wasting your resets if you’re just hammering the box with gibberish.

#41

Priv esc?

#42

@ipatchcables said:
Priv esc?

For this box, you don’t necessarily need to Priv esc.

Read the other comments. Don’t over think this one.

#43

I guess I’m over thinking it then… spent most of the day trying to priv esc after getting a stable shell and user. Back to basics tomorrow.

#44

finally got it, dont kill yourself on priv esc, focus on the file itself

#45

Thanks for the hint, got it… and this is why I love HTB. Hours of researching various way to get to something can be used next time :smiley:

#46

My session keeps getting killed with error message Died from Errno::ECONNRESET before I can do anything. Is that because someone else is on the machine? I tried several payloads already. This one’s the only one that opened a session.

#47

@bianca said:
My session keeps getting killed with error message Died from Errno::ECONNRESET before I can do anything. Is that because someone else is on the machine? I tried several payloads already. This one’s the only one that opened a session.

Happened to me too, google up auto migrating meterpreter sessions. The exploit used will naturally close out the connection unless migrated

#48

I’m having an issue with formation of the payload. How to keep the payload under 730 bytes while avoiding the mentioned characters?

#49

@Kwicster said:

@bianca said:
My session keeps getting killed with error message Died from Errno::ECONNRESET before I can do anything. Is that because someone else is on the machine? I tried several payloads already. This one’s the only one that opened a session.

Happened to me too, google up auto migrating meterpreter sessions. The exploit used will naturally close out the connection unless migrated

Thanks! That did the trick :slight_smile: