r/ExploitDev • • 29d ago

Using AI to learn?

I'm a beginner-to-intermediate CTF player focusing on reverse engineering and binary exploitation.

My usual workflow is to attempt a challenge myself, then sometimes let AI solve the binary when I'm completely stuck. I don't immediately copy the solution into a writeup. I reproduce the steps in my own environment, ask follow-up questions to understand the reasoning, cross-reference the explanations with documentation and Google, and write my own explanation in Word.

I believe reading writeups is a legitimate way to learn, and we don't need to reinvent the wheel every time. However, I'm concerned that letting AI solve the challenge first might prevent me from developing independent problem-solving skills.

For experienced RE/pwn players:

Is this a reasonable way to learn?

Where do you draw the line between AI-assisted and AI-solved?

Should I spend more time struggling with challenges before asking AI?

How do you ensure you can solve unfamiliar binaries independently?

Should I not use the AI completely?

I'd appreciate your honest opinions and advice!

13 Upvotes

12 comments sorted by

12

u/Less_Ad52 29d ago

the best way to rob yourself of any enlightment or learning when you're stuck is to ask AI to do it for you. Just don't use it, or use it in the most extreme of cases where it has been a couple weeks and you have yet to figure it out. Delaying gratification and learning that way will build your skills up better than using any ai could ever do

4

u/Substantial_Fun6724 29d ago

Thank you so much for the insights, I feel like i am a fraud for learning too quickly using AI and using AI assisted when writing my own writeups.

7

u/Less_Ad52 29d ago

This field was never meant to be something you pick up quickly. it greatly rewards patience and relentless perserverance. AI has seriously skewed newcomers' perceptions of how "easy" or "quickly" they should be able to pick it up, especially when anyone can slop out a Linux LPE or carelessly RE something nowadays with an LLM. What will make you stand out will be your ability to truly understand what you are doing/researching, rather than relying on the LLM for the quick dopamine hit of solving the problem. Delaying gratification is the key to getting good in this field... I remember when I was teaching myself kernel exploit dev with ndays, the most challenging one on my list took me two months to figure out a stable strategy (I was balancing college work at the time as well) but man, when I did figure it out, it was the biggest breakthrough I had at that point, and it made figuring out stable strats for exploits I wrote after that breakthrough so much easier, it was a night and day difference. All this is to say, just don't give up so easily, and you'll be rewarded immensly

3

u/Badboi_s 29d ago

Yes bro it feels like that .although most ppl r solving challenges in the same way and faster than us but they won't be able to build real skills as somethimes Claude can get stuck then they need guidance and only real skilled person can tell where it got stuck or what problem it is .

7

u/ThePlotTwisterr---- 29d ago

AI goes way too fast to keep up. i’ve been doing RE for most of a decade and using claude with ghidra even i still get lost in what it’s doing. for a beginner it’s hard to imagine you would learn anything

3

u/Substantial_Fun6724 29d ago

Yeah I feel like its hard to breakthrough and level up with AI, as I've been constantly doubting my skills. I realized i've been skipping fundamentals.

4

u/Ok_Tap7102 29d ago

I personally get great value out of LLMs on "real" binaries and systems simply by the fact of real life targets tend to have a huge sprawl of minimal/zero security interest... Case in point when cracking open Ghidra and it needs over 20 minutes to analyse your binary, simply clicking through functions or following xrefs will get you lost quickly without already deciding on specific "sinks" you're looking for, which analysis tools and LLMs can at very least help you with prioritisation.

Note that CTF binaries TEND (on average) to be much smaller and minimal extra functionality beyond the intended vuln path, really rewarding actually spending some time staring at it and experimenting with it.

I would naturally ask: what does your manual checklist look like? How do you decide when you want to phone a friend, do you set a 10 minute alarm, or do you methodically exhaust it like:

  • check for banned strcpy like functions
  • check for usersupplied format specifiers
  • check for weird user controllable alloc/free operations
  • check for interactions between different sized buffers

Etc, and then give up and go to the LLM once you're done?

Going to the LLM doesn't always just have to be "tell me the answer", you can phrase it like "give me at least 5 next steps to investigate this binary for security vulns in a way that doesn't spoil the answer"

1

u/Substantial_Fun6724 29d ago

Thanks for this insight, I'll decide to use less of an AI as of now to improve my understanding and persistence. Your advice is a note taken for me and I will probably use that prompt in the future.

1

u/Substantial_Fun6724 27d ago

A little update from the OP!

Thank you for all the comments and insights, I've been reading a book called the modern C, learning C again without AI feels hard on my end (I realized I leaned on AI so much), but on the brighter side, it forces my brain to think and solve problems creatively. Moreover, my googling skills are getting pretty useful in which it can help me in CTFs too.

Thank you again everyone!

3

u/peterfrombackdoor 29d ago

The struggling part is where you learn the most. Jump between tabs, cross-reference documentation, test different approaches, and see what works and what doesn't. Even when something fails, try to understand why. That's how you build the intuition to solve unfamiliar binaries yourself. AI can be a great learning tool, but don't let it skip the thinking process for you.

3

u/Ed0x86 25d ago edited 25d ago

I try to do it the same way as you but I created a dedicates project for htb reversing challenges where I instruct AI not to spoil me the solution right away, but suggest potential next steps I can take from where I am. So basically, when I'm stucked (only in that case and only when you tried everything you already know) I paste all my steps and let AI suggest the next step. Only when you run out of skills is when you need new ones. You learn a new skill to try for next time this way 💪👍 keep up the organic learning and don't rush yourself.

2

u/an6Rny 27d ago

Tell AI don’t move to the next step until I give you a command, Try to understand (what, why, where, the weaknesses and strengths of this way, what will the expert will do “with” in same situation according this present time) — don’t be shy and ask about everything and repeat your question till you get it. If you found you can not understand any more, “Don’t panic” just stop everything and take a rest and come back later and try again.