ttdennis /fpicker
fpicker is a Frida-based fuzzing suite supporting various modes (including AFL++ in-process fuzzing)
★ 299⑂ 34👁 10⑃ 10● 36▤ 0
299
stars
34
forks
10
watchers
10
prs
36
issues
0
releases
README
fpicker
fpicker is a Frida-based fuzzing suite that offers a variety of fuzzing modes for in-process
fuzzing, such as an AFL++ mode or a passive tracing mode. It should run on all platforms that
are supported by Frida.
Installation Instructions
Building and Running
Creating a Fuzzing Harness
Modes and Configuration
Some background information and the thoughts and ideas behind fpicker can be found in a
blogpost I wrote.
Fpicker is based on previous efforts on ToothPicker,
which was developed during my master thesis. Most of fpicker was developed during working hours at
my employer (ERNW).
Requirements and Installation
Required for running fpicker:
- frida_compile to compile the harness script into one JS file
- The frida-core-devkit for the respective platform found at Frida releases on GitHub.
- Depending on the platform you want to target store the library as libfrida-core-ios.a, libfrida-core-macos.a, or libfrida-core-linux.a.
- The same goes for the header files (frida-core.h). Store them as frida-core-linux.h or frida-core-ios.h depending on the platform.
- The makefile was built this way so you can build for different systems on the same system (e.g., your host system and the phone).
- If you prefer to use a specific version, adjust the Makefile accordingly.
- To update to the latest version, simply run update_frida_version.sh before building.
Required only when running in AFL++ mode:
- AFL++
- on macOS:
- Compile with CFLAGS="-DUSEMMAP=1".
- on iOS:
- Compile with CFLAGS="-DUSEMMAP=1 -DTARGET_OS_IOS".
Building and Running
Fpicker can be built for macOS, iOS or Linux. The Makefile currently only supports building
for iOS on macOS but it should be totally possible to build fpicker using an iOS toolchain on
Linux.
Depending on the desired target run:
bash
make fpicker-macos
make fpicker-ios
make fpicker-linux
to build fpicker.
Once fpicker is built, the fuzzing harness needs to be built next:
See the examples folder for different sample fuzzing cases. The general approach is as follows:
- Create a custom harness for the target (e.g. examples/test/test.js) (see
here for more information on harnesses)
- Compile the custom harness using frida-compile frida-compile test.js -o harness.js
Now fpicker can start fuzzing. The exact command highly depends on the configuration and setup. In
the following, a few example cases are given. These mostly correspond to the examples in the
examples folder.
- Run fpicker as AFL++ proxy attaching to a target process fuzzing a specific function in process:
bash
afl-fuzz -i examples/test-network/in -o ./examples/test-network/out -- \\
./fpicker --fuzzer-mode afl -e attach -p test-network -f ./examples/test-network/harness.js
- Run fpicker in standalone mode attaching to a server and running a client program to send the fuzzing input:
bash
./fpicker --fuzzer-mode standalone -e attach -p server-process -f harness.js --input-mode cmd \\
--cTop issues
#28Failed the examples/test on MACOS while using AFL++ mode as the README.md requires.6 comments · 2023-09-07#23unable to find method 'prepare'4 comments · 2023-03-28#18javascript issues3 comments · 2022-06-30#38Unable to find method 'prepare' (#23)2 comments · 2025-01-21#30Fpicker instrumentation hangs in AFL proxy mode2 comments · 2023-10-09#42Unable to run the fpicker fuzzer succesfully on protocol_example1 comments · 2025-02-27#40Unable to resolve1 comments · 2025-02-24#25The AFL test failed1 comments · 2023-04-15