Postman

@c1cada hey man i rooted in 1 hours. the whole machine but there one issue! i think i did unintended wanna share how you rooted…

Spoiler Removed

someone plz pm me i am stuck in user need of help for privilege escalation??

I got creds for low user but not able to login anywhere, can anyone give a little push?

Type your comment> @cycl0ps said:

I got creds for low user but not able to login anywhere, can anyone give a little push?

Got in, I was messing with case. :smiley:

I’ve got access through r***s. I’ve discovered 4 potential attacks,

  1. webshell → not working (no write access)
  2. copy ss*-related file in home dir → not working (no access)
  3. inject cronjob → not working (no access)
  4. Master/Slave exec payload → not working (missing command MOD***)
    what i’m missing? is it one of the 4 options i discovered?
    Option 4 seemed the most promising to me. Ive worked through this thread, but as it seems i dont understand the breadcrumbs at all.

This is my first box. Managed to get user, but stuck getting root. Have been trying exploits in m*f on w***** with user credentials but unable to get a session. Would be grateful for a PM with any hints/nudges.

Got it! Overlooked an option. Thanks to @usernamestaken and @Lucyn .

ssh -i id_rsa r****@10.10.10.160
r****@10.10.10.160’s password:
Permission denied, please try again.
anyone can help? i input correctly but i can’t login

Stuck in the same place as @zikuto. Is it correct way to solve it? Or am I something missing here?

Type your comment> @d4rk5p07 said:

I’ve got access through r***s. I’ve discovered 4 potential attacks,

  1. webshell → not working (no write access)
  2. copy ss*-related file in home dir → not working (no access)
  3. inject cronjob → not working (no access)
  4. Master/Slave exec payload → not working (missing command MOD***)
    what i’m missing? is it one of the 4 options i discovered?
    Option 4 seemed the most promising to me. Ive worked through this thread, but as it seems i dont understand the breadcrumbs at all.

One of them works. Think about directory aspect again…

First machine and finally got root! Lessons learned and i thought it was a fun box !

I just rooted the box and have some questions about the initial foothold. The way that r**s is set up on the box, is that a normal setup? I was surprised how my attack actually worked.

Was able to decrypt the i*****.**k , although always getting “Connection closed by 10.10.10.160” , looking into the sshd config i can see that the user is actually denied to login via ssh, is this expected?

@tekkenpc said:
Was able to decrypt the i*****.**k , although always getting “Connection closed by 10.10.10.160” , looking into the sshd config i can see that the user is actually denied to login via ssh, is this expected?

I’ve been having a ton of overall issues connecting to the box lately so i don’t think you’re alone. not sure if anything has changed, but some others have been saying “keep trying til it works” :confused:

Type your comment> @nob0dy73 said:

I just rooted the box and have some questions about the initial foothold. The way that r**s is set up on the box, is that a normal setup? I was surprised how my attack actually worked.

There are more than one configuration items which bears the imprint of a CTF-like implementation. One of them is applying the DenyUser option in sshd_config, and an other one is using the command rename option in the r***s configuration file.

Purpose of these settings are exclusion of alternative solutions.

Type your comment> @passkwall said:

@tekkenpc said:
Was able to decrypt the i*****.**k , although always getting “Connection closed by 10.10.10.160” , looking into the sshd config i can see that the user is actually denied to login via ssh, is this expected?

I’ve been having a ton of overall issues connecting to the box lately so i don’t think you’re alone. not sure if anything has changed, but some others have been saying “keep trying til it works” :confused:

Let’s just say, if you’re already in one of the house’s rooms, don’t just walk out and ring the doorbell again.

Nice box, learned something new and yes, there are already more than enough hints in the previous comments. Special thanks to @TheCyberGeek

Type your comment> @bumika said:

Type your comment> @nob0dy73 said:

I just rooted the box and have some questions about the initial foothold. The way that r**s is set up on the box, is that a normal setup? I was surprised how my attack actually worked.

There are more than one configuration items which bears the imprint of a CTF-like implementation. One of them is applying the DenyUser option in sshd_config, and an other one is using the command rename option in the r***s configuration file.

Purpose of these settings are exclusion of alternative solutions.

So this would be atypical of how a default r**s would be setup? From my understanding of how the accounts for services should be setup, even in a testing environment, is that none of my attacks should have worked. I’m just curious if this is something you actually see in the wild.

Man I’m at a wall and I know it is going to be something stupid got user M*** and I know people are saying to go to the beginning but I must have missed something enumerating… Please PM! Great so far haha

Type your comment> @nob0dy73 said:

Type your comment> @bumika said:

Type your comment> @nob0dy73 said:

I just rooted the box and have some questions about the initial foothold. The way that r**s is set up on the box, is that a normal setup? I was surprised how my attack actually worked.

There are more than one configuration items which bears the imprint of a CTF-like implementation. One of them is applying the DenyUser option in sshd_config, and an other one is using the command rename option in the r***s configuration file.

Purpose of these settings are exclusion of alternative solutions.

So this would be atypical of how a default r**s would be setup? From my understanding of how the accounts for services should be setup, even in a testing environment, is that none of my attacks should have worked. I’m just curious if this is something you actually see in the wild.

I think several r***s services run as root and accessible without authentication in the wild. In that case all mentioned attacks can be successful.