intel / intel/tsffs

Similar testcases while fuzzing platform bios

Open
#101 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
Rust
Stars
331
Forks
26
Avg merge
1d 5h
Merged PRs (30d)
2

Description

The fuzzing process for example 5.3 "Fuzzing a platform BIOS" **started successfully**:
![tsffs_starts](https://github.com/user-attachments/assets/d4e59133-926b-4319-b0ca-3173882115e9)

I expected to see the bugs added in example after some time. I left the fuzzer running for a while and the logs are as follows:
![logs_2_0](https://github.com/user-attachments/assets/a11272e2-db53-49d2-a70e-e87e91fb867b)

The first thing that confused me is **exec/sec: 0.000**.
I tried to use different data in corpus, but specifically in this case I used 7 different bmp images. So the second thing that is confusing is that the fuzzer used only two input images (only 2 were created in the corpus) and then nothing happened over time
![new_corpus](https://github.com/user-attachments/assets/e6f5cb88-8979-4f58-801a-80817137f187)

After that, I stopped the fuzzer and started it again (I did not delete those 2 pictures in the corpus). And in this case **exec/sec: is not 0.000**
![second_time_start_fuzz](https://github.com/user-attachments/assets/e11be13e-7a66-409b-b3d0-012ffed76c6a)

next, I repeated the previous iterations but at the **logging level 4**. I left only 7 test bmp images and run a fuzzer with a logging level 4. As you can see, testcases are the same
![logs4_firststart](https://github.com/user-attachments/assets/50bef330-5014-4c08-8d7d-31811df69514)

After that, I restarted the fuzzer (there are 2 additional images in the case from the previous start). In the following logs, you can see that the size of the testcases is different, but the data is the same:
![logs4_secondstart](https://github.com/user-attachments/assets/28df4669-a1c5-4785-bfa9-abf42fba3480)

And as a result, it is not possible to find the added bugs, the solutions folder is empty

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.