mirror of
https://github.com/lwip-tcpip/lwip.git
synced 2024-12-29 03:14:04 +00:00
c2f9244137
Although ntohs and htons perform equivalent operations (a byte swap on little-endian platforms), their semantic roles (as implied by the names) are different. In fuzz_common.c, we get integers from simulated network packages, and convert them for host CPU use, so ntohs is the right variant to use. |
||
|---|---|---|
| .. | ||
| inputs | ||
| config.h | ||
| fuzz2.c | ||
| fuzz3.c | ||
| fuzz_common.c | ||
| fuzz_common.h | ||
| fuzz.c | ||
| lwipopts.h | ||
| Makefile | ||
| output_to_pcap.sh | ||
| README | ||
Fuzzing the lwIP stack (afl-fuzz requires linux/unix or similar) This directory contains small apps that read Ethernet frames from stdin and process them. They are used together with the 'american fuzzy lop' tool (found at https://lcamtuf.coredump.cx/afl/) or its successor AFL++ (https://github.com/AFLplusplus/AFLplusplus) and the sample inputs to test how unexpected inputs are handled. The afl tool will read the known inputs, and try to modify them to exercise as many code paths as possible, by instrumenting the code and keeping track of which code is executed. Just running make will produce the test programs. Then run afl with: afl-fuzz -i inputs/<INPUT> -o output ./lwip_fuzz and it should start working. It will probably complain about CPU scheduler, set AFL_SKIP_CPUFREQ=1 to ignore it. If it complains about invalid "/proc/sys/kernel/core_pattern" setting, try executing "sudo bash -c 'echo core > /proc/sys/kernel/core_pattern'". The input is split into different subdirectories since they test different parts of the code, and since you want to run one instance of afl-fuzz on each core. When afl finds a crash or a hang, the input that caused it will be placed in the output directory. If you have hexdump and text2pcap tools installed, running output_to_pcap.sh <outputdir> will create pcap files for each input file to simplify viewing in wireshark. The lwipopts.h file needs to have checksum checking off, otherwise almost every packet will be discarded because of that. The other options can be tuned to expose different parts of the code.