I have reached out to numerous people on this forum to help with getting the initial foothold and have tried all of their suggestions but without success. I starting to wonder if I am somehow being blocked from getting that initial foothold. If anyone is wiling to help me get through this please PM me. I promise I have exhausted all tips and tricks but still cannot get “connected”
Hum, weird, if you follow all tips, you should be ok
Stuck on elevation from i*** to C****. Any nudge appriciated - I know about wi**m service working locally, but don’t have any idea to connect to it with found creds. PS C*M is blocking me and downgrade is not an option.
Stuck on elevation from i*** to C****. Any nudge appriciated - I know about wi**m service working locally, but don’t have any idea to connect to it with found creds. PS C*M is blocking me and downgrade is not an option.
Think about a cmdlet that will allow you to call commands with the creds that you have
Guys please help me, i stucked root part. I create .c** file on my windows box. nc is listening, when i upload .c** file to C:\D**s directory i need to get admin shell but nothing happened. I tried 20-30 times
I have my foothold. Thanks to ShellInt0x80 I was able to get in. Also thanks to cyberafro, nando740, Michae1, Ad0n, MariaB and VbScrub for getting back to me in my desperate time of need.
Guys please help me, i stucked root part. I create .c** file on my windows box. nc is listening, when i upload .c** file to C:\D**s directory i need to get admin shell but nothing happened. I tried 20-30 times
If You tried 20-30 times with the same payload to get a shell back, try first using a more simple payload to confirm that you do have code execution. After confirming that check if you can get a shell back using nc
Guys please help me, i stucked root part. I create .c** file on my windows box. nc is listening, when i upload .c** file to C:\D**s directory i need to get admin shell but nothing happened. I tried 20-30 times
If You tried 20-30 times with the same payload to get a shell back, try first using a more simple payload to confirm that you do have code execution. After confirming that check if you can get a shell back using nc
I’m trying on my Windows box but cant get shell. Trying some payload codes but nothing…
So the first step - initial foothold - for this machine was quite pleasant. I can say the same for jumping to the user shell, because I learned few things. Root was CTFy.
Thanks to @Watskip and @cyberafro for help - much appreciated.
I have managed to get an Indian webshell using R**, but it is restricted and rather slow, so I am trying to get a more interactive one. However, I am unable to upload any files to the server as there are no write permissions on any folder I’ve looked in so far.
Am I on the right track, or is it possible to go from i*** to C**** using only that webshell?
I have managed to get an Indian webshell using R**, but it is restricted and rather slow, so I am trying to get a more interactive one. However, I am unable to upload any files to the server as there are no write permissions on any folder I’ve looked in so far.
Am I on the right track, or is it possible to go from i*** to C**** using only that webshell?
You’re on the right track, you can use the white wolf instead of the Indian
Rooted. Wow that took a long time but was wonderfully educational. Thanks @MinatoTW & @felamos!
Hints:
Foothold: Look around for something vulnerable to injection. Research how that works. Don’t use the tool in the packet, set it up yourself using the Indian for guidance then switch to the white wolf.
User: It’s possible to get a user shell using nothing but the white wolf. You have a command box and credentials, find the command you need, then use it to spawn the shell as a user.
Root: Look for interesting files when enumerating where you land. Open and you will see a response to something. Enumerate the system to find that something, then follow the instructions carefully. Many people on here are generating venomous payloads, this isn’t necessary; you can finish the job and get a shell without. Finishing the job may not require Windows but it is much easier on a Windows box.*
*If anyone managed to get around this on Linux, please PM me.
I’m confused during the root step, how did you find what type of the file in the D**s dictionary? Any hint, please? Yes ,I have read the .txt file, without any clue. Thanks!