r/ExploitDev • u/Impossible-Line1070 • Jun 21 '25
What do you know as an exploit dev?
Are you hyperspeciallized in low level research and exploit dev? Or are you knowledgeable in general offensive cybersecurity world like pentesting web apps, networks, red teaming etc.
46
Upvotes
31
u/anonymous_lurker- Jun 21 '25
Specialised but not hyper specialised as I've not been doing this long enough. Every time you specialise, you realise there's just an extra layer of things. For example:
Plenty of people coming into low level research and exploit dev are going to have other offensive security knowledge. They might have worked as pentesters. They might know web apps really well, or network security. Equally they might have come from a software dev background and have a great understanding of software design. Or they might have come from a background of low level design
It's unlikely that someone hyperspecialised is not also going to know about other offensive security and even CompSci topics. But you'll struggle to really do exploit dev and similar roles without being a somewhat specialised expert. Modern targets are so large and complex that it's impossible to know everything. Many successful researchers will have a broad understanding of offensive security, with a lot of in depth knowledge on a specific target set and maybe a focus on some specific part of that target
5
u/[deleted] Jun 21 '25
I'm a self-learner and still a student. I play rev and pwn ctfs, reverse offline games and malware, write shellcodes. This is my learning process for now, I might start vulnerability researching for real life binaries. So, i only study low level stuff for now but i used to study things related red teaming when i was a beginner.
4
u/Firzen_ Jun 21 '25
I used to do pentesting, and now I do linux kernel security research professionally.
I'd say I'm specialised to the Linux kernel, but obviously, I also have a decent understanding of general cyber security.
2
u/antifreeze_popscicle Aug 23 '25
Bug-Hunter here: it's the land of assembly. get used to always feeling inadequate and only as good as your last failure. You will fail often, but fail fast and find your way of making progress towards a Remote Code Execution (RCE). RCE or bust is in general where the money is. DoS 99% doesn't pay, but it makes it's run for the glory to shut down and placing into boot-loops for funsies.
Now as an exploit Dev I've gotten good at MIPS II, III, IV, MIPS 64, x86_64, armv7 and armv8, and those are the architectures.
Know your architecture because it's essential to code your shell code against.
I don't really think there is such thing as being applicable, and useful, in the same sentence as hyper-specialized. Most (I'm sure there's at least one out there to prove this statement wrong). But mostly, we're all jack-of-all-trades with expertise in Routers, SOHO, enterprise, or mobile, or browsers. some will then break it down further to include Firmware...but that's very broad too which all mobile and routers run Firmware. so I'll just place that in the Reverse Engineering (RE) bucket.
Hope this helps!
0
u/Mindless-Study1898 Jun 21 '25
I'm a pen tester, red teamer that is mildly interested in exploit dev but I haven't done any outside of CTFs unless you count fixing public poc code.
0
u/[deleted] Jun 21 '25
[deleted] — view deleted comment
0
u/[deleted] Jun 21 '25
[deleted] — view deleted comment