Windows Kernel Fuzzing

Recommendations

Info

<strong>Fuzzing</strong> Run 1. Fuzzer selects random test from catalog 2. Generates arguments by calling generate_arguments() 3. Serialises arguments according to type ( numbers, strings, handles, return buffer ) 4. Logs test name, arguments, procedure and thread 5. Executes test by calling run() Labs.mwrinfosecurity.com | © MWR Labs 18
Procedures • Execution of tests in different contexts – Threads, Callbacks, Window Procedures • “<strong>Kernel</strong> Attacks through User-Mode Callbacks” – Excellent paper by Tarjei Mandt Labs.mwrinfosecurity.com | © MWR Labs 19
Page 1 and 2: Windows Kernel Fuzzing Nils T2 Info
Page 3 and 4: Introduction - About me • Nils (@
Page 5 and 6: Introduction - Goals Labs.mwrinfose
Page 7 and 8: What are we trying to find? • CVE
Page 9 and 10: Fuzzer Design and Implementation La
Page 11 and 12: Implementation • Everything imple
Page 13 and 14: Test Catalog - Implementation • E
Page 15 and 16: Test Catalog - Example - Short Form
Page 17: Handle DB Handles are references to
Page 21 and 22: Procedures - User Mode Callbacks
Page 23 and 24: Logging t0:main:SC_NtGdiCreateMetaf
Page 25 and 26: Reproducing Testcases • We get: t
Page 27 and 28: Repro Run 1. Fuzzer selects current
Page 29 and 30: Architecture - Manager Labs.mwrinfo
Page 31 and 32: Manager - Scaling it up • First O
Page 33 and 34: Manager - Scaling it up Labs.mwrinf
Page 35 and 36: Cloud - Costs ¯\_(ツ)_/¯ Example
Page 37 and 38: Minimising Testcases - Divide & Con
Page 39 and 40: Distributed Minimising • Divide a
Page 41 and 42: Special Pool • Page heap or Addre
Page 43 and 44: Exception Handlers - DISCLAIMER •
Page 45 and 46: Fuzzing with Minidumps • Configur
Page 47 and 48: Results - 26 Bugs reported so far 1
Page 49 and 50: Future Work • Open source the fuz

Windows Kernel Fuzzing

Create successful ePaper yourself

Delete template?

Save as template?