-
Notifications
You must be signed in to change notification settings - Fork 40
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
tfuzz did not consider cannot-renamed programs #14
Comments
When preparing the fuzzing environment, why don't you rename the binary to tic, solving the problem by setting up the environment instead of changing tfuzz? (Changing tfuzz to observe and keep the filename is somewhat harder, it would be easier to simply rename the binaries during setup. Another option is to fudge the arguments as they are passed to main). Let me know if any of these work for you. |
@zjuchenyuan let me clarify a little bit. Am I correct? If yes, the quick way to solve it is to use the target binary directly during fuzzing. |
Thanks for your reply, let me clarify the problem. @gannimo @benquike The target program need to be named as The behaviour of this program depends to what the name is it, different name leads to different behaviour:
I want to fuzz I want fuzzer to keep the original ELF name rather than renaming it before fuzzing. More detailed strace output: infotocap just read the file, but tic write an output file.
|
I would suggest change this 2 lines: Lines 53 to 54 in 14777b0
change to:
Line 198 in 14777b0
change to:
|
There is a type of programs whose behaviour depend to which name they are.
busybox
is a good example, only one file is real ELF file and others are just symlink to it.In this scenario, it's important for fuzzer to keep the original ELF filename, otherwise desired program behaviour will not be triggered and fuzzed.
I want to fuzz
infotocap
, which is a symlink totic
But tfuzz actually runs: (which means it has been renamed to
infotocap_tfuzz
)Could you consider this type of program? Thanks~
The text was updated successfully, but these errors were encountered: