Skip to content
AI Security

Interview question · Systems, OS & Memory Safety

A fuzzer found a memory-corruption crash in a parser. How do you decide how exploitable and how severe it is?

'It's just a crash' and 'mitigations are on' are the two answers that get candidates marked down. The scored answer separates the primitive, the reachability and the privilege, and treats a read bug as half of an exploit.

hardNewPreparation tags: Google, Microsoft, AppleUpdated Nov 2026

'It's just a crash' and 'mitigations are on' are the two answers that get candidates marked down. The scored answer separates the primitive, the reachability and the privilege, and treats a read bug as half of an exploit.

Make your first attempt

What would you say before reading the answer?

  1. 01 State the assumptions your answer depends on.
  2. 02 Explain the mechanism and choose a control.
  3. 03 Name a condition that would change your decision.

The worked answer includes an approach, scoring criteria and follow-up questions. Compare the reasoning with your own.

10 answers per topic instead of 5, plus saved progress and bookmarks · costs nothingor unlock all 529 remaining answers · $25

Every worked answer in all 17 topics, every lesson in every course, the full concept curriculum, the complete practice-test bank, and the downloadable security field guides.

6 months · One payment · No auto-renewal

What if · the follow-ups in this answer

The answer works through 6 follow-ups like an interviewer would

A bug report shows a function returns uninitialised stack memory to the caller in a network-facing service.

  1. Which three questions decide severity?
  2. Why can an information leak be serious?
  3. How does reachability change things?
  4. What does the process hold?
  5. How do you fix and prevent it?
  6. How would you assess and fix the bug?

Each rung has a nudge, a model answer, the principle that carries over and the weak answer to avoid. Premium opens every answer and ladder.

UP NEXT ON YOUR JOURNEY
Next in this trackAs a staff engineer, how would you reduce memory-safety risk in a large C++ codebase that cannot be rewritten?Next in this trackHow does coverage-guided fuzzing work, how do you write a good fuzz harness, and what do you do with the crashes?Next in this trackStatic versus dynamic analysis in reverse engineering: what do disassemblers, decompilers and debuggers each show you?
DISCUSSION · 0

No comments yet. Share a correction or a different way to answer it.