Abstract
<jats:p>This paper examines fuzz testing of MAVLink-oriented telemetry and command modules in unmanned aerial vehicle (UAV) control systems implemented in Rust. The aim of the study is to develop a reproducible approach to analyzing such modules and to provide a quantitative comparison of cargo fuzz and cargo afl. For the experiment, four test targets were implemented: a frame reception and validation module, a telemetry message routing module, a command processing module, and a combined structured processing pipeline. Six-hundred-second fuzz-testing campaigns were conducted for each test target under identical experimental conditions. The results showed that the average execution speed of cargo fuzz was 22,759.5 exec/s, whereas for cargo afl it was 2,506.1 exec/s. At the same time, cargo afl produced a larger cumulative test corpus: 18,764 input samples versus 5,192 for cargo fuzz. Within the selected time budget, no crashes, hangs, or semantic errors were detected. The practical significance of the study lies in determining the suitability of two fuzzing engines for analyzing MAVLink-oriented UAV modules and in establishing a foundation for further long-duration testing campaigns. Key words: AFL++, cargo afl, cargo fuzz, MAVLink, Rust, UAV, command modules, telemetry modules, fuzz testing.</jats:p>