recon · exploit · report

protocol1337

Security research, penetration-testing notes, and the occasional blue-team detour. Breaking things to understand them — then writing down how it actually worked.

// offense informs defense. both get documented here.

Latest: Methodical Linux Privilege Escalation: Enumerate First, Guess Never

~/engagements/target-01
guest@protocol1337:~$ rlwrap nc -lvnp 4444
Ncat: Listening on 0.0.0.0:4444
Ncat: Connection from 10.10.10.5:49231
[+] reverse shell caught
guest@protocol1337:~$ whoami
www-data
[*] enumerating local privileges…
[+] misconfiguration found
[+] shell upgraded → root
root@protocol1337:~# id
uid=0(root) gid=0(root) groups=0(root)
root@protocol1337:~# cat /root/notes.md
# write it down before you forget how you got in

Browse by topic

Tagged by domain. Pick an attack surface.

// whoami

Notes from both sides of the engagement

I spend my time finding the ways in — web app logic flaws, Active Directory misconfigurations, the privilege-escalation path everyone walked past. Mostly offense, because the fastest way to understand a system is to try to break it.

But the report is the point. This blog is where the engagement gets written down: the attacker mindset that connects findings into impact, the detections that would have caught it, and enough blue-team context to make the fix stick. Real methodology, lab-safe, no edgelord nonsense.

6
posts
red · blue
both sides
boxes to root