Summary
A Zigbee stack hands every received frame to a single function before doing anything else, which makes it a clean fuzzing entry point. The harness is thirty lines. The work that took time was triage: forty crashes collapsed into three root causes once I grouped them by the faulting instruction and the allocation site.
Background
Radio frames are attacker-controlled input that reaches the parser before any authentication, so bugs here are reachable by anyone in range.
Method
I built the parser as a standalone library with AddressSanitizer, wrote a harness that feeds the fuzzer’s buffer to the frame handler, and ran four AFL++ instances with a shared corpus seeded from captured frames.
Findings
Two crashes were out-of-bounds reads on a length field that was trusted before it was validated. The third was an integer underflow in the fragment reassembly code.
Takeaways
Minimise first, then group, then read. Triage by stack hash alone overcounts, and triage by crash site alone undercounts.