PentesterLab (@PentesterLab) header
PentesterLab (@PentesterLab) profile picture

Don’t just learn tools and payloads. Learn why vulnerabilities exist. Hands-on web hacking, security code review, and real-world CVE labs.

Melbourne, Victoria
Joined December 2011
Photo by PentesterLab (@PentesterLab)Photo by PentesterLab (@PentesterLab)Photo by PentesterLab (@PentesterLab)Photo by PentesterLab (@PentesterLab)Photo by PentesterLab (@PentesterLab)Photo by PentesterLab (@PentesterLab)Photo by PentesterLab (@PentesterLab)Photo by PentesterLab (@PentesterLab)Photo by PentesterLab (@PentesterLab)Photo by PentesterLab (@PentesterLab)
We recently came across this snippet as part of our CVE review process What would you flag during a security code review?
11
2,119
PentesterLab retweeted
I just completed @Pentesterlab's Recon Badge!!!
1
1
6
900
Why use ../../ when ../ is enough... The check looks reasonable: /../ means someone is walking up the path, let's return a 404! But do you really need ../../: request $page verdict --------------------------------------------------------- /static/../../../𝗲𝘁𝗰/𝗽𝗮𝘀𝘀𝘄𝗱   ../../../𝗲𝘁𝗰/𝗽𝗮𝘀𝘀𝘄𝗱 BLOCKED /static/../munin.conf ../munin.conf PASSES The first / gets consumed by the first regular expression, so $page is ../munin.conf and doesn't contain /../ but it still allows you to get what matters... Sometimes, you don't need a full directory traversal... just one directory up is all it takes.
1
11
54
5,434
PentesterLab retweeted
Threat modeling badge !
All the labs in our threat modelling badge are now available! We built this badge around practical, high leverage skills that help you spot potential threats and ask better security questions when designing, developing or using AI to build your next application. pentesterlab.com/badges/thre…
1
1
889
All the labs in our threat modelling badge are now available! We built this badge around practical, high leverage skills that help you spot potential threats and ask better security questions when designing, developing or using AI to build your next application. pentesterlab.com/badges/thre…
4
1
34
4,490
Stranger Strings. Some inputs open doors to another dimension. Others open a reverse shell. Which one scares you more?
1
1
13
2,235
Sometimes, doing code review is just as easy as playing spot the difference... Two handlers, same file, 40 lines apart. Same auth decorator, so both need a valid login. Both read current_user_id. Both read group_id from the request body. One asks whether you're allowed to see that group. One doesn't. You don't need to have in-depth understanding of Python, authorisation logic or code review. You just need the right idea: "Are all those functions checking the same thing, if not, what is the security impact?" CVE-2026-121552
4
4
18
2,801
PentesterLab retweeted
I just completed @Pentesterlab's Recon Badge!!! unto the next
1
2
860
A Go bug put the private key inside the certificate, in clear text (CVE-2025-6224). The culprit: h.Sum(key) doesn't hash key. It appends the hash of nothing to key. pentesterlab.com/training/on…
1
2
24
2,804
PentesterLab retweeted
Watching DEFCON talks, I heard about PentesterLab and decided to give it a try. Coming from HTB and THM, I found it way more educational. The labs are realistic and quick, but the code review videos are the real game changer for understanding API workflows behind the scenes.
5
3
1
34
3,389
If you're wanting to level up your code review skills, I would highly recommend @PentesterLab's on demand training, I've completed the training and the amount of information covered is insane and you learn techniques from an industry veteran @snyff. pentesterlab.com/training/
3
15
1,434
Would you rather only be allowed to pentest using Nikto, or only be allowed to pentest Perl applications?
5
10
6,360
If you use a whole package for one small helper, consider the updates, maintenance and trust you take on. Removing unused functionality or replacing a tiny helper with simpler, tested code you can maintain may be worthwhile. pentesterlab.com/blog/brace-…
10
2,187
Remember: the codebase you're reviewing is alive, and it won't stop changing just because you're taking notes. When documenting a potential vulnerability, don't record only the filename and line number. Code moves, code changes, files get renamed, and your reference might point to something completely different by the time someone reads your findings. Always keep the filename, line number, commit hash, and a copy of the relevant code, along with an explanation of the issue. If you include a link, make sure it points to that specific commit, not to the branch. Your notes should still make sense after the code has changed.
1
4
15
3,090
PentesterLab retweeted
I just completed @Pentesterlab's Serialize Badge!!!
1
2
1,173
PentesterLab retweeted
I just completed @Pentesterlab's Java Deserialization Badge!!!
1
1
3
1,986
Java gotcha: concatenating a null reference doesn't throw. It becomes the four characters "null". In Tomcat's digest authentication, a missing user's password became "null" (CVE-2026-43512). When code hashes a lookup result, look for the null check. pentesterlab.com/training/on…
2
14
2,964
Say "we don’t validate signatures" again. I dare you. I double dare you.
2
5
60
4,363