Traverxec

@jox said:
Type your comment> @gurbanli said:

Type your comment> @jox said:

If there were something go go on, I’d guess port knocking.

i think brute forcing ports is not good idea. 65535³ combination

No, without any input/inspiration on what to knock, that is not an option.

exactly… wtf is that - i had port 80 open for a few minutes and then it died again…

blooded

Got shell and creds but not sure where to use them.

Type your comment> @clubby789 said:

Got shell and creds but not sure where to use them.

Do you have port 80 open?

nope closed

US VIP 18 port 80 closed even after resets… great job at testing prior to deploying HTB…

trying to brute ssh?

@rholas said:

Type your comment> @clubby789 said:

Got shell and creds but not sure where to use them.

Do you have port 80 open?

It was open when I started, seems to have closed and dropped my shell. Wonder if other users are breaking it or if it’s meant to be like this

Well this sucks.

got the creds but can’t escalate to user

nah don’t bruteforce

TCP scan done, UDP scan done, bruteforce done…

I assume the port 80 being closed is a bug? Unless it was a knock there is no way first blood could have done that in 26m

@intninja said:

I assume the port 80 being closed is a bug? Unless it was a knock there is no way first blood could have done that in 26m

Port 80 is open on EU VIP 7 currently, so presuming a bug

port 80 n ssh should be open

port 80 is dying… i guess its a bug too

@Systolic said:

@intninja said:

I assume the port 80 being closed is a bug? Unless it was a knock there is no way first blood could have done that in 26m

Port 80 is open on EU VIP 7 currently, so presuming a bug

Yea. I am jumping between VIP servers and getting all closed. Guess I will hold off.

PSA: As soon as you get RCE, open an nc shell

I assume port 80 isn’t supposed to be closed? Just a bug?

Annoying that closed port 80 issue :s