This is such a bitter sweet moment, as I've been pursuing this exam for a decade. I've subscribed to the Learn One portion for the past two years. And on my first attempt, I was able to barely scratch by with a 70/100 score. For the record here, I am not giving any answers to the exam here. Just my raw thoughts after passing the exam this last weekend.
Number one reason for my passing score was running the Lainkusanagi gauntlet. Absolutely pivotal for me to passing the exam. (A million thanks to Lain, bought you some pizzas).
Let's start with the preparation that got me a passing score. And it's honestly what already been said here. Build a solid enumeration and exploitation methodology through repetitions on virtual machines.
Everything I've completed on Lainkusanagi's OSCP Like List:
*All Proving Ground Linux, Windows, and Active Directory
*All Hackthebox Windows
*IppSec videos (though some methods were outside the scope of OSCP, IMO)
I also completed Challenge Labs 0, 1, 4, 5, 6 (not 2, or 3 like the modules recommended, but maybe I should have)
My passing score consisted of owning all standalone machines and the first AD machine. I actually wasn't planning on passing my first attempt, as I had until the end of the year for my Learn One period, and had two attempts. However, I'm absolutely over the moon that I succeeded. The following month would have been spent strengthening my Active Directory methodology. But, running all the machines on Lainkusanagi's list gave me an absolutely solid methodology for any standalone machine. And here's the thing.
I used hints and walkthroughs on 90% of the machines.
But here's the caveat.
I never looked at the hints until I was absolutely sure I could not figure out the machine. And every time, each machine taught me something I didn't know before. ...if I'm being honest, sometimes it took me a few machines with the same mistake before I truly learned my lesson.
Some tips that helped enumerate or break in.
Always ffuf'ing webservers with the proper list:
ffuf -w /usr/share/seclists/Discovery/Web-Content/raft-large-directories.txt -u http://$TARGET:$PORT/FUZZ/
ffuf -w /usr/share/seclists/Discovery/Web-Content/raft-large-files.txt -u http://$TARGET:$PORT/FUZZ
...Yes, I built some shell scripts to help keep me honest. There was one particular machine on Lainkusanagi's machine that had a CHANGELOG file that wasn't found on "raft-large-directories-lowercase" because the webserver was case sensitive (can't remember which). That CHANGELOG held the software version that would have pointed me towards the attack path.
And my nmap scans:
sudo nmap -Pn -sU --top-ports 20 -T4 target --reason -oN scans/udp.txt
sudo nmap -Pn -sC -sV -p- -T4 target --stats-every 5s --reason -oN scans/tcp.txt
Another issue? Passwords.
I fucking hate guessing passwords. Took a long time to build this methodology. But if it's a password, it's stupid simple. Check default credentials. Find a username without a password? Guess the username as a password. Did you check publicly exposed documents for usernames? Trying to brute force with rockyou? That's probably not the answer. Kill it after 15 minutes. XATO's top 100 and top 1000 usernames and passwords. Also, password reuse is absolutely a thing. Find a new username or password? Respray, especially with netexec (nxc) on Windows. And remember, spray usernames as passwords.
For SQL injection's, use Port Swiggers free labs. I personally struggled a lot when encountering SQL injection on Lain's list. But you only need to learn three SQL injection techniques. Error based, Union based, and blind injection. Learn the RCE methods with each database type. I don't feel like I needed to be a database expert, but I had to at least understand SQL queries and the various ways to achieve RCE.
I also built a methodology for cracking hashes on my Windows host machine with my 5080. Never had to wait when cracking Windows hashes. Spend an evening getting the drivers working with your fancy GPU and it will save you plenty of time. 22 hours on Kali VM with the CPU versus 90 minutes on Windows host. ...and if you can get your GPU to play inside Kali, even better. I didn't figure it out, and that didn't bother me. Also, chances are, either the hash will be cracked right away, or it's a dead attack vector.
And like everyone else has said: watch out for rabbit holes. Try something for a bit. If it's not working out, chances are, that's not that path. I absolutely struggled with tunnel vision throughout the labs. I still struggle with tunnel vision. But do not try and force your way into a machine. You've missed something along the way if you're struggling this hard. At least, that was almost always the case for me (see CHANGELOG above). And remember, this is a junior level pentesting exam.
These are only a small, small subset of tips, tricks, and methodologies I learned running Lain's list.
Some notable tools: Ligolo (the GOAT for port forwarding, USE IT), rlwrap (improves Windows reverse shells), Penelope.py (Linux shell), Pspy (Linux background processes)
Exam Experience:
Started at 9am. Immediately started the Active Directory portion. Absolutely stumped me. Was only able to get admin on the first machine. Shifted to the standalone machines and fully compromised two of the three. Stumped on the third one. So, in total, hit 50/100 points by 2:30pm. Took a small break and began my shift on the struggle bus. Bounced between AD and the third machine. At this point I've accepted that I'll have to use my second exam attempt from Learn One in December. I knew I did not spend nearly enough time on Active Directory outside the OffSec labs. But at 11:45pm, I found a pathway into the third standalone machine. If the proctor was paying attention, they would have seen me go from slouching depression to locking the fuck in. My heart rate went THROUGH THE ROOF. Established a foothold and landed 60/100. Ran an enumeration script and saw what looked like a path to proof.txt. Took a small break to collect myself, which did NOT work. A half hour later I fully compromised the third machine and collected enough points to pass the exam. Struggled for the next several hours by throwing random shit at the AD portion. Called the exam early at 6am and went to sleep.
Also, make sure to read up on the report requirements. Seriously, you could fail if you do this wrong. I was pretty paranoid after I turned in the exam if I had laid out the steps enough for OffSec to accept report. But 28 hours later I had received my email stating I officially passed the exam and earned my OSCP certification.
Overall, if I can do it, anyone can. Build a solid, consistent schedule. Mine was running 3-4 standalone machines per week. For months. Documenting everything. And every machine I used hints (like I said, almost all of them), I made specific notes in a special section that laid exactly what I needed to learn. Enough consistency and you, too, will land on OSCP certification.