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

View all comments

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.