Fighting with
“Fo********d port closed due to local error: Network error: Connection refused”
using p****k
Cannot understand why…
Chances are your machine is refusing a connection. The service which needs to be running isn’t normally on by default and you may have a firewall in the way.
I suppose there was something stuck with the “normal” port, or the service being hit by everyone!
I switched to another higher port and retried a few (many, indeed) times, and finally got root shell!
First day, first attempt at a box. Only mildly discouraged by everyone saying how easy this is :neutral:
I supposedly have RCE access via a php exploit I found, but not sure where to go from here. I can’t change directories, I can’t upload anything, and there’s nothing to run, but I am definitely in a file system as a user.
First day, first attempt at a box. Only mildly discouraged by everyone saying how easy this is :neutral:
I supposedly have RCE access via a php exploit I found, but not sure where to go from here. I can’t change directories, I can’t upload anything, and there’s nothing to run, but I am definitely in a file system as a user.
The exploit has tricked you a little bit by giving you what looks like a functional shell. You actually have a browser based RCE. Read the code of the exploit carefully and you can see the step the author got wrong in their instructions as well. Armed with this information you can build it to a real “shell” on the box.
Ok so looks like I may have been going down a rabbit hole trying to get a php rs uploaded… but probably doable with burp. Found a working exploit though and got user a minute after.
Extremely loved this box for its path to root. Those who are unaware/ scared / have not learned that part, its highly recommended (at by me) to do it first locally and then on actual machine.
My Hints:
User:
You may stuck in rabbit hole. I did. Be careful. Nothing much is required. Read all pages carefully, Google accordingly. You will find it easily.
Understand the difference between (Reverse) Shell and RCE
Root:
You will easily find an exe. Google it.
Do it manually on you machine first. Once you are confident, do it on actual machine.
Yes there are tools to convert script to (windows) executable
This was a fun, easy box with an opportunity to learn a few things from. There are a couple of rabbit holes that may catch you, I spent way too much time on one of them.
User:
There are certain pages that you should always check first because they provide information or a way in, this box was no different.
Google is your friend (If you’re searching verbatim what you found on the box, Google might show you something a little different)
Find out what you can do with the foothold in, then make it better with a common tool
Root:
This is where it can get extremely frustrating. I knew what needed to be done quickly, but I didn’t know how to do it. I’ve done this kind of “workaround” before, but never with windows.
ENUMERATE!!! There are two places to find the vulnerability (one will show you it’s on the system the other will show you if it’s running).
Google is still your friend
You can use the original way in (user step 3) with this exploit to get admin (no metasploit needed).
does anyone have an issue running an exploit where the issue is:
ImportError: No module named colorama ?
I’ve reinstalled this module over and over but the exploit still can’t seem to find the module.
Did you install it for the right Python version?
I had it once that I installed a module for python using pip(2), but never noticed that the script was running with python3
does anyone have an issue running an exploit where the issue is:
ImportError: No module named colorama ?
I’ve reinstalled this module over and over but the exploit still can’t seem to find the module.
This might be an issue between python2 and python3. If you’ve installed the module into python2 and are running the exploit with 3, it might never be able to find it (and no amount of pip install colorama will solve it.
If you are on Kali there have been issues in the past where some modules end up causing nightmares.
If all else fails you can remove it from the exploit - its only really there to make the output look pretty and lots of people get misled into thinking its a shell rather than an RCE because of this.