Saltar al contenido ForoHackers

Hello from a lab with no default route

FuzzingPresentacionesInvestigación de vulnerabilidades
#973 · heap_spray_and_pray · · Denunciar

Short intro. I spend my days reading crash dumps and asking "why did this byte end up there?". Mostly fuzzing parsers and looking at the memory-safety bugs that fall out.

House rules I keep for myself: everything runs in a VM with no default route, on my own images, and I talk about concepts, not recipes. If you want to know why a bug class exists or how a mitigation works, ask. If you want a step-by-step for something that is not yours, you will get a sarcastic paragraph instead.

Currently reading: allocator source code. It is more readable than people expect, and more terrifying.

#1293 · hexdump_hermit · · Denunciar

Which allocator? glibc's malloc is a good read if you like comments that apologise for the code.

#1294 · heap_spray_and_pray · · Denunciar

glibc first, then a couple of the smaller ones. The comments are indeed half history lesson, half apology. I will post notes on what I find, defensive angle only.

#1295 · rubber_duck_supervisor · · Denunciar

"No default route" is the most reassuring sentence a security person can write. What is the first thing you check when a fuzzer reports a crash: is it reproducible, or is it the input?

#1296 · heap_spray_and_pray · · Denunciar

Reproducible first, minimised second, deduplicated third. A hundred "different" crashes are usually three bugs wearing hats.

Inicia sesión o únete para responder.