@jh305 said:
One thing I haven’t seen anyone mention is how they get p*** onto the machine. wget doesn’t seem to work?!
In Linux, once you have SSH you can always use SCP for file transfer. Failing that, set up a mini web server on your machine and use wget/curl. Or even, just use nc and pipe it.
Ended up using SCP and learning something new, thanks!
Anyone give me a nudge on root for writeup. Running the p****4 script but not sure what I am looking for. Seen the ippsec LAZY video and understand the process but not sure how this translates to this host.
Anyone give me a nudge on root for writeup. Running the p****4 script but not sure what I am looking for. Seen the ippsec LAZY video and understand the process but not sure how this translates to this host.
You should check previous comments there are a lot of hints…
But here’s my hint: Focus on understanding what p****4 does, once you know what it does, try to use it for any task you do, “even the one you think is most obvious”, from there you just need to apply the logic by following the correct path.
User was skid level easy. Root was easy, but so convoluted, and not to mention confusing since a lot of comments in this thread are misleading. Not a big fan of this machine, I feel it should have been worth more than 20pts since root requires more thinking than just knowing the fundamentals, you have to really think outside the box. Plus without the forum this machine would be a brainfuck on VIP labs. I’ll give this machine a 3/5. Probably better for someone who isn’t a total newbie, but still hones in the fundamentals while forcing you to think creatively and like a sys admin. Some tips:
USER:
Do your fundamental recon, take notes on the tech used, google for the correct exploit and remember stuffing is not only for turkeys, sometimes its for credentials as well
ROOT:
Whew, laddie. I don’ t know where to start with this one. @illuminatiguy (page 6) gave the best advice here so far for root. So just go back and read his comments, not much more I can add, except that you’ll need to use two terminals and login and out of one while monitoring with the other.
Could someone PM me for a nudge on root? i know what i need to do with P**H and i used the tool p****4 but i can’t seem to find a writable dir.
EDIT:
Nevermind i finally got it!!! pretty good machine, root was fun but easy to fall in rabbit holes.
I’ve made it without using remote shells or anything pretty easy actually, PM me if someone who got it wants to share different methods.
Finally pwned user and root today (my first box!).
Thanks for the largely non-spoilery tips here guys, learned a lot. Could someone PM me the way they enumerated for user? I wouldn’t have figured it out if someone didn’t give too much of a hint on enumeration
To echo others:
user: enumeration is the key to starting, and once you later find the exploit, READ IT CAREFULLY; it does more than you thing and it will make your last run for this flag much simpler
root:
ippsec-lazy. he takes the time to run a couple examples of a trick for simple privesc. you just have to find the right path
rooted…thanks to @jkr and working the second half with @djdale3 it benefits us to work in pairs or even teams on some of these boxes, it makes a huge difference. I have no hints other than what’s allready been said on this forum.
For the exploit for user, should I be using the /w****** or the /w******/a**** path?
Focus on the /w****** path - find a tool that can help identify what the website is running (databases, language written in… etc…) then find which one of the services are vulnerable
if u check the source code of the /w******* page u actually dont need any tool for enumeration. though the tool may come handy in other machines … im too stuck on login page … searching the google got an exploit on /w*****/a**** but there also no luck. any help much appreciated
I’ll leave my mark on Root as it was the most difficult part for me.
What you want to use is a process monitor, the one told here was the best (p**y).
Once you get it to work, you may need to interact with it, maybe doing what you used to get here
You have to follow the PATH, even it keeps changing, so you will have to see how to make it not change, you should look for it if you are as lost as I was. IppSec’s Lazy Machine explained it very well, and documentation of PATH comes in handy.
Once you’ve done all of that, creating a file (in a writeable) called as what you’ve been monitoring all time should get you the reverse shell!
I hope all of this works to the person struggling with the box!
Thanks to @jkr for this amazing box! I’ve learned a lot of privesc