Development

There are already a number of protocol fuzzers that work perfectly well. If we’re going to create a new one, to avoid building a “me too” project, it will need to offer something that others don’t. Given that many existing fuzzers run from the command line, we aim to differentiate ProtoFuzz with the following goals:

• Intuitive. Use of ProtoFuzz should not require a long learning curve. An end user should be able to figure out the basics of the tool without wrestling with a manual or remembering convoluted command-line options.

• Ease of use. ProtoFuzz should be immediately functional once it’s started. Rather than require that the user build cumbersome templates to define the structure of a data packet, we’ll leverage the structure of previously captured data packets to build fuzzing templates.

• Access to all protocol layers. Some network fuzzers focus on data within the packet as opposed to the protocol headers themselves. ProtoFuzz should be able to fuzz any and all portions of a packet from the Ethernet header down to the TCP/UDP data.