I took my exam the day after yours. Ran into the exact same problem. Enumerated just fine actually found the exploit for the 20 point box the first day. Just didn't try hard enough :-) came back to second day did the exact same exploit and got it to work. Probably 10 plus hours wasted on the exam. But at least I learned something hoping to schedule second exam around the 11th of November. Good luck! Will be following you
Glad I wasn't the only one who ran into the issue of "too much enumeration" lol. Probably around 10 hours wasted on the exam for me too. Good luck next time!
My lab time expired. I haven't done so many labs. 2:16 To be honest, enumeration scripts never actually helped me alot. Manytimes, I got good stuffs when I was doing manual enumeration. I believe we can do good when having a sweet ratio of both efforts (manual enum and script enum).
Hey Andy, I’ve been prepping for the exam myself and I just wanted to say thank you for taking the time to share your insights! Out of curiosity, in your last video, you mentioned that on the report, you have to include all your exploit code and any modifications you make to it. I was wondering wether that would be impractical since some exploits are incredibly long. Also, I find my images to be of different sizes/aspect ratios and they often make my final pdf doc look really…weird and roughly formatted. Do you have any advice/resources on creating a polished a report?
Hey Ansari, I thought of this long exploit thing. In that case, I think we can share link/resource of that exploit code. And share critical info exactly where we made changes in that exploit. That can be reverseIP and reversePORT. Sounds logical. You can check out John Hammond's OSCP report making video. I am using MarkDown to make report. I can can control size of images easily with right editing. I hope it gave you an idea.
According to the OSCP exam guide you need to include all the exploit code. Maybe just put it in the appendix. For the report, I plan to just stick with Word.
Got it! I’ve compiled a 111-page VHL report using markdown in vscode and then put it all together with that public script that uses pandoc. I found it to mostly work, but the control over nuanced formatting and small adjustments such as image resizing and seeing previews before generation to be quite limited. I’ll stick with word as well then…
Best of luck on your next attempt! I'm curious, was your path to gaining user on the 25 pointer something that was at least very similar to a box you had done in the past or was it something that required out of the box thinking? Also, I'm wondering if you've researched the ports/services of the 20 pointers on Google/HTB and whether that yielded any results.
